Mods Not working on Steam Beta Update

[BSDJoker]

Ok, so I'm one of the people who has been getting plagued by constant crashes to desktop from the game. I'd been suffering through it for now. That's not really the point. I've been running some mods on the game pretty much ever since I started playing, and the list has grown a bit long, roughly 20 mods or so I've been running. I read online that one of the ways to fix the crashing issues was to use the Steam Beta update. So I went in, patched in the Beta update, redid the ini mods for the game and then launched the game. When it loads in, none of my mods are working. I tried disabling and re-enabling the mods all again and still nothing. I'm kinda worried that I somehow screwed up the games ability to be modded or something. Can anyone lend some insight onto this? I didn't see anything else listed anywhere, but I may have just missed it.

 

Thanks for your help,

Joker

[Lisnpuppy]

Unfortunately it appears that the beta update disables the ability to use plugins and other mods. This may have been intentional as Beth may (and this is pure speculation) have wanted Beta feedback with non-modded games. The Beta isn't really there to fix issues with a modded game it is there to fix issues with a vanilla game and for those folks to provide feedback as to if it works or not.

 

This game is also not really ready to be modded (as the tools are not yet out) and thus a game which you have many mods may have issues.

 

At this point I would suggest that you go from a clean install (and a new character) and either 1) stay vanilla and use the beta and play and see how it goes or 2) do a clean install and put your mods back in but not the beta patch and 3) play offline if you wish to keep these mods as when the patch goes live Steam will force the patch on you. If they have not changed it to let the mods work again then you will be in the same boat as now.

 

If they have fixed it then you can go online again and take the patch then adjust any mods that would need updated due to the patch. Keep in mind that even after the modding tools (GECK) are released there will be some mods that break after updates and will need updated by mod authors. This is just how it goes.

 

Good luck.

[selerna]

workaround for beta update users, launch the game with the exe and not the launcher, should work normally

[badpeoplesuck]

When I launch it with the EXE it just launches the damn launcher again.

[Aldebaran1113]

Open NMM to the Plugins tab. Make sre all your mods are enabled. If you have NMM set to shut down when the game is launched, turn that off.

 

Open the game using Fallout4.exe. This will open the Launcher.

 

Now wait. After a few seconds, you'll see everything on the Plugins tab disabled.

 

Reenable everything and shut down NMM (if you usually play with it off).

 

Switch to the Launcher and press Play. The game should start with all mods working.

 

This got me back up and running. Give it a shot.

 

-GD

[Uzibeatle]

Yes, this is by design and one can understand why they do so. They don't want to test mods compatabilty

or function with the beta game patch. They want to test if their beta patch does what it should with base

game and if it introduces new bugs. Plugging in mods (plugin esp files to be specific) are not part of the picture. Pointless

confusion for them.

 

That said, it is easy to workaround the 'problem'

 

Here is what I do.

I launch NMM (nexus mod manager) prior to launching the game.

I can either launch the game launcher via NMM, or via normal Steam launch.

I wait for the game launcher to pop up.

One can then watch the PLUGINS panel on NMM as the game unchecks any ESP's and that panel reflects that.

I then simply go to NMM PLUGINS panel and click that green arrow on left, I have to click it twice, to enable all plugins

that are listed. If I have to deselect any that is time to do that.

 

I then play the beta game patch with no issues. Least with the load out I use, so FAR anyway. I assume all risk .

 

By the way, none of this applies to the texture swaps you install, just plugin esps. Textures are not blocked by beta patch.

 

If you do run plugins with the Beta, do not be one of 'those idiots' who post about beta bugs and issues

without running the game minus any plugins you are using or did use.

 

Sadly, most that read this will probably ignore this and post about issues anyway. Fact is, save files

can be corrupted by these early .esp mods created minus benefit of ToolKit. Just depends on the mod, how clueless

or careless the mod author was, and random bits of cosmic rays.

 

 

ANyway, no need to riot about beta not working with mods because it 'disables' them. Move on to the next fire please.

[manni44]

Uzibeatle thank you for your solution with mods and beta patch works perfectly !

[luthienanarion]

You could also just run the game using F4SE...

[Thumper87]

I am posting this just in case some people are still having trouble with Nexus Mod Manager and Fallout 4 (Beta).

The plugin.txt (located here C:\Users\USERNAME\AppData\Local\Fallout4) for NMM can't be in "Read only". Like others have said, the game will ignore ESP plugins (not mesh/texture overides, those are not plugins) if the game is launched with plugin.txt not in "read only.

 

 

-=What I do when launching from NMM=-

I open NMM: I allow NMM to take plugin.txt out of read only.

NMM will apply all selected/installed esp files into the Plugins tab of NMM. (You can check for yourself in the plugin.txt)

Now turned plugin.txt back to read only. (right click/properties/check read only/apply)

 

Finally Launch Fallout 4 from NMM. (leave NMM open until you see all the Plugins stay checked)

 

Fallout 4 will launch the little screen that says "launch, options, settings".

When that shows up keep an eye on the Plugins tab of NMM.

If all applied ESP stay selected then you are good to go and the mods will be in game.

Edited December 6, 2015 by Thumper87

[bben46]

Please remember that whatever you do to 'fix' the mods not working in the beta version is not a true fix, but a workaround that may be part of the problem on the next Beth patch that does allow mods. Or it may still work.

 

Th beta participation is for people that choose to help Beth and steam find the bugs before a patch goes mainstream. So, don't expect it to be stable. And there may be multiple versions of the beta - and the next version may disable your workaround again. :pinch:

 

For those that don't choose to deal with the beta not working with mods, And don't want to be faced with patching a patch multiple times. Disable beta participation, and if steam does not automatically reload the older Official Release version, run the verify game cache to get back to the pre beta version. Then, when the new version comes out of beta and is actually released, you will get the new version automatically - and hopefully it will not be disabling mods. :rolleyes: