1.5 Update Disabling Mods?

[Bootskii]

I just got the 1.5 update. Despite being activated in NMM (all are .esp), none of my mods actually work in-game. I'm assuming this is related to Bethesda's own modding system, but it seems that the update is affecting everyone a little bit differently, which is why this is so confusing. And yes, I have the required .ini edits. Mods are all from Nexus. They appear in Bethesda's new in-game Mods menu, specifically in the load order, but seem to load forever without progress. I just updated NMM to 0.61.20.

 

If it helps, then here's an absurdly detailed explanation of exactly what I've been doing in FO4:

SURVIVAL BETA:

I had a butt-load of mods installed before the Survival beta. When I tried the Survival beta, I did a fresh install and deleted all my mods, and started a new game, but keeping my old, heavily modded one (which I didn't touch during the beta).

 

I've enabled auto-updates in Steam, and therefore have the 1.5 update. I also updated to the latest NMM to the one they told me to. Like I said earlier, NMM seems to work just fine, but the mods don't activate in-game, so it's basically running Vanilla. When I exit the game and go back to NMM, all the mods and .esp files are apparently still active. This goes for both save files. As I mentioned, all my mods (all from Nexus) appear in the new in-game mod menu (see above) and just load forever.

I also have both DLCs.

 

 

 

My Current Mods as they appear in NMM Mods tab (all active):

 

Brighter Settlement Lights

 

Darker Nights 1.10.6

 

Darker Nights 1.10.6 for True Storms 1.3

 

Fallout 4 Seasons - Grass - Trees - Plants - Snow - Seasons Summer 3.0

 

Ponytail Hairstyles by Azar - Ponytail Hairstyles by Azar v 1_6

 

Proto Vault Suit - Proto VaultSuit - Blue 1.2

 

SURVIVAL QUICK SAVE - No Sleep Til Bedtime - SURVIVAL QUICK SAVE

 

True Storms: Wasteland Edition

 

Vault Booty - Enhanced Female Vault Suit - Vault Booty 1.0.3 Boobish Update

 

 

 

My Plugins as they appear in NMM Plugins tab (all checked/active):

 

Fallout 4.esm

 

DLCRobot.esm

 

DLCworkshop01.esm

 

Quick Save.esp

 

TrueStormsFO4.esp

 

TrueStormsFO4-ClimateSettings.esp

 

TrueStormsFO4-GlowingSeaExtraRads.esp

 

DarkerNightsDetection.esp

 

DarkerNights.esp

 

DarkerNights-TrueStorms.esp

 

AzarPonytailHairstyles.esp

 

BrighterSettlementLights_LessHarsh.esp

 

 

 

My Rig (not so detailed):

 

MSI Dominator Pro GT72 yada yada yada

 

Windows 10

 

Core i7 6820HK

 

GTX 980M

 

32GB DDR4 RAM

 

Everything is on my internal D: drive, i.e. separate from OS. This was not an issue before, and I can't imagine it would be now. I'm able to overclock, but I never have.

Edited April 30, 2016 by Bootskii

[HeyYou]

I think you need to update NMM to work with the 1.5 update.

[Bootskii]

Already updated to 0.61.20 last night. Sorry, I didn't make that as clear as it should be.

Edited April 30, 2016 by Bootskii

[jemacdonald]

I have been reading through these posts with interest because I too am having to re-activate each of my mods every time I launch the game. First, let me say that I am still using Nexus Mod Manager 0.61.4 because I have not been able to upgrade Nexus Mod Manager. Unfortunately, newer versions of Nexus Mod Manager require installing an update to MS .Net framework 3.5 which I cannot do since I have been unable to install win 7 sp1. That being said, everything had been working pretty well for me until FO4 1.5 was rolled out.

 

I followed the procedure to activate all my mods with Bethesda.net active. Everything seemed to be fine. I played for an hour or so then saved and closed the game for the night. Today I found I had to reactivate each of my mods again at start-up. Frustrating! So I started doing some testing and checking. Although my mods are all inactive when I launch the game, they are all checked active in Nexus Mod Manager. I ran LOOT to check the mod order, made sure the plugins.txt file was not write protected and updated the load order. This, of course, generated a new plugins file which was, once again, set to read only. All of the mods were still active in Nexus Mod Manager. When I launched the game sure enough – all mods were inactive. At that point, I rechecked and all mods in Nexus Mod Manager were still checked active. I once again reactivated all the mods at the startup screen and continued my saved game. Everything was fine except it reported that “some content is no longer present”. I have gone through this same procedure 6 or 7 times. Every time, my mods are not active at launch. I’ve reactivated them again each time. Sometimes the content missing message is reported, sometimes not. Each time I check the status of Nexus Mod Manager and all the mods are still checked. Also, the status of the plugins.txt file has not changed since I ran LOOT. It is always set to read only with the same date and time filestamp.

 

Based upon what I see, it appears to me that the problem is squarely on Bethesa’s doorstep. I cannot say that newer versions of Nexus Mod Manager which have been modified to play nice with Bethesda.net do not also have their own problems. But I have to believe that the mod manager Bethesda has built into the 1.5 update is not working correctly. Let’s hope someone can find a fix for this quickly because reactivating 100 mods at each launch has gotten real old real fast.