Sorry to be so simple with this. I've spent a lot of time (without much luck) trying to get this game to work right. Perhaps this info will help others as well.

So the final process to play FO3 with OA and still have Vats working correctly is:

1) Install FO3
2) Patch using v 1.0.0.15 (as linked on the first page)
3) Copy the 1.0.0.15 exe and the Fallout 3.esm to another folder.
4) Patch to v1.1
5) Replace the exe and esm files back to the install folder.
6) Copy the Fake Patch esm into my Data folder
7) Install the Unofficial FO3 patch from the Nexus site
8) Install Operation Anchorage
9) Using FMM, Launch order should be: Fallout3.esm -> FakePatch_v1.4.0.6.esm -> Unofficial Fallout 3 Patch.esp -> OA.esm

And this will give me FO3 with Vats working and access to OA?

Bingo! If you've already gotten O:A, you can skip 1.1 entirely.

Ok, that doesn't work exactly as it should.

I followed my steps listed. FO3 works perfectly. However, OA does not.

OA never shows up in my quests if I use the 1.0.0.15 exe. It only shows up if I use the 1.1 exe.

If I load the 1.1 exe, let the quest activate then save. Then load the 1.0.0.15 exe, the OA quest is there, but it's so glitched it can't be played.

How are you getting OA to work properly, and still have Vats working correctly?

Try starting a new game? Are your O:A files in Fallout3\Data? There were a ton of people who had the same problem getting the O:A signal/quest update even using 1.1, so try a new game or ~StartQuest DLC02oa1. If you've updated to 1.1, there might be remnants of it messing with you. If all else fails, reinstall FO3 (which won't delete Anchorage.esm or the O:A .bsa's or your mods) and update ONLY to v.1.0.0.15. I got the signal and update witin a minute of walking out the door...

http://www.gamesas.com/bgsforums/index.php?showtopic=959505&st=0&p=13872813&#entry13872813 is how I have my O:A set up and it's working with the described 0.15/Fake Patch setup.

Well, odd problem. I was messing with my data folder and accidentally moved my saved old(or new? lol) 1.1 .esm into my data folder(it was a brain fart moment, don't ask) and I just thought I'd redo everything to make sure I could have working VATS. Uninstalled FO3, reinstalled and then updated to the 0.15 patch. It got interrupted partially through, but I thought nothing of it, went and did another fresh reinstall to compensate for the first fudged patching, and now the game wont even get to the title screen on vanilla. I launch with a fresh install from the disk(fully fresh directory too so no remnants in the data folder) and it CTD's as soon as I start seeing slides.

I have one more thing I am going to try(lol, restore point) and if that doesn't work then it looks like my FO3 days are numbered.


Edit: wow, when windows messes something up, they really like to mess it up hard. I just completed a system restore to yesterday when I installed winLame to alter some sound files for my mod, and every single folder that I had touched got deleted by windows since then. My documents is empty, my fallout 3 data, saves, half my programs are gone, all of my mod zips are gone, everything from my installer folder is gone.

How many people want to place some bets on whether or not FreeUndelete can restore any of my stuff?

Also, I am so depressed now(since my only mod I have been working on may be gone now) I am going to go drink some beer until this is done "undeleting" stuff.

The "startquest DLC02oa1" command didn't work in my game. I can still go to Bailey's Crossroads, but the map is f**ked up as I can see some objects that should be only seen in GECK floating around. It looks like the 1.0.0.15 exe didn't load the data from OA bsa correctly. Guess I should reinstall FO3 again to see if I can use OA bsa, since now I'm using 1.0.0.15 exe + 1.4.0.6 esm combo (I don't have the mouse problem with this combo). I personally don't believe that all the OA problems I got is because of esm version, but well, nothing impossible... :\
BTW, I use FOMM's ArchiveInvalidationInvalidated!.bsa, not the old txt method. It's a reliable solution too.

Why did you mess with it when you had it right? Something tells me you've over complicated things. Sounds like the interrupted patch must have been the hold up or your system restore most likely? Just having your 1.1 esm in your data folder and starting with the 1.0.0.15 exe will only cause the no mouse on startup, but won't cause any severe system issues. I tested with all four .esm versions and 1.0.0.15 works best, but having the others in its stead did NOT cause any issues with anything but Fallout 3. Make a fresh install after uninstalling from your control panel and just opt to keep your saves. Also, I had something similar happen with the crash on startup which was remedied by renaming the Fallout3.ini and FalloutPrefs.ini files and letting the launcher make new ones.

The more I think about it, the more I'm convinced you goofed by doing the system restore if you hadn't made a restore point while you had everything working.

Use the matching .esm as described. I've A) Gotten the signal and Quest update upon exiting Vault 101 and B) Activated the sim chair and played in the snow with things set up as described (there were no displaced objects). Like the OP states, the 1.0.0.15 .esm works best with the 1.0.0.15 .exe.

I had a brain fart and put the wrong .esm in my backup folder(the one from my saved data folder, not the one from my new install) so when I went through and have everything back in the FO3 folder, instead of putting the right esm in I had the 1.1 esm. That is when the reinstall happened with the fudged patch and now my entire FO3 has gone to hell(got my mod's .esp back though, now I just have to figure out why FO3 doesn't want to work right).


Edit: found my problem, the setup didn't want to launch so I couldn't uninstall/repair Fo3. So I just had to execute it myself from my disk. This has been fun and I certainly hope to never have to do it again <_<

I see you Dan Ross......

Will this fix be in the next patch?

Glad to hear you found your problem. When you get everything set back up, you should make a new restore point. I'll bet anything the untimely system restore had borked your install.

I'm having the same problem. When trying to do OA and use the 1.0.0.15 exe i see things that I shouldn't be seeing (giant red exclamation marks) and walls/steps/npcs missing.

When I replace with the 1.1 exe, everything is normal. This is also when starting a new game. And yes, I'm absolutely sure the files are in the right place ( how could it work with the 1.1 exe if it wasn't ? )

With that done, and on the previous advice, here's what I've just done:

- Complete uninstall of FO3 and everything related. Ensured the install folder is deleted along with anything in the My Documents folder.
- Installed FO3. Only patched to 1.0.0.15. Installed OA. OA never shows up in quests after playing outside for 30min (new game).

However, I can patch up to 1.1, and OA shows up almost immediately when loading my game ( or starting a new game ).

Conclusion: OA has to be run on 1.1 for it to work (properly). However Vats is broken like this.

This is so frustrating...

Edit: Also the "startquest DLC02oa1" command doesn't work for me either.

You're doing something wrong then, as I've just started a brand new 1.0.0.15 game, exited the Vault, got the radio signal, then the quest update, went straight to Bailey's Crossroads, put on the sim suit, sat in the chair, and BAM, Anchorage Cliffs, all with 1.0.0.15! I did, however, have the floating trees for the first time ever when coming to at the beginning of the sim, which was remedied by reloading the game and activating the chair again. I insist, O:A DOES work w/ 1.0.0.15's exe and .esm.

How did you install O:A?
Which version is the save you're testing with?
Are you auto logged into LIVE?
Do you accidentally have the DLC in both your AppData AND Data folders?
Have you let your launcher make new .ini's?

We'll get to the bottom of it, but there's something holding you up, I'm just not sure what it is yet.

I'm currently testing adding and removing perks and targeting a Chinese Soldier with 1.0.0.15 VATS in the sim.

Commando: Player.AddPerk 99828 PASS
Concentrated Fire: Player.AddPerk 44CAF PASS
Gunslinger: Player.AddPerk 94EBB PASS
Wired Reflexes: Player.AddPerk 24D5C PASS
Sniper: Player.AddPerk 31DB4 PASS

Are there any other perks I should check?

Ok, here's an example that may explain what I'm dealing with here.

[img]http://i62.photobucket.com/albums/h92/pretikewl/FO3/ScreenShot5.jpg[/img]

For more pics, see http://s62.photobucket.com/albums/h92/pretikewl/FO3/

I did a new install of FO3. I only patched up to 1.0.0.15. I installed OA. FMM shows it active.

For some reason OA will only show up when I patch to 1.1. GRRR!

On the upside, I can play FO3 with no problems, so kudos on that :celebration:

The !'s are missing meshes. Rename your meshes folder ;Meshes, load the game and let it use the archived O:A files? Everything else looked in order. Maybe the internal structure of your extracted meshes folder is faulty? :shrug:

FOMM picture includes OA esm
but not OA esp

did you forget to move a file?

There is no Anchorage.esp

Renamed my Meshes folder to ;Meshes = same result. Big red ! in the same places. Also, I got the same result before I even did a clean install of FO3.

The only "fix" that works is to use the 1.1 exe. When I use it, everything is exactly where it should be and normal (aside from Vats being broken).

This may just be an OA + FO3 issue. FO3 works great with the fixes provided. But it doesn't make sense that a 'vanilla' install of FO3 + OA, and OA never shows up.

I can live without OA, but it's just annoying that I'm 99% there for having the game work fully and missing this one tiny part.


And btw, I really appreciate the responses and effort to helping me get this issue fixed. It's people like you that make the gaming community a nice place to be.

You shouldn't have to compromise O:A for VATS. It's still really confusing me that your meshes aren't showing up when using the 1.0.0.15 exe yet they are when you use the 1.1.0.35!o_0 Had you tried a brand new game? I remember a few posts in the Hardware/Software about that http://www.gamesas.com/bgsforums/index.php?showtopic=955989&hl=exclamation+points http://www.gamesas.com/bgsforums/index.php?s=&showtopic=948894&view=findpost&p=13717952 w/ O:A but happening even with the 1.1 patch fully installed. Have you let the 1.0.0.15 launcher make new .ini files for you?

Documents\Games\Fallout3\

Don't give up on O:A just yet, as there's bound to be one little detail we're overlooking somewhere.
Garsh! Thanks, and I really do hope we can get your O:A working right with the VATS and everything.


Also, did you change the name of the Xlive folder in Application Data after copying/moving the three DLC files? If you have the DLC content in both places and haven't renamed (;Xlive) that folder, it causes problems.

~ResetQuest DLC02oa1?

Yes, all new .ini's
Yes, new game. (all my old saves are in a diff folder)

And I don't understand what you mean by changing the name from the Xlive folder?
The 3 files I have are: Anchorage - Main.bsa, Anchorage - Sounds.bsa, and Anchorage.esm ( am i missing something? )

Btw, I just did a new clean install of FO3 v1.0.0.12, no patches. Copied the OA files to the Data folder. Made sure the OA box was checked in the launcher. Started new game and no OA shows up.

*Hidden
Windows Vista: C:\Users\{UserNameHere}\*AppData\Local\Microsoft\Xlive\DLC...
Windows XP: C:\Documents and Settings\Users\{UserNameHere}\*Local Settings\*Application Data\Microsoft\Xlive\DLC...
To see hidden files/folders: Control panel -> Folder Options -> View -> Show Hidden Files [√]

That's the location LIVE originally downloads the DLC content to and where the game plays it from if you're logged into GFWL while playing. Since they're in your Data folder, you want to be certain that Xlive folder is renamed.
Save in a folder titled "1.0.0.12" copies of the Fallout.esm and Fallout3.exe then run the 1.0.0.15 patch and you should have the same results (O:A working fine) with FOSE compatibility along with the official fixes included in the Fake Patch.

Compromise nothing!

I've tried that. From the .12 install, i copied the exe and esm to a diff folder. Updtaed to .15. OA still doesn't show up

I can only get OA to show up when I update to 1.1

It really makes no sense...

btw, check your pm's

Uh, it's good to see there's other people that has the same problem like me. Thank you for trying the reinstall & result, Pretikewl. I think we might need more result from people to determine if it's because of esm version.

Just a thought, JustinOther. Do you always install FOSE? Maybe the problem/fix has something to do with FOSE I guess. When I installed FOSE with the "wrong" combo, I can get the Outcasts singal normally (and "startquest dlc02oa1" can be executed without any error message in console). But there are still weird objects on the new maps. I'll do more test when I back from work.

Odd.o_0 http://www.gamesas.com/bgsforums/index.php?s=&showtopic=959505&view=findpost&p=13872813's exactly how I've got my O:A set up and working. Of course, ignore the first part since you've already got the O:A files.

As in typical Bethesda fasion they only implemented esm\esp loading of BSA's when THEY needed it (for the release of OA in v1.1), so what does that mean? it means if you are using the v1.0 exe you have to add Operation Anchorage's BSA's to the SArchiveList in fallout.ini.