Textures Glitches (ArchiveInvalidated related?)

[deangame2]

Well everything was going smoothly, and I was playing around 70 mods installed (including all DLCs.etc) I notice that there was a glitch with Breezes new male bodies the skin of the guys heads would not match their body. Plus, their underwear texture was the right one but it wasn't mapped properly to the mesh. so I google it and find out I don't have (or rather I had to re-reactivate archiveinvalidated) wala, it works like a charm.

 

But, another problem surfaced right after this. Stuff like this started to happen. For whatever reason, on specific armors and weapon textures are seemingly "corrupted" or they loaded improperly.

 

Sometimes its just part of the armor/weapon (On the m110 rifle mod the weapon itself is textured properly but the scope texture is much like the athe pictureIndeed, the main problem is that these weird "blips" of random, bright colored pixels seem to be on specific, yet random things. Most notably it replaced the whole damn texture of the night sky (not the day sky weirdly) with this weird texture. Although it didn't heavily affect the armors/weapons I used it was annoying so I decided to see if I can fix it.

 

Notably, I was told that Nexus Mod Manager's Archive invalidated doesnt work for Breezes new male bodies I was directed to use the older FOMM's archive invalidated. That got it to work, however I don't know if the fact that I had FOMM and NMM archive invalidated both turned on were creating weird issues.

 

 

Attempts to Fix

 

-Deactivating ArchiveInvalidated

Although doing this DID remove the weird blip textures, it pretty much made every mod that included a custom texture pretty much broken. Not even Item logos were displayed. So that was out of the question

 

-Deleting Mods

I sized my mods down to around 45, however the way I went about doing this im not sure if it was actually effective. Research has told me that sometimes stuff like this can happen when you've played for a long time and there are too many plugins, mods.etc active at the same time. One thing to note is that this has been happening the instant I load the game, not after a long play session. The way I went about deleting mods was because I install mods manually (drag and drop folders/esp into the data folder) its kind of cluttered and I dont know what to delete to not harm the mods I want to keep. So I just started deleting esps of the mods I didnt want and esms.etc In past experience this has lead to some mods being "always on" as in they act as if they're part of the vanilla game. That is leaving in the files but deleting the esp. Either way this didn't seem to help. I also knew that just because an esp/esm is not activated doesn't mean its not creating clutter or problems

 

Notably, I tried running a game with no mods activated (or so I think) a pure vanilla game, I go past the tutorial, go outside and wait till night fall and then the texture glitches are still showing up. The picture from above is from a vanilla game.

 

-Reinstalling

Clean reinstall and reupdate to current patch, left all the mods intact however, no effect.

 

-Memory?

Some of my research has told me that this could be due to your computer using too much memory. This is possible since the data folder alone of my FNV is 22 gigs. But I was playing the game and looking at my CPU usage and memory and it doesn't seem to go into the danger zone. Plus if this where the case I imagine it would come from a long play session like what happens when I play SWTOR for too long.

 

-Save files

I thought maybe a safe file got corrupted so I moved all of my saves out of the folder and started fresh, but still problems.

 

So I'm stumped essentially, I also use NVSE. Please help if you can.

 

If I can't this resolved I'm going to complete uninstall, and delete all of my mods and completely restart.

 

 

 

 

[Inazuma22]

The same thing happened to me when i reached 130 mods. The game was like NOPE and dident load any textures so i deleted like 20 mods and that fixed it. You only had like 70 mods and took away 40 so it should of fixed it self. Oh and btw if you just disalbed the mods in mod manager that might not work. try deleting all the ems/esps and stuff for the mod aswell.

[deangame2]

Update, I deleted the meshes and textures folder (around 22gigs) and I ran the game, everything went back to normal.

 

Now the real problem is finding out how much memory I can have in the data folder. Unfortunate but what can you do.

[deangame2]

Update:

 

Fixed it, turns out it was a combo of too many mods and an archive invalidation error.

 

It turns out there was a complication of using both FOMM's Archive Invalidated AND NMM's Archive Invalidated. Turned on FOMM, Deactivated it and actived NMM's everything seems to work now.

 

For now...until I screw it up again heh.