Archive invalidation switching wastelands

Post by **Bielgee** » Sun May 17, 2015 5:07 pm

Hello so I have nmc for both nv and fo3 but whenever I switch wastelands I have to uninstall and reinstall nmc because everything goes invalidated re toggling archive invalidation does nothing also if I go into the game without nmc everything that used nmc textures in invalidated any way to fix this ps using my iPad so forgive grammar

Post by **Bielgee** » Sun May 17, 2015 5:51 pm

Update: even uninstalling and reinstalling nmc doesn't work anymore everything is invalidated

Post by **RoyBatty** » Sun May 17, 2015 7:31 pm

One other person has reported this issue, we have no idea what causes it. I am sorry.

Post by **Bielgee** » Sun May 17, 2015 8:00 pm

Dont be sorry its not like it was your fault

maybe when my game switches from fo3 nmc to nv nmc it freaks out if this is the case how would i go about removing the fallout 3 nmc

Post by **AlMustansir** » Sun May 17, 2015 10:08 pm

I do have this issue too mate ! Started a new game in the mojave to check out some texture stuff and enbs to finally start a new playthrough. Especially road textures seem to stay vanilla and i tried a lot of different textures...

I tried to archive invalidate wiht fomm too through MO but no luck at all. Kinda frustrating...

Post by **mayoko** » Mon May 18, 2015 8:30 am

if you're using MO you need to move the fallout - invalidation.bsa that MO creates and incorrectly places in the main folder and move it to the Data folder. Also consider making a new profile under MO and selecting default new game settings. Sometimes the remanents of older AI fixes can cause issues. Also make sure your .ini files under profiles in MO are not read only as well as the ones in the typical locations. Hope that helps.

Also enable the bsa management option, also organize the install packages in the correct order, (yes even the official game files as this order is highly relevant to texture overrides.)

Post by **RoyBatty** » Mon May 18, 2015 11:46 am

MO was updated yesterday to 1.3.5 and supposedly that bug was fixed.

Post by **Bielgee** » Thu May 21, 2015 12:55 am

thank you the issue has been resolved