Makashisan Posted February 24, 2016 Share Posted February 24, 2016 After ruling out many other factors i found out that Editing my fallout4custom.ini caused my game to crash, however it wasn't a crash before or at the main menu. These crashes are after about a minute of gameplay, i've searched this problem alot and cant seem to find another person having this problem. Can somebody help me? Link to comment Share on other sites More sharing options...
Deleted23456504User Posted March 5, 2016 Share Posted March 5, 2016 Having the same issue.I've tried the new .ini edits listed on the wiki tutorial but it gives the same outcome. Link to comment Share on other sites More sharing options...
wax2k Posted March 5, 2016 Share Posted March 5, 2016 (edited) Thing is, those ini edits allow custom assets to be loaded. Without them, apart from any .esm / .esp mod file, the game runs in vanilla state without any custom textures, sounds and so on. What that means is, that your CTD is related to at least one of the custom assets in your \Fallout 4\data folder. The ini edit is not the cause, it just allows the cause to actually trigger. Could be a texture, a mesh file or even some modded interface file or whatever other custom mod asset. If you have no clue, which file or from which mod it could be, the easiest way would be to uninstall all mods and manually clear that folder from any non-vanilla file.The \Fallout 4\data folder should look like this to be completely vanilla: \Strings \Video Fallout4 - Animations.ba2 Fallout4 - Geometry.csg Fallout4 - Interface.ba2 Fallout4 - Materials.ba2 Fallout4 - Meshes.ba2 Fallout4 - MeshesExtra.ba2 Fallout4 - Misc.ba2 Fallout4 - Nvflex.ba2 Fallout4 - Shaders.ba2 Fallout4 - Sounds.ba2 Fallout4 - Startup.ba2 Fallout4 - Textures1.ba2 Fallout4 - Textures2.ba2 Fallout4 - Textures3.ba2 Fallout4 - Textures4.ba2 Fallout4 - Textures5.ba2 Fallout4 - Textures6.ba2 Fallout4 - Textures7.ba2 Fallout4 - Textures8.ba2 Fallout4 - Textures9.ba2 Fallout4 - Voices.ba2 Fallout4.cdx Fallout4.esm Every other file and folder should be deleted and I'd delete everything in the \Strings folder as well since that might be modded content as well.Then verify game cache in Steam to make sure, all game files are there and in order as well.Then again make the edit to Fallout4Custom.ini which should look like this afterwards: [Display] iLocation X=0 iLocation Y=0 [Archive] bInvalidateOlderFiles=1 sResourceDataDirsFinal= Then launch the game without any mods and see if it works. If it does, start adding in your mods one at a time and check for CTD in between. If you end up with all mods working fine, you probably had some conflicting leftover from earlier mod installations. If you run into a crash again, you at least know the mod causing it and can look for updates / fixes or just leave it out. Edited March 5, 2016 by wax2k Link to comment Share on other sites More sharing options...
Zombielogic Posted May 6, 2016 Share Posted May 6, 2016 Tried this method, now keep in mind the mods were still in the nexus folder. I just hunted down what was in the fall out folder itself....should I have tried to start a new save file minus the edits? I did follow all the steps above minus doing something like that.....Ugh.....all this s#*! for the console tards to get mods... -.-; Link to comment Share on other sites More sharing options...
bennyboyinoz84 Posted August 8, 2017 Share Posted August 8, 2017 wax2K. You are a champion. Link to comment Share on other sites More sharing options...
Recommended Posts