Mods Installed and Plugins active, but mods aren't working in-game.

[SpaceClopWarrior]

Hello.

 

I checked the guides on mod troubleshooting but none of them seem to really answer my problem.

 

Yesterday I did a clean installation of Fallout 4 onto my new SSD from an old HDD. I did this as was recommended by copying the files into the SSD, and then "redownloading" FO4 from Steam to my new SSD, and verified the game cache to boot.

 

Then I went and moved the Fallout 4 saves folder with the ini files to the new ssd, and also moved my nexus mod manager to the new ssd as well. For some reason, I was able to redownload and install all of my mods on the profile, but they loaded in a different way this time and now almost none of my mods work in-game.

 

I've checked my files in both LOOT and FO4Edit, and while LOOT says everything is fine and dandy FO4Edit says that while there is a lot of unused data in some mods everything else seems indicate that there shouldn't be an issue.

 

Now the fun part: Whenever I load a game save file in Fallout 4, almost all of my mods (despite showing as installed and ready to go) are not working. The modded weapons show up as invisible things that make no sound, and there is always a ctd a few short seconds later. If I load a save state where my character or another is wearing, say, a modded outfit, the game will ctd immediately. CBBE isn't working either as the game always loads my character as the base model along with everyone else.

 

I can't seem to find any solution to this problem. My inis have been edited properly as far as I can tell.

Here is this from my fallout4.ini

 

[Archive]

sResourceIndexFileList=Fallout4 - Textures1.ba2, Fallout4 - Textures2.ba2, Fallout4 - Textures3.ba2, Fallout4 - Textures4.ba2, Fallout4 - Textures5.ba2, Fallout4 - Textures6.ba2, Fallout4 - Textures7.ba2, Fallout4 - Textures8.ba2, Fallout4 - Textures9.ba2

sResourceStartUpArchiveList=Fallout4 - Startup.ba2, Fallout4 - Shaders.ba2, Fallout4 - Interface.ba2

SResourceArchiveList=Fallout4 - Voices.ba2, Fallout4 - Meshes.ba2, Fallout4 - MeshesExtra.ba2, Fallout4 - Misc.ba2, Fallout4 - Sounds.ba2, Fallout4 - Materials.ba2, Higher Female Protagonist Voice - Type U2.bsa

SResourceArchiveList2=Fallout4 - Animations.ba2

sResourceDataDirsFinal=

SGeometryPackageList=Fallout4 - Geometry.csg

SCellResourceIndexFileList=Fallout4.cdx

SResourceArchiveMemoryCacheList= Fallout4 - Misc.ba2, Fallout4 - Shaders.ba2, Fallout4 - Interface.ba2, Fallout4 - Materials.ba2

And from Fallout4Custom.ini

[Display]

iLocation X=0

iLocation Y=0

[Archive]

bInvalidateOlderFiles=1

sResourceDataDirsFinal=

Attached is my load order as of a few minutes ago. Please help if you can, as I myself have no idea what to do now. And thanks in advance.

 

[adrithefinch]

I'm also having this exact same problem. This is after hours of reading tutorials and following them to the letter, installing mods with NMM, installing them manually, uninstalling, reinstalling, only to get the same result. It's also a problem that seems to go unanswered in every forum I visit so the frustration in me is mounting.

[SpaceClopWarrior]

Hopefully someone replies with a solution or something soon. I'm quickly losing hope.

[SpaceClopWarrior]

Well I just tried something and it may have fixed my problem.

 

I had originally moved my Fallout 4 folder out of C://mygames and into the new ssd drive along with a new steamlibrary for Skyrim and Fallout 4, but apparently this broke the game as steam ended up making a fresh Fallout 4 saves directory under C://mygames and began using that one instead of the old one, or at least that is what I am led to believe.

 

I moved the old save directory that I moved into my ssd drive back into C, complimented with the old edited ini files and F4SE, and lo and behold, things have started working again. I tested a new save file and everything from the edited player voice to the CBBE textures and outfits appear to be working again, but I have yet to get into the actual fallout 4 world in order to test if everything works yet. I will get back to this forum after I get off work and test FO4 for more errors, but until then I think I may have solved my own problem. Just don't write this topic off just yet, I'm not sure If I'm completely out of the woods yet.