This feature of steam should search your documents and game directory and find any missing files and replace them with original copies. Once here click "Verify Integrity of Game Cache"
Go to "Properties" then click the "Local Files" tab. ini files.Īfter you've done all this, go to Steam, right click on Fallout4 in your library. (Unless you know what the files are and are sure you want to keep them).Īfter you've done this, go to MyDocuments/MyGames/Fallout4 and delete your. Make sure that you have all of those files, and delete any files other than these. there are a total of 9 different "Fallout4 - Textures#.ba2 (they are numbered 1-9) You should have the following files: Strings OP: I'd suggest going to your Fallout/ Data Folder (Generally: C:/ProgramFiles(x86)/Steam/SteamApps/Common/Fallout4/Data) if he's crashing at the menu it sounds like an. If that doesn't fix it, there might be something wrong with his INI files. Hope that helps.Disabling the mods(red circle with a line button) in NMM on the mods tab should remove all associated files, if that's the issue.
So to me, that was the culprit.Įdit: A thought occurred to me and I cross-referenced the file's "Date Modified/Created" information with Nexus Mod Manager's "Date Installed." For me, it appears that an old Survival Mode enabler/disabler mod (which has since been discontinued) was the culprit.
I even tried it just now, and it doesn't work with the file in the "Interface" folder. I deleted the file- everything works now. I tried running the game with it- wouldn't work. I uninstalled any and all mods that added files to the "Data/Interface" file (such as dialogue fixes, Mod manager, etc.) until I was left MainMenu.swf. That had never happened before, but a thread with similar problems mentioned that they were crashing on startup and it had turned out to be the interface loading at the startup screen (the. I can't say for sure that the solution I'm going to impart will work, because I really don't know the exact origin.īut for me, Fallout 4 wasn't working anytime the custom.ini was modified to allow mods. I had this problem until about 6 hours ago.
0 kommentar(er)
