N7Lisbeth

Came back after a hiatus and I'm experiencing the same thing. Disabled and deleted everything, but I'm pretty sure it's ENB causing my issues. This never used to be the case.

I have heard there are some users who haven't had any success with that.. but I'm not one of them I guess. 6+ hours of gameplay tonight with 0 CTD issues. If I restart and have those processes run again, the game is again unplayable :down: Sorry it hasn't fixed your issues :sad: I'm guessing the people whose issues this fixed were playing on laptops. Or at least that's what I've seen alluded to.

I wish that worked, but it doesn't.

This did absolutely nothing for me. It was never running it to begin with; I must've disabled it when I first started using Windows 10. I consistently crash trying to get off the wagon (character creation), with zero mods installed. Fresh game, verified integrity, downloaded new graphic drivers, did everything I could think of. I've seen posts indicating that the wagon crash, in particular, may be related to the official high resolution textures -- if so, I'm hooped. There's no way to disable them with the Special Edition.

Same issue, started first week of October. I updated my nvidia drivers that week, updated NMM, and Windows 10 updated Windows Defender. Now I black screen/CTD before the Bethesda logo shows if I try running Fallout 4 with an ENB -- without the ENB everything works fine. Wish I knew the answer but I'm as stuck and probably even more confused than you are since I did knowingly change a few things between sessions and now can't figure out what happened. (I uninstalled drivers, rolled back, reinstalled an older version of NMM, and made exceptions in Windows Defender for Fallout 4 just in case, but nothing works.)

Chiming in on this one. I often have anywhere between 1 and 3 coinciding attacks. I usually have 100+ defence on my settlements and I've never once seen a settlement successfully defend itself post-1.5 (they did several times before 1.5). Also, there are sprawling fights constantly respawning on either side of Hangman's Alley -- I can walk by 10 minutes later and there will be another shootout in the broken houses right at Boston's edges (near Hangman's Alley). Definitely some hinkiness afoot in 1.5.

In response to post #37000585. #37008525 is also a reply to the same post. So you don't want me to point out problems? Okay.

So, I'm using the new NMM and running the Survival Beta. I tried to update a mod today. The mod was deactivated and deleted fine; I activated the new version, files moved and everything is green and checkmarked. Except it didn't add it to my plugins.txt. It clearly REMOVED it from my plugins.txt, but didn't re-add it back when the new file was activated. You want to know what it DID do? It added "*Fallout.esm" at the end of plugins.txt, even though it's at the TOP of plugins.txt and should NOT be asterisked. Just a warning to those using Survival Beta, DOWNGRADE your NMM and after everything is installed, just asterisk the files in plugins.txt yourselves. Whatever this new Survival-"compatible" NMM is doing is nothing you want to deal with. It needs time.

I created a "new" profile and nothing. Do I have to create two "new" profiles for it to show? If so, that's insipid. I'm going to chalk the thing up as broken and carry on doing what I'm doing to make it work, e.g., manual tweaking. The only thing NMM did was try to add "*Fallout.esm" at the end of my plugins.txt file -- um, one, it's already there; two, Fallout.esm is an official .esm and doesn't get an asterisk. Only unofficial mods get the asterisk. Like I said, broken.

So, I've been using mods with the Survival Beta. I installed the new version of NMM and there's no such option to "import load-order from the Profile menu." Maybe that didn't make its way into the release version or something, but that's not an option in 0.61.17. The only options under Profile are "new, rename, remove, save."

Installing the beta completely removed all the .esps from my plugins file again, so I had to uninstall all my mods and reinstall them. Given that I ran NMM before the game, I'd have thought it would make the file read-only again, but apparently it failed (or it was rewritten on the install). Seems anti-mod friendly to me, contrary to the bullet point, but reinstalling everything worked out. I also noticed it referenced which .esps were missing when I loaded a save file.