Oggie221 Posted December 7, 2015 Share Posted December 7, 2015 Right now as it stands i have found only ONE successfuly method for playing my Fallout 4 as it was fully modded before this darn update. its is as follows: (( First i went into the settings 'cog' at the top of NMM and in the general tab unchecked ' close Nexus Mod manger after game launch' )) then.. 1) Open NMM. You will see all the plugins unchecked. (or maybe checked) anyways... 2) Top top left of NMM you will see a tab ' Launch Fallout 4'. 3) Click it once. this opens up a FO4 launch popup. when it does this, after a few seconds you will suddenly see all your plugins on NMM uncheck automatically.grrr... 4) click the green Tick on the left and activate them all again. 5) Now on the game launcher popup for Fallout 4 click PLAY. The game should run with all your MODS. :smile: Only downside so far is you have to do this each time you freshly launch NMM and Fallout 4 via steam. I am sure there are better ways to do this and i hope a fix soon but this clumsy method i use works for now.This workaround checks out. It so far is the only workaround that completely checks out. Good job sophiextime Link to comment Share on other sites More sharing options...
fadingsignal Posted December 7, 2015 Share Posted December 7, 2015 Exactly, I'm opted out of any betas and I still got the patch, it went official / live today. Thankfully all my files are set to read-only so I didn't have any issues. Link to comment Share on other sites More sharing options...
redfesh Posted January 8, 2016 Share Posted January 8, 2016 http://www.ign.com/wikis/fallout-4/How_to_Install_PC_Modsmaybe this will help? Link to comment Share on other sites More sharing options...
Arnaeus Posted January 8, 2016 Share Posted January 8, 2016 (edited) Thread necromancy! That stuff with sResourceDataDirsFinal is old. Use bInvalidateOlderFiles=1 instead. Don't use Fallout4.ini, use Fallout4Custom.ini http://wiki.tesnexus.com/index.php/Fallout_4_Mod_InstallationAnd:All that won't help with the patch.Renaming the launcher to something else (i.e. Fallout4Launcher.renamed.exe) and the standard game exe to Fallout4Launcher.exe does help. If you do that, steam will never start the launcher and the mods wont be disabled. You can start the launcher manually if you want and reactivate the mods via NMM later. Edited January 8, 2016 by Arnaeus Link to comment Share on other sites More sharing options...
tomomi1922 Posted January 9, 2016 Share Posted January 9, 2016 Thread necromancy! That stuff with sResourceDataDirsFinal is old. Use bInvalidateOlderFiles=1 instead. Don't use Fallout4.ini, use Fallout4Custom.ini http://wiki.tesnexus.com/index.php/Fallout_4_Mod_InstallationAnd:All that won't help with the patch.Renaming the launcher to something else (i.e. Fallout4Launcher.renamed.exe) and the standard game exe to Fallout4Launcher.exe does help. If you do that, steam will never start the launcher and the mods wont be disabled. You can start the launcher manually if you want and reactivate the mods via NMM later. Does this still work with this new patch? Link to comment Share on other sites More sharing options...
razor157104 Posted October 18, 2016 Share Posted October 18, 2016 (edited) Im having problems the mod appears on the sections but it has a cancel sign and i cant activate it l Edited October 18, 2016 by razor157104 Link to comment Share on other sites More sharing options...
Recommended Posts