Fallout 4 Won't Run

[Fireapple]

https://simsettlements.com/site/index.php?threads/master-list-for-f4se-mods-that-require-an-update-every-time-something-gets-added-to-cc.4626/

 

Thread for f4se dependent update list.

[MarkusTay]

Thanks for heads-up. Precisely what I was looking for in the other thread. Cheers

Went in and checked my file structure on my C:drive. Win 10 had set my entire users folder (where game saves reside) to read only. Still didn't fix the problem but good to know, one more thing off the checklist.

 

Unless you 'assign ownership', it will not stick. Trust me, And good luck with that - you need to be an administrator, and even if you login to YOUR OWN COMPUTER as an administrator... you aren't... not really. That's the gist of what I am getting reading about some things that happened during the last Windows 10 update. That's why I had to go to a Command Line prompt. Brought back memories of my DOS, pre-GUI days.

 

However, on the bright side... your drive is lying to you. Go ahead - try changing a file on it. it will still let you. They reset ALL the folders to 'read only' every time you reboot... even if they aren't. its just to 'scare away' people who don't know what they are doing from messing around with stuff (in other words, they are trying to cut down on tech-support). We live in interesting times.

 

I took the day off from trying to fix the problem. Took the day off from gaming altogether. I need a reboot myself. I am going to try something tricky tomorrow - wish me luck.

[MarkusTay]

So late last night - after I promised myself I wouldn't even bother yesterday (although technically it was already the next day) - I did some more research and found there were two different ini files I was supposed to alter. Now, I only recall altering the one, and until very recently everything ran fine. And most of the stuff I read - even here on the Nexus - only mentioned the Fallout4Custom.ini. But, since it was something I hadn't checked, I did so, and low and behold I didn't have the other file where it was supposed to be. It was in basically the same place, but in the Fallout4pref.ini, and the line I had to add under 'Launcher' was bEnableFileSelection=1

 

Once again, I thought I found the problem. I thought 'maybe' when the latest update from Beth happened it somehow removed that file (even though I don't remember putting it there in the first place... and I have a DAMN GOOD memory).

 

So even though it was after 2AM I was so elated about my discovery (having thought I finally found the problem), I tried to start F4... and it crashed about 5-10 seconds in. It wouldn't start. it would take me to the game (yet another new game I started), but then would immediately crash before I was even able to adjust one thing on my toon. This was WORSE than what it as doing the past two days, since I was able to play the game, just not save it. Anyone know what this file is, and was that outdated info?

 

The more I tinker, the more I think something was either altered in an ini file, or something about the update isn't playing nice with a modified ini.

 

Stay tuned for the next episode of "Mark pulls all his hair out".

 

 

Adendum: For you uber modders/coders out there who hopefully have been following this problem, I have another question/mystery for you. Since I have been watching TONS of 'how to' videos about getting modding to work in F4 (which almost all say basically the same thing), the one thing I've noticed is that most of these YOUTubers don't have anything under those lines in [Launcher] (in the ini's). Yet, I have this in my Fallout4Prefini -

 

[bethesda.net]
uPersistentUuidData3=1805962700
uPersistentUuidData2=2173665329
uPersistentUuidData1=490752404
uPersistentUuidData0=1355625574

What the heck is that mess? Is that some sort of 'tracking'?

[emmingerl]

I think this was something in the last update for Fo4 as there are a few of us having the same issue of crashing during the opening. Even if you do not select anything on the main menu it will crash at about the same time that it takes you to load up a save. I know myself and a few others have done a clean install on everything and also updated F4SE to the current update but, still crashes. My ini files appear to be in good order and was working before two days ago. So, not sure what was in that last Steam update but, it seems to have effected several people. Crash happens whether I use the regular exe or F4SE to open the game.

 

I have reached out to Bethesda Support to see if there is anything in the recent update that may have been missed. I'll let you know when I hear back.

[Fireapple]

F4SE released another update with a crash fix. v0.6.15 (v0.6.14 was the one that dropped immediately after steam update Dec.6th).

I deleted everything in my FO4 root folder (not data) and then installed the newest version.

 

Game save loaded from f4se launcher for me just now, will see if it keeps working.

[emmingerl]

@applegatc

 

Trying that but, not having same success. Color me dumb but, which folder are you deleting out? I've eliminated all of the v0.6.14 files I can find and have reinstalled v0.6.15 but, still having crash.

Edited December 14, 2018 by emmingerl

[Fireapple]

*deleted double post Edited December 14, 2018 by applegatc

[Fireapple]

@emmingerl

 

Extract f4se to loose folder, inside you will see a src folder, a data folder, and the f4se loose files.

 

Check your FO4 root folder to see if you have a src folder. If so delete it.

 

Then copy over the loose files and data folder to your game root and overwrite when asked.

[Fireapple]

@emmingerl

 

Also after you overwrite with new F4SE version, open Fallout4/Data/F4SE/plugins folder to see what mods are dependent. Check for updates (looks menu is f4ee in the plugins folder)

 

The usual culprits for update are

 

MCM

Looks Menu

Extended dialogue interface

Place Everywhere.

 

Hope this helps.

[emmingerl]

@ applegatc: Thanks! Did that, just wasn't sure if I was in right folder.

 

Found this post from way back and it has fixed my issue. I disabled ALL mods in Vortex, ran the game and no crash, ran F4SE and no crash. It did however pop up that my looksmenu was out of date but, otherwise ran everything ok. Just to be clear... What I did was disabled ALL mods but, I let all the plugins enabled and it did the trick plus mods were running in game as well. Hope that helps.

 

Also, I went through and enabled each mod to find the culprit. Found it was simply a mod that did not go through its normal FOMOD install menu. Also found 1 mod was not playing well with others period. I suspect that it just needs to be deleted and reinstalled but, since it's not a mod I really use, I just got rid of it.

 

Make sure you have the latest F4SE installed and screen through your mods to make sure there are no orange colored notes or flags on them in Vortex and you should be good to go.

 

I'll leave a copy of the full post I found that helped me.:

 

 

Hey everybody,

 

I was getting occasional crashes that became more and more frequent until there was just no way to play the game at all, barring reverting back to the original INIs... which meant, of course, no mods.

 

Eventually, after a lot of pain and suffering (and re-downloads and re-installs) I worked out what was happening and how to fix it. Here's the step-by-step:

1. Open NMM
2. Click on each mod, one at a time, and click the icon on the left to "Disable" it.
3. Go to Program Files (x86)\Steam\steamapps\common\Fallout 4\Data
4. It should ONLY have TWO FOLDERS: Video and Strings... so delete anything else that might have been left over. This is what's been crashing your game.
5. Launch Fallout 4 and load a few games just to make sure it isn't crashing.
6. Quit Fallout 4.
7. In NMM, reinstall just a few of your mods and then load your games, make sure they aren't crashing.
8. Repeat the last step until you're back up and running.

This is generally going to do it. Here are a few things others have suggested that you can also try if the above doesn't work:

• Run FOMM to sort the load order and get a sense of any known conflicts.
• Check your mods for compatibility patches.
• Load a previous game, make sure it's not just a corrupted save file.
• Sleep for a week in-game, let all the cells reset themselves.
• In Steam, right-click on Fallout 4, go to Properties, and tell it to Verify the Cache... it usually finds a file or two that was "corrupted" (NOTE: you'll have to re-do your settings and re-customize your INIs if you do this!)
• Uninstall / Reinstall

Let me know if any of the above works for you, or if you have more ideas on Fallout 4 troubleshooting!

Edited December 15, 2018 by emmingerl