3. Game crashes after I press F to enter a car (SOLVED)
Log in to reply
 

Game crashes after I press F to enter a car (SOLVED)


  • Hello. This is my first post here

    I need someone to help me with this crash problem. So it happens when I press F to enter RUNE Cheburek, the game instantly freezes for five seconds and crashes to desktop. Even worse is it causes random crashes when this car spawns in traffic with modded popgroups.ymt

    I'm sure this happens because of a specific mod that caused this problem. So I want someone to solve this crash, especially what files that caused this

    Edit: The case has been solved. But I accidentally marked one of my replies as a solved

    That's all. I'm glad if you're able to help me. Thank you

    0
  • A

    @Daddynnoob said in Game crashes after I press F to enter a car:

    specific mod that caused this problem

    What specific mod was it? Link to the download if you can etc

    "Never imagine yourself not to be otherwise than what it might appear to others that what you were or might have been was not otherwise than what you had been would have appeared to them to be otherwise." - Lewis Carroll (Alice in Wonderland)

    0

  • @a63nt-5m1th Probably Sparky's Traffic Overhaul

    0
  • A

    @Daddynnoob
    If you want to revert the changes 'Sparky's Traffic Overhaul' made you can create an uninstaller for it using this tutorial (also shows you how to access & edit/extract an '.oiv' installer & see where & what it installed (useful to know etc)), or if you have a working backup of 'update.rpf', revert to that (as that is the only '.rpf' archive 'Sparky's Traffic Overhaul' edits :thumbsup:).

    If you don't have a backup of 'update.rpf' you could test a vanilla 'update.rpf' in it's place, but keep a backup of the 'update.rpf' you have at the moment, as it will be useful for (non-Sparky's edited) file retrieval if you have to rebuild 'update.rpf' & also just in case it turns out Sparky's wasn't the cause of your issues you can revert to it if you need to etc.

    "Never imagine yourself not to be otherwise than what it might appear to others that what you were or might have been was not otherwise than what you had been would have appeared to them to be otherwise." - Lewis Carroll (Alice in Wonderland)

    0

  • @a63nt-5m1th Thank you for this, but I doubt this mod causes the crash because I feel like the crash happens before I instal this mod. So I just want to find the files that cause this problem

    0
  • J

    @Daddynnoob why not remove your change to popgroups.ymt and see what happens. Cause and effect.

    GTA 5 2023 Help Desk -- and -- GTA How to Install Mods

    0

  • @JohnFromGWN Already did after the crash happens many times

    0
  • J

    @Daddynnoob The only time I've ever seen a similar issue is when I was researching a fix for the Code 16 error. There was an old mod, which i never used, which apparently could crash when trying to enter the vehicle but while crouched or stealth, don't remember which.

    Just saying this because your issue might be due to a script mod. Have you tried renaming your scripts folder temporarily and see what happens? Could also be an asi mod. Would rename those making sure extension isn't asi to prevent load.

    GTA 5 2023 Help Desk -- and -- GTA How to Install Mods

    0
  • A

    @Daddynnoob
    If the Cheburek is removed from 'popgroups.ymt', it can't be causing the random crashes & in that case you would most likely have two separate issues. So, confirm for us, have you test removed the Cheburek from 'popgroups.ymt' & if so, does the random crashing persist? Thanks.

    Obviously, there is an issue with entry to the Cheburek, so I'll deal with that first :thumbsup:

    Cheburek Entry - Freeze & Crash Issue:

    Do what @JohnFromGWN says & remove scripts as a variable before proceeding. Once you've done that (& if it offers no solution) try reverting the 'mpassault' files to vanilla as a test (after making full '.rpf' backups ofc).

    Best method is probably to revert them all to vanilla to confirm whether they fix the entry crashes or not & then if they do & you want to know what file caused it, or you have other data in those files you don't want to lose etc, use your backups to revert those changes & test each file one at a time.

    If required, after you identify the file/s causing it, you can compare them to vanilla ones using something like https://www.diffchecker.com/ or WinMerge & see if you can identify the exact value/s/entry etc.

    Instructions:
    Grab vanilla versions of these 'mpassault' '.meta' files & place them here (even if they don't exist there already):

    ...\Grand Theft Auto V\mods\update\update.rpf\dlc_patch\mpassault\common\data\ai\vehiclelayouts.meta
    ...\Grand Theft Auto V\mods\update\update.rpf\dlc_patch\mpassault\common\data\levels\gta5\vehicles.meta
    ...\Grand Theft Auto V\mods\update\update.rpf\dlc_patch\mpassault\common\data\carcols.meta
    ...\Grand Theft Auto V\mods\update\update.rpf\dlc_patch\mpassault\common\data\carvariations.meta
    ...\Grand Theft Auto V\mods\update\update.rpf\dlc_patch\mpassault\common\data\handling.meta

    Note:
    'update.rpf\dlc_patch' (not dlcpacks etc). Also, test them in order as 'vehiclelayouts.meta' & then 'vehicles.meta' (or a combination of issues in both) are the most likely '.meta' file related causes for crashing when entering a vehicle.

    'dlc_patch' vs 'dlcpacks' Info:
    Basically, if a file exists in the same (correct) location within both 'update.rpf\dlc_patch\dlc_name_here' & 'dlcpacks\dlc_name_here\dlc.rpf' the one in the 'update.rpf\dlc_patch' folder structure will be the one loaded by the game, so placing them in 'dlc_patch' (even if they don't exist already) will guarantee that they are the ones loaded by the game.

    If the Cheburek still has entry issues after reverting the '.meta' files, also revert to vanilla:

    ...\Grand Theft Auto V\mods\update\x64\dlcpacks\patchday19ng\dlc.rpf\x64\levels\gta5\vehicles.rpf\cheburek.yft
    ...\Grand Theft Auto V\mods\update\x64\dlcpacks\patchday19ng\dlc.rpf\x64\levels\gta5\vehicles.rpf\cheburek_hi.yft
    ...\Grand Theft Auto V\mods\update\x64\dlcpacks\patchday19ng\dlc.rpf\x64\levels\gta5\vehicles.rpf\cheburek.ytd
    ...\Grand Theft Auto V\mods\update\x64\dlcpacks\patchday19ng\dlc.rpf\x64\levels\gta5\vehicles.rpf\cheburek+hi.ytd
    ...\Grand Theft Auto V\mods\update\x64\dlcpacks\patchday19ng\dlc.rpf\x64\levels\patchday19ng\vehiclemods\cheburek_mods.rpf

    Also, do an OpenIV Ctrl+F3 'mods folder only' search for those Cheburek files just above (.yft/.ytd/_mods.rpf etc) & make sure none exist in another mod/dlc that might be overriding those patchday19ng vehicle model/texture files (like EMF or another replace vehicle add-on etc).

    Random Crashing With A Possibility Of It Being A Vehicle As The Cause:

    Quickest & easiest way to diagnose that would be to edit 'popgroups.ymt' & 'vehiclemodelsets.meta' & remove vehicles. If you use these empty 'popgroups.ymt' & 'vehiclemodelsets.meta' files as a test, you'll be able to confirm whether your random crashes are related to them or the vehicles they spawn.

    File Locations:

    ...\Grand Theft Auto V\mods\update\update.rpf\x64\levels\gta5\popgroups.ymt

    ...\Grand Theft Auto V\mods\update\update.rpf\common\data\ai\vehiclemodelsets.meta

    If those 'empty' files fix the random crashes, test each file independently & figure out whether it's one of them or both that cause the crashes.

    50/50 / Binary Test Method:

    Quickest way to diagnose an issue like this, where you need to identify a particular value within a large file, is to use what's called a 50/50 or binary test method. That will allow you to usually identify a culprit's general location within ~6 to 7 loads of the game (for 100 starting entries). Even starting with 1000 entries to begin with, you can usually find the issue within ~10>11 loads of the game & for 10,000 starting entries ~14>15 loads of the game. So you can see the benefit of learning it for modding :thumbsup:

    50/50 Method - Proof of Concept (starting sample 100 entries in file):

    No. of Loads of Game        No. of Entries
         0                       100
         1                       50
         2                       25
         3                       12.5 (lets call it 12)
         4                       6
         5                       3
         6                       1.5
         7                       <1 (i.e below 1, entry identified)

    50/50 Method:
    Basically, either add to an empty file or remove from a full file half of the entries (use my empty files & copy & paste between them & yours etc) & then load the game & see if the issue persists.

    • If it persists, you know it's not in any of the empty entries (so they can eliminated), but instead must exist in one of the entries that has data in it. You then empty half of those filled entries (replace them with empty ones from my file etc) & test load the game again. Continue using the method like that until you find the entry causing it.

    • If your issue/crash is fixed with your initial 'half full' file test, you know the issue must reside in one of the empty entries. Fill half of the empty entries with their data & test load the game again. Proceed like that until you find the issue causing it.

    Alternatively, for 'popgroups.ymt' & 'vehiclemodelsets.meta' you could always go section by section, but that will take a little longer:

    Section by Section could potentially require (at absolute worst):

    popgroups.ymt         = ~36 loads of the game

vehiclemodelsets.meta = ~150 loads of the game

    So, if you do go section by section, try 10 or so sections at a time to cut-down the maximum amount of potential loads of the game required. That, or use a hybrid method utilising both sets of principles etc.

    "Never imagine yourself not to be otherwise than what it might appear to others that what you were or might have been was not otherwise than what you had been would have appeared to them to be otherwise." - Lewis Carroll (Alice in Wonderland)

    1
  • M

    @Daddynnoob Go to menyoo's vehicle spawner and in the spawn settings make sure teleport to spawned car is checked.

    Then try spawning the car.

    If it doesn't teleport to the car when it spawns; the car is using a wrong/missing vehiclelayouts.meta file.

    If it does teleport to the car and it crash; there is something wrong with the model or one of the meta files.
    In this case, take a random vanilla car (preferably from x64e.rpf) and rename it to that car. Replace it and try.

    If it works; the car model has a fault.
    If it doesn't work; there is an error in one or multiple meta files.

    It is possible to use another car's meta files if you know what needs to be copied over.

    2
  • J

    @MissySnowie funny how every gamer has different needs. I never use vanilla cars, only addons, and they never cause this kind of issue. Problems occur when you start modding the hell out of every editable file, then add scripts, and then try to find what went wrong.

    There was a joke, perhaps misogynistic, that a woman marries the perfect man and then spends the rest of her life getting him to improve. Bad joke aside, GTA5 modders never accept the game behavior as designed. I never change the game mechanics, I just expand its assets and entities.

    GTA 5 2023 Help Desk -- and -- GTA How to Install Mods

    1

  • @JohnFromGWN Already did, but the crashes still happens

    0

  • @MissySnowie I already did, but it makes the player ragdoll at the top of the car because the auto-enter while spawning the vehicle is enabled, and that is because of that problem

    0

  • @justincornishseo Are you a bot?

    1
  • M

    @Daddynnoob Then try checking the second part. It's either vehicle model or a misconfigured meta file.

    It happens time to time. I had a Humvee and Black Hawk in a dlcpack with a different type of paint, one day they started to crash my game out of nothing.

    Got it fixed by renewing the metas.

    1

  • @MissySnowie It's still nothing changed

    0
  • A

    @Daddynnoob said in Game crashes after I press F to enter a car:

    It's still nothing changed

    You're talking about just the Cheburek entry issue there^ yeah?

    We should concentrate solely on that one issue/crash for now anyway, so forget the random crashes if you haven't already (diagnosed that/them later/after the Cheburek is fixed etc).

    Cheburek Entry Crash:
    Give us a list of all of the things you have tried to fix the Cheburek. Thanks
    If you can, include folder paths to the files you have reverted/changed & give us a thorough account of the steps you have taken. Be as detailed as you can, don't spare the keyboard, the more info the better :thumbsup:.

    Like, did you:

    • Use Ctrl+F3 in OpenIV to make search for & make sure no other Cheburek model/texture files exist in another location, like another add-on or in a patchday higher than patchday19ng?
    • Replace the '.meta' files in 'update.rpf\dlc_patch\mpassault' folder structure as well as the ones in 'mods\update\x64\dlcpacks\mpassault'?
    • Try the 'Cheburek Entry - Freeze & Crash Issue:' instructions from my previous post? Double-check you replaced every single file listed there (all 10 of them) & specifically confirm for us that you've done so. Thanks

    Also, where are you getting the vanilla files from? If it's from the vanilla/game folder, run whatever verify integrity method is appropriate for your version of the game & make sure the files are fully 100% vanilla before using them to replace the mpassault/Cheburek files a second time:

    Methods to Verify Integrity of Game Files:

    "Never imagine yourself not to be otherwise than what it might appear to others that what you were or might have been was not otherwise than what you had been would have appeared to them to be otherwise." - Lewis Carroll (Alice in Wonderland)

    2
  • J

    @Daddynnoob

    If all fails after taking the wise advice from @a63nt-5m1th and @MissySnowie, remember that there are 3 reasons why your game will break.

    With experience you get to find the problem area quickly, but there are times when you need to accept you made too many changes or the wrong changes and either start from scratch or do a rigorous and systematic troubleshooting clinic.

    This is guaranteed to find where the problem lies, but not necessarily the optimal solution. Some issues can be solved, others have workarounds, and some require acceptance and uninstalling misbehaved mods.

    If you get to the point where the pain exceeds the pleasure:
    Troubleshooting

    GTA 5 2023 Help Desk -- and -- GTA How to Install Mods

    2

  • @a63nt-5m1th 1. I've installed this Cheburek mod inside patchday19ng folder after the crash happens. So it's not because of this mod

    1. I've done replace carvariations, handling, and vehicles.meta in both dlc_patch and dlcpacks of mpassault, and the results is none
    2. Seems I missed the third option, but I'm gonna only replace vehiclemodelsets.meta
    0

    1. Seems I missed the third option, but I'm gonna only replace vehiclemodelsets.meta

    Nevermind, it's not the problem of the crash

    0
  • A

    @Daddynnoob

    1) -

    If you still had entry issues even with the modded Cheburek installed to patchday19ng. That would tent to suggest the issue is either:

    • in one of the mpassault '.meta' vehicle files

    or

    • the Cheburek is being loaded by the game from another location.

    I'm going to presume the modded Cheburek worked & you saw the changes in-game when you installed it? If so, your Cheburek entry crash/issue most likely resides in the mpassault '.meta' vehicle files:

    ie In one of these:

    vehiclelayouts.meta
    vehicles.meta
    carcols.meta
    carvariations.meta
    handling.meta

    Most likely vehiclelayouts.meta or vehicles.meta.

    2) -

    What about the 'mpassault' 'vehiclelayouts.meta'? Have you reverted that to vanilla as well? That's generally the most important one for vehicle entry issues.

    Get the vanilla version of that mpassault 'vehiclelayouts.meta' from here:

    ...\Grand Theft Auto V\update\update.rpf\dlc_patch\mpassault\common\data\ai\vehiclelayouts.meta

    & use it to replace your 'mods' folder version here (even if it doesn't exist):

    ...\Grand Theft Auto V\mods\update\update.rpf\dlc_patch\mpassault\common\data\ai\vehiclelayouts.meta

    Note:
    Check the folder structure carefully. You're going to 'dlc_patch' within 'update.rpf'. Ignore the 'dlcpacks' 'mpassault' 'vehiclelayouts.meta' file, as it's not loaded by the game (as long as the one in 'dlc_patch' actually exists ofc).

    3) -

    As I think you noticed, 'vehiclemodelsets.meta' was just referenced in relation to the random crashes you are having. It won't do anything to help fix the Cheburek entry crash.

    Note: Don't try to fix more than one issue/problem/crash at a time, just concentrate on one & fix that first & then diagnose the other after :thumbsup:

    "Never imagine yourself not to be otherwise than what it might appear to others that what you were or might have been was not otherwise than what you had been would have appeared to them to be otherwise." - Lewis Carroll (Alice in Wonderland)

    0

  • @a63nt-5m1th Oops my bad, the modded Cheburek I instal is actually in mpassault, since I realised I don't have patchday19ng folder in my modded dlcpacks

    0

  • @a63nt-5m1th I replaced all of these .meta files into dlc_patch of mpassault but nothing changed. Anyway, do you know how the crash works? If you don't I'm probably send you the video of the crash

    0
  • J

    @Daddynnoob
    Must be frustrating making all those changes, multiplying the potential crash variables tenfold, and going deeper and deeper into the rabbit hole.

    Ever consider doing a reset instead of all these trial and error changes, hoping the spaghetti will stick to the wall?

    If you agree your game broke because of changes, whether simply adding a mod or editing 10 meta files, why not undo all these changes. I'm not talking reinstalling the game, I mean do a verify integrity to ensure all your vanilla files are purely vanilla and copy the ones that engendered your issue to your mods folder. Uninstall, temporarily, the suspect mods.

    Next, one step at a time, redo your changes and installations, testing after each edit.

    In passing, from experience, selectively restoring files in an rpf, while simpler and seemingly logical, is not the best approach when your game is FUBAR. Instead restore the full rpf, not just the component files, because as much as we have faith in OpenIV it's not foolproof.

    You've gotten excellent advice in this thread but you're still struggling, so you might want to consider a reset. Sounds too obvious but it works 100% of the time. Remove the changes, problems magically disappear, reintroduce changes patiently and systematically testing in between. Or continue what you're doing.

    Remember that your system is different from all others, and due to configurations, settings, and potential conflicts due to modkits, or scripts, or unknown factors, you might never get a specific mod to work even though it works for others. At some point you might just want to walk away from a problematic mod.

    GTA 5 2023 Help Desk -- and -- GTA How to Install Mods

    1
  • A

    @Daddynnoob
    Do you have patchday19ng activated in your 'mods' folder's 'dlclist.xml'?

    ...\Grand Theft Auto V\mods\update\update.rpf\common\data\dlclist.xml

    Also, when you installed the modded Cheburek, did the vehicle change to the modded one in-game?

    "Never imagine yourself not to be otherwise than what it might appear to others that what you were or might have been was not otherwise than what you had been would have appeared to them to be otherwise." - Lewis Carroll (Alice in Wonderland)

    0
Log in to reply
 

Looks like your connection to GTA5-Mods.com Forums was lost, please wait while we try to reconnect.