

I tried disabling and enabling Auto Archive Invalidation, using the Archive Invalidation Invalidated mod with Auto Archive Invalidation off and on but nothing seemed to fix this. Some textures just wouldn't show up no matter what I did. I installed some basic UI mods which worked just fine, but it's when I started installing texture mods that I noticed something strange. Going through the MO tutorial I enabled Auto Archive Invalidation and copied the default profile making my own.


I installed MO to the default location of program files(x86)\Mod Organizer which I know realize was a bad idea. I saw a video about MO and decided to use that instead. I started up NMM and I told it where to find the newly installed New Vegas. After that, I saw all my old mods that I had previously installed and still had Archive Invalidation enabled. I completely uninstalled and reinstalled New Vegas, started it vanilla and exited. So after using Nexus Mod Manager ( NMM) for a long time I decided to use Mod Organizer ( MO) v1.3.8 to install my mods later.
