son0fgrim Posted September 10, 2017 Share Posted September 10, 2017 (edited) So I need some help with Fallout 4 crashing Too desktop when i hit Escape.I Verified Cache, removed mods that do stuff too the menus, Sand blasted out my entire install and reinstalled the entire game from scratch, and reinstalled my mods. still crashing too desktop with no error message.Mod list:https://pastebin.com/A2jbtmZs Update: Game is Crashing on a Clean Install, new game, no mods installed before hand. Edited September 10, 2017 by son0fgrim Link to comment Share on other sites More sharing options...
arrtista Posted September 11, 2017 Share Posted September 11, 2017 (edited) WARNING :nuke: these changes will solve the problem but after many mods they will not work properly. The decision is very hard, I do not want responsibility LOL.. Specifically, it is the string added in the Fallout4.ini file to run the mods the problem: sResourceDataDirsFinal = STRINGS \, TEXTURES \, MUSIC \ SOUND \ INTERFACE \ MESHES \ PROGRAMS \ MATERIALS \ LODSETTINGS \ VIS \ MISC \ SCRIPTS \ SHADERSFX \ You can delete it and replace with this: sResourceDataDirsFinal STRINGS=\ it worked for me or You can resolve by deleting Fallout4prefs.ini, Fallout4custom.ini and Fallout4.ini files from the My Games folder, and then from STEAM verify the integrity of the game files, the files will be recreated and should work. Those changes served to enable mods for PC but after the Creation Club update, :mad: not work properly. Someone will sooner or later create some solution, me too also waiting and I still have not found anything.. :happy: Edited September 11, 2017 by arrtista Link to comment Share on other sites More sharing options...
son0fgrim Posted September 12, 2017 Author Share Posted September 12, 2017 (edited) Ok The first solution worked With minor stability Issues as a result. Edited September 13, 2017 by son0fgrim Link to comment Share on other sites More sharing options...
son0fgrim Posted September 13, 2017 Author Share Posted September 13, 2017 Upon further review that first solution only caused insanely more issues then it fixed which only became apparent after the Tutorial bit was over. So now we are back too square one. Link to comment Share on other sites More sharing options...
arrtista Posted September 13, 2017 Share Posted September 13, 2017 (edited) Just put the old string back in place, however with the new .ini files it would not be difficult.I'm opening discussions about it in some posts. This works, before maybe a backup of .ini files.. "This works for me:Only adjust Fallout4custom.ini with[Archive]bInvalidateOlderFiles=1sResourceDataDirsFinal= nothing in prefs.ini related to [archive] Fallout4.ini AND the Fallout4default.ini in the game folder are 'vanilla'. Verify on steam if you changed those." Edited September 13, 2017 by arrtista Link to comment Share on other sites More sharing options...
son0fgrim Posted September 13, 2017 Author Share Posted September 13, 2017 (edited) My main issue is that my mods aren't loading anymore with the first solution and trying too play Fallout 4 without mods is like eating a Sandwich that only consists of Bread.The only lines In Fallout4custom.ini are [Display]iLocation X=0iLocation Y=0 do i put the new line above or below that? Edited September 13, 2017 by son0fgrim Link to comment Share on other sites More sharing options...
arrtista Posted September 13, 2017 Share Posted September 13, 2017 I think it's the same thing.. anyway it's still work in progress, I'm noticing that with those changes DEF_Ui does not work. I'm waiting for answers in the Transfer Settlement Blueprints post. :wallbash: Link to comment Share on other sites More sharing options...
son0fgrim Posted September 13, 2017 Author Share Posted September 13, 2017 (edited) I'm not using Def_UIHere are the files as they currently stand when I press Esc and the game crashes to desktop: Fallout4.INIhttps://pastebin.com/0xut0G7SFallout4Cutom.inihttps://pastebin.com/gaQQmwkGFallout4prefs.inihttps://pastebin.com/4kv0wuXk I have no idea what the hell is wrong at this point. Edited September 13, 2017 by son0fgrim Link to comment Share on other sites More sharing options...
arrtista Posted September 13, 2017 Share Posted September 13, 2017 Bethesda's update has compromised NMM's operating and the mod's enabling process, seems to be a meditated thing to temporarily slow mods from Nexus and other third parties. Solution: We expect that for someone to find a solution or in a definitive way return to the previous build and block upgrades from Steam. Link to comment Share on other sites More sharing options...
son0fgrim Posted September 13, 2017 Author Share Posted September 13, 2017 Bethesda's update has compromised NMM's operating and the mod's enabling process, seems to be a meditated thing to temporarily slow mods from Nexus and other third parties.Solution:We expect that for someone to find a solution or in a definitive way return to the previous build and block upgrades from Steam. So i'm f*#@ed until we find a work around? Link to comment Share on other sites More sharing options...
Recommended Posts