Crash at startup when editing Fallout.ini

[SteveE22]

So in order to use some replacement mods, one must edit the Fallout.ini located in My Documents/My Games/Fallout3 by changing the value for bInvalidateOlderFiles to equal 1, right? However, if I do this, Fallout 3 goes off and has a conniption and crashes its little old self to the desktop when I try to fire it up, never even making it to the main menu. I go back into Fallout.ini, change the value back to 0, and the game runs fine, even if all the same mods are being used.

 

I've tried using the ArchiveInvalidation Invalidator, FOMM, and the ArchiveInvalidation creator, all with no luck.

 

I wouldn't really care except I decided to download the excellent Vault 89 mod, and everytime I look at the doors in that place they get all freaky and start displaying random textures tiled on their surfaces, changing the texture with each major angle change. It's kinda've annoying and disimmersive (or however you say it.)

 

I was wondering if anybody knew any workarounds/solutions/prayers/etc... for this issue? I can't seem to find one no matter where I search. Of course, I may just be blind, for which I hope you can forgive me.

 

Anyway... yeah, any suggestions?

[ibot_bob]

Are you sure your changing the correct value? You could be changing the one.

[SteveE22]

Yup, all I changed was:

 

bInvalidateOlderFiles=0

 

to:

 

bInvalidateOlderFiles=1

 

And it freaks out. My game seems to only like it when the value is 0.

[Khet]

Few things first. Are you launching Fallout directly, using the Fallout Launcher, or using FOMM?

 

Secondly, are you running the latest patch or not?

 

Third, have you tried running the game with NO mods activated but still have bInvalidateOlderFiles=1 in the ini?

 

Fourth, how much are you willing to pay me for helping?

[SteveE22]

Few things first. Are you launching Fallout directly, using the Fallout Launcher, or using FOMM?

 

I haven't tried launching Fallout directly, but I have used the Launcher and have been using FOMM.

 

Secondly, are you running the latest patch or not?

 

Yeah, I got the latest patch before my computer was even able to run the game (had to upgrade my outdated graphics card).

 

Third, have you tried running the game with NO mods activated but still have bInvalidateOlderFiles=1 in the ini?

 

Yep. Tried that a little bit before making this post, so as to avoid appearing as dumb as I really am. ;)

 

Fourth, how much are you willing to pay me for helping?

 

I can pay you in terrible jokes?

[Khet]

Terrible jokes are better than nothing. Have you changed ANYTHING else in the ini? I don't care what it is, I want to know. bInvalidate shouldn't be crashing... you've said you tried other methods of invalidation (ArchiveInvalidated) and all that?

 

Have you tried the ArchiveInvalidation text doc method? Make a text documents in your DATA folder, name it ArchiveInvalidation (I believe) and then manually type in the paths to the new files. Many of the retextures that were released before we have the GECK will explain exactly how you do this.

 

Let me know if you can launch after trying that method.

 

Edit: Just thought of something. Back up any saves/mods you have installed, then reinstall Fallout, get FOMM then enable archive invalidation through that and DON'T touch anything else. Restore saves/mods and then try launching.

[spineynorman]

are you running Windows Vista?

[Khet]

I don't see why Vista would matter. UAC is easily avoided/disabled, besides it shouldn't be causing a complete crash, and from what I understand from the OP other mods were used successfully, just not texture replacers and the like.

[SteveE22]

What kind of car does Luke Skywalker drive?

A Toyota!

 

So I backed all the mods and save files up, and tried a clean install, then tried using FOMM's invalidation. Didn't touch anything else. Tried running the game, but to no avail! Fallout hates me for toggling invalidation through FOMM.

 

So I re-toggled the invalidation through FOMM (this seems to have the effect of resetting bInvalidateOlderFiles to 0 again, though it does not replace the ArchiveInvalidation.txt) and created a new ArchiveInvalidation.txt through the utility available here on the Nexus. Then I manually turned bInvalidateOlderFiles to 1. I still haven't copied the save files or mods back to Fallout 3. I tried running it again and get to the first image on the opening "projector" but it still crashes before I reach the next frame, nevermind the main menu. Fallout 3 still hates me.

 

I'm also running XP, because Vista doesn't do what I need it to on the programs I need.

[Khet]

Curiouser and curiouser....

 

I'm starting to run out of ideas here. Only thing I can really think of is reinstall one more time and change bInvalidate in the ini, once again doing nothing else and then launching the game. Perhaps FOMM is actually causing a problem when setting the invalidate. And unless I think of something between now and your response I'm out of ideas.