Just had STEAM update FalloutNV.exe to 1.1.1.280 and ArchiveInvalidationInvalidated seems to be broke again.

Had it working fine for 6 days by manually adding it to the Fallout_default.ini file.

Now after the update, CTD from launcher unless I remove the ArchiveInvalidationInvalidated!.bsa entry.

The damned Steam auto-update screwed up what has otherwise been a fine game & mod experience. I don't understand why Bethesda got into bed with Steam in the first place. The entire reason many of us purchased FONV in the first place was so we could mod it... Steam SUX!

There is some disscusion about it http://www.thenexusforums.com/index.php?/topic/255381-fallout-new-vegas-archiveinvalidation-invalidated-endorsemants/page__st__140. See post #147. Seems we have to edit the .bsa entries in a certain order now.

Ah, excellent. Thanks Maedhros.

(The solution is to put some other .bsa file other than AII.bsa in the front position, such as the Meshes or Voices file. Just make sure AII.bsa is before the texture BSAs and you should be golden)

From those posts it seems the invalidation.bsa must be loaded after meshes.bsa?

Thanks Maedhros_the_6th for the pointer to the discussion.

I modified the line Fallout_in the default.ini file to be SArchiveList=Fallout - Voices1.bsa, Fallout - Sound.bsa, Fallout - Misc.bsa, AII-FNV!.bsa, Fallout - Textures.bsa, Fallout - Textures2.bsa, Fallout - Meshes.bsa

This series worked, FYI - I also tried adding it last and it did not work.

I think the key is to have the Invalidation.bsa load before the texture .bsa's and meshes.bsa, right after misc.bsa

I can't express in words allowed on this forum how I felt after a long day at work and the game CTD on launch because of this. It took a while before I found one of these threads. Very very very very very angering. :flamethrower: :thumbsdown: :banghead: :brokencomputer:

Before textures, but not first. The way I always had it.

I was able to place it as the first bsa in SArchiveList with the latest patch simply by renaming it...

I renamed my "ArchiveInvalidationInvalidated!.bsa" file in the Data folder to "Fallout - ArchiveInvalidation.bsa" and added it as the first bsa in the SArchiveList just like i always had it, I have no issues running the game with it.

Example: SArchiveList=Fallout - ArchiveInvalidation.bsa, Fallout - Textures.bsa, Fallout - Textures2.bsa, Fallout - Meshes.bsa, Fallout - Voices1.bsa, Fallout - Sound.bsa, Fallout - Misc.bsa

I must be the odd one out as no matter where I put mine, or what I named it to it wasn't working. I could instantly tell as I have a pipboy texture replacer and it wasn't its usual jet black. Oddly enough my body and face textures were fine. Just the pipboy was back to that horrid plasticky-look.
I don't have a whole lot of texture replacers so the not recommended archiveinvalidation.txt file will do for now.

i havent installed the new patch., i've had a similar problem with a body replacer, all other texturmods were fine but this one works only if the ini changes are also added to the falloutprefs.ini, perhaps this works also with your pipboy, give it a try,





Could this little "!" really be the real problem, anyone can confirm this?

Not sure if it's the "!" or the rename to "Fallout -", but doing this does work, and allows the fake bsa to be first in the list without crashing the game.

I don't think so; renamed mine to AII.bsa, first in list, game doesn't load. Move the misc.bsa to the front - works fine.

Has anyone confirmed whether it is necessary anymore? AII! was a hack to exploit a flaw in the GameBryo engine. I'd think that the "Load Loose Files" option should have made it unnecessary in the first place, but maybe Bethesda is actually working on fixing the error that made the hack necessary in the first place?

Could be. But, I doubt it. :whistling:

Whats Beth messing up their own game have to do with Steam?
And you can turn off the autoupdates, you realize, right?

In the words of Heavy Weapons Guy: "Cry some more!"

I'm going to agree. This isn't a Steam problem. It's a patch problem. The only issue is Steam doing the auto-update without user intervention. That can be turned off.

To summarize the fixes though, in no particular order (and I have tested both) -
1) Rename your fake BSA to - "Fallout - ArchiveInvalidation.bsa". Update the ini files to reflect this change. This will allow the fake .bsa to be the first on the SArchiveList entry.
2) Change the order of the .bsa files in the SArchiveList. I put "Fallout - Voices1.bsa" as the first entry, then the fake .bsa, then the rest of the line.

Both of those do work. I put it into the fallout_default.ini file and it did overwrite the fallout.ini file in the My Documents\My Games\FalloutNV directory.

Edit: I'm using the first option myself as this will hopefully stop any other issues down the road with loading this list (knock on wood)

thats weird everyone having a problem the only issue i had with the update is NVSE not working but that was also updated now everything is fine for me , i didnt have to change anything and i use I invalidated

God thanks I was able to follow this thread on my job. But henstly, what did they thought they where doing? Don't they know we're using archiveinvaldation and NVSE. However...



...I can confirm the first tactic is working, with NVSE enabled, and I recommend using that incase the next patch messes up archiveinvalidation again, so you only have to rename it.

First- You would have updated anyways.
Second- OBSIDIAN not bethesda
Third- It was either steam or microsoft and look what happened Microsoft got their hands on the game DLC exclusive to the xbox.

That's not entirely correct, it's Bethesda that handles the business decisions side of things, which also means that they get to decide whether their game engine bundles in with Steam or Games for Windows Live. Still, I suspect that Obsidian urged them to go with Steam, and in my opinion, they made the right choice. Games for Windows Live is frankly a steaming pile of cack, at least Steam is functional, even if it does suffer the odd bout of eccentricity.

Anyway, as for ArchiveInvalidationInvalidated, it still works! I can still use it, anyway, I just renamed the file in the INI and in my Data folder from ArchiveInvalidationInvalidated.bsa to Fallout - AII.bsa. Then it worked perfectly.