[RELz] Fake Patch! : Fallout 3

» Fri Apr 01, 2011 7:56 pm

So, does the Official 1.1 patch need to be be used before the unofficial patch?

» Fri Apr 01, 2011 7:54 pm

Phew!

Thanks for the hard work in working toward a fix, but the installation looks a bit confusing.

Could you maybe put together a walk-through for those not too familiar with the technical end of fallout 3?

» Sat Apr 02, 2011 4:10 am

wait... does this mean that if I get my lovely bought data from GFWL folder and put it on DATA, I can play O:A with 1.0.0.15 stright away with no patch? you know... I don't give a s**t about GFWL...

Yes and yes!

Well maybe I didn't notice with the older patches...but I get HDR flicker with the new patch

Here is a video

also the % chance to hit with VATS is lower (most likely due to the fact that no VATS perks work) and you can NOT hit grenades/missiles mid-air anymore...the chance to hit is 0%
Has anyone confirmed that the newer Patches truely affect SLI? If there is no difference, then I want to revert back...but if reverting back and using "Fake Patch" will "break" my SLI then I will skip this.

hope someone can shed some insight on this, I would love to have normal VATS again,
TheDamned

I'm not certain as I've only one video card, but Martigen seemed uninterested in this only because the 1.1 patch fixed a SLI issue, so my impression is that the newer patches did, in fact, improve SLI performance somehow. Might still be worth investigating, but I won't be able to as I'm broke as a joke and can't currently afford a second card/SLI motherboard.

I have a suggestion. You guys previously said that there is a "fix" for sli in the new 1.1 exe?
How about making a fake 1.1 or fake 1.4 exe that removes these "sli" fixes and make it almost look like 1.0, but is compatible with DLC

Currently, opening the .exe's, examining their guts, comparing/contrasting, and making a definitive .exe is beyond my abilities. I can learn if anyone wants to point me in the right direction... Chances are though that Bethesda's next patch and .exe will have all of the best from all four currently available .exe's and that the next patch will be out soonish anyway. Maybe it's easier than I'd anticipate though? If there's a will, there's a way?

So, does the Official 1.1 patch need to be be used before the unofficial patch?

No. However you might need to let patch 1.1 fully install and update LIVE to get O:A and to 1.4 to get the Pitt, but after acquiring the content and moving it to Data, you can uninstall/reinstall/patch to 1.0.0.15 and skip 1.1 and 1.4 entirely, provided the newer patches aren't needed for the SLI fix in your case.

Just to post something odd, I am having a VATS glitch. Not as severe as the one from the patch, but for some odd reason anytime an enemy is past ~15 steps or so away from me my vats % drops dramatically. I can achieve a %95 at up to about eight steps, but it starts to degrade past that. I am using sniper and commando perks and testing using Lincoln's repeater and the Xuanlong. Pretty much every time an enemy is at 15 or more steps from me the head and torso drop down to single digits while the legs and sometimes arms stay in double digits similar to the patched version of the game.

I moved all of the contents of my data folder, uninstalled FO3, reinstalled, updated to the 1.0.0.15, moved my .exe and my fallout .esm, moved my original data folder back, used a copy of my new 1.0.0.15 .esm to overwrite the one in my data folder, put my .exe back(while saving a copy) and then reinstalled FOSE and FOMM(and archive anvalidated! everything) and then installed the fake patch. Did I do this wrong or is there something just "weird" going on?

If it helps I can post my load order.

Try, to eliminate possibilities, loading a save without any mods running to ensure that there isn't any interference from edited records contained in any of your mods. I know I was targeting ant torsos and antennae from further distances last night, but hadn't tested with the perks... After answering more replies, I'll ~hook myself up and test the perks, then report my findings here.

Edit: I see there's already some experimenting going on and will try as well with/without perks and using pre/post 1.1 saves. If the VATS issues could somehow be fixed by doctoring saves, maybe that's where the solution to all this lies? If it's so, maybe a save updater utility could be made by a programmer or even added to the official patches themselves?

» Fri Apr 01, 2011 7:13 pm

You should answer my question, it's pretty important.

» Sat Apr 02, 2011 1:51 am

You should answer my question, it's pretty important.

re-read post directly above yours.

» Fri Apr 01, 2011 10:34 pm

Thanks Fonger!
I still have a problem that I need good expert help with.

I cannot change my .exe version

I have version 1.0.0.12

When I try to update the game to Fallout 3 with the 1.0.0.35 patch, and it stops on the first file and says:
"Old file not found, however, a file of the same name was found. No update done since file contents do not match"'
(This is for fallout3.exe, fallout3.exe.cat, fallout3.exe.cfg, FalloutLauncher.exe, and Readme.txt)

So when I try to load fose_loader.exe , a message comes up saying " you have the original version of Fallout, please patch it to the latest version.."

I dont know what to do now :/

» Sat Apr 02, 2011 1:30 am

Have you tried a clean install? Took me <10 mins to do it this second time around, and apparently I did do something wrong because VATS works fine now.

» Sat Apr 02, 2011 1:47 am

The install is not the problem obviously,
I bought my copy from Steam [ build 1.0.0.12 (the original pre-patch version of Fallout) ]

EDIT: I just updated the game to 1.4 using the patch from the Bethesda website, and it is still not working.
I'm guessing this is because patch 1.4 doesn't change the fallout3.exe file.

» Fri Apr 01, 2011 10:55 pm

I dont know what to do now :/

Try uninstalling and reinstalling, then running only the 1.0.0.15 official patch and then bridging the gap to 1.4.0.6 w/ PakePatch. I'm not certain, but I don't think the patch .exe's will let you patch backwards, so you have to wipe the slate clean first. Uninstalling/Reinstalling won't delete your mods or anything, just be sure to say no when asked if you want to delete your saves and they'll also be left for use after reinstallation. IF you have problems getting Fallout to load after patching, back up or rename your .ini files (in your documents) and let the game make new ones by starting it once with the launcher.

I'm guessing this is because patch 1.4 doesn't change the fallout3.exe file.

It does make a new .exe. I'm using a store bought disc, but I'd imagine the steam version also has a launcher which will make new .ini's in the event they're needed?

» Sat Apr 02, 2011 12:42 am

Ok, I dont think that you understand.
When I install a clean slate,
the default installed version of fallout3.exe is 1.0.0.12

Now when I try to patch that with 1.0.0.15 patch (Fallout3_v1.0.0.15_EnglisS.exe)
It says "Old file not found, however, a file of the same name was found. No update done since file contents do not match".

Therefore, I cant run any patches that change fallout3.exe

» Sat Apr 02, 2011 6:38 am

Ok, I dont think that you understand.
When I install a clean slate,
the default installed version of fallout3.exe is 1.0.0.12

Now when I try to patch that with 1.0.0.15 patch (Fallout3_v1.0.0.15_EnglisS.exe)
It says "Old file not found, however, a file of the same name was found. No update done since file contents do not match".

Therefore, I cant run any patches that change fallout3.exe

I'm not familiar with the steam setup, but there is bound to be an officially supported method of patching an initial install, right? Maybe there's a trick w/ the steam version to be found in the Hardware/Software forum. I'll go digging, but I've a few other matters to attend to first.

Also, for some reason FileFront shortened the name of the file to "Fallout3_v1.0.0.15_EnglisS.exe" when it's supposed to be "Fallout3_v1.0.0.15_English_US.exe" o_0 Works nonetheless...

Have you tried a clean install? Took me <10 mins to do it this second time around, and apparently I did do something wrong because VATS works fine now.

So evidently the saves aren't the issue!?! That shoots down the thought of being able to update to 1.4 and somehow getting the old VATS back by just doctoring saves, but it's good news. Thanks for verifying this and posting your findings.

» Fri Apr 01, 2011 3:10 pm

I have a question. Will any mods experience an incompatibility due to the lower version number? (such as ones I've made myself with the GECK recently)

» Sat Apr 02, 2011 3:48 am

I have a question. Will any mods experience an incompatibility due to the lower version number? (such as ones I've made myself with the GECK recently)

I highly doubt it. All of mine are running fine and you shouldn't have any conflicts. Open everything you're running in FO3Edit if you want to check. For instance, if ModX (made before 1.1) has a reference to the Megaton worldspace, the safety net will be removed as the "Do not allow NPC fall damage" flag will be removed by ModX. Open all of the FakePatch tree and make sure A) That its records aren't being overriden and B) That it's not overwriting any records from other esm's/esp's you might be using. If there are any conflicts, you can easily solve them by dragging the appropriate values from one file to another.

» Sat Apr 02, 2011 2:20 am

I have a strong suspicion that once a savegame that has been "compromised" with patch 1.1 or 1.4 it will never return "clean" even by reverting to 1.01 and the fake patch.

So, that leaves open the possibility that someone can figure out what it is in a compromised savegame that makes it unclean, and then write a savegame cleaner app, right?

» Sat Apr 02, 2011 2:55 am

OK, this looks awesome!

Here's my list of Five Things That The Patches Broke.
I'd like to verify which are fixed, which are not.

1. Mouse acceleration in menus. - Looks like this would be fixed by this, since the user isn't stuck with the latest .exe
2. Vats takes seconds to load. - Same. Shouldn't be there if using the old exe, right?
3. Vats accuracy way broken. - Same.
4. Sniper and other vats accuracy perks broken. - Same, right? Old perks fixed?
5. Ninja perk broken still. - this is the one I am curious about, was it broken right out of the box that it doesn't give the +15%? Is this tinkered with in anyway?

Tempted to go ahead and see if the DLC works with this. Not like the new patches give anything I give a [censored] about other than the right to download the new DLC. The esm files, yes, but the futzed exes make my cats cry. Really, you should see them. Poor kittens.

» Fri Apr 01, 2011 8:41 pm

I don't get the OA/DLC... ok, I must backup the vanilla .exe right ? But what's that 'and .esm in a folder containing the patch itself named after the version. ' about ??

» Fri Apr 01, 2011 11:49 pm

So, that leaves open the possibility that someone can figure out what it is in a compromised savegame that makes it unclean, and then write a savegame cleaner app, right?

Have you tried a clean install? Took me <10 mins to do it this second time around, and apparently I did do something wrong because VATS works fine now.

It seems as though it's not a savegame issue since VATS works fine so long as 1.0.0.15 is the only official patch installed.

» Sat Apr 02, 2011 3:25 am

answered in first post

the 1.0 patch.

Ok, I'm a bit of noob here myself with this. So just so I have this straight...

1) Install FO3
2) Patch using v 1.0.0.15 (as linked on the first page)
3) Copy the Fake Patch esm into my Data folder
4) Install the Unofficial FO3 patch from the Nexus site
5) Install Operation Anchorage
6) Using FMM, Launch order should be: Fallout3.esm -> FakePatch_v1.4.0.6.esm -> Unofficial Fallout 3 Patch.esp

And everything should work using VATS, right? Also I can use the DLC?

If I have the order wrong or am missing a step, please correct me.

» Sat Apr 02, 2011 7:00 am

OK, this looks awesome!

Here's my list of Five Things That The Patches Broke.
I'd like to verify which are fixed, which are not.

1. Mouse acceleration in menus. - Looks like this would be fixed by this, since the user isn't stuck with the latest .exe
2. Vats takes seconds to load. - Same. Shouldn't be there if using the old exe, right?
3. Vats accuracy way broken. - Same.
4. Sniper and other vats accuracy perks broken. - Same, right? Old perks fixed?
5. Ninja perk broken still. - this is the one I am curious about, was it broken right out of the box that it doesn't give the +15%? Is this tinkered with in anyway?

Tempted to go ahead and see if the DLC works with this. Not like the new patches give anything I give a [censored] about other than the right to download the new DLC. The esm files, yes, but the futzed exes make my cats cry. Really, you should see them. Poor kittens.

All of the above should be restored to their original condition and the DLC (at least O:A) does work with the fake patch plugin. I have Anchorage.esm and both .bsa's in my Data folder though, so I'm not sure how things would work out with DLC if it's left in AppData...

I don't get the OA/DLC... ok, I must backup the vanilla .exe right ? But what's that 'and .esm in a folder containing the patch itself named after the version. ' about ??

You don't really have to back up the Vanilla .exe or .esm. I saved them to have an easy way to compare/contrast and test them, but you only really need the 1.0.0.15 exe and esm. Just hold on to the v_1.0.0.15 patch in case you ever need it again.

Ok, I'm a bit of noob here myself with this. So just so I have this straight...

1) Install FO3
2) Patch using v 1.0.0.15 (as linked on the first page)
3) Copy the Fake Patch esm into my Data folder
4) Install the Unofficial FO3 patch from the Nexus site
5) *Install Operation Anchorage
6) Using FOMM, Launch order should be: Fallout3.esm -> *FakePatch_v1.4.0.6.esm -> Unofficial Fallout 3 Patch.esp

And everything should work using VATS, right? Also I can use the DLC?

If I have the order wrong or am missing a step, please correct me.

*To get Anchorage, you might need to have updated to 1.1, if only temporarily, as 1.1 updates that GFWL marketplace. If you've previously updated to 1.1, you might still be able to buy The Pitt using your 1.0.0.15 setup.
*If you do get the DLC's and are going to use FOSE or end up moving the three files to your Fallout3\Data folder, load FakePatch_v1.4.0.6.esm right before Anchorage.esm instead.

Other than that, you should be good to go.

» Sat Apr 02, 2011 1:42 am

*If you do get the DLC's and are going to use FOSE or end up moving the three files to your Fallout3\Data folder, load FakePatch_v1.4.0.6.esm right before Anchorage.esm instead.

Sorry, but I can't play DLC with their BSAs with 1.0.0.15 exe. I have to extract all the data from DLC BSAs to Fallout3\Data folder and activate the "archive invalidation" in FOMM. I don't know if there's only I got the problem? (this "extract" one and the "need post-1.1 saves for proper mission" I said in previous post) Can you play OA with pre-1.1 saves and with its bsa & esm?

» Sat Apr 02, 2011 3:39 am

Sorry, but I can't play DLC with their BSAs with 1.0.0.15 exe. I have to extract all the data from DLC BSAs to Fallout3\Data folder and activate the "archive invalidation" in FOMM. I don't know if there's only I got the problem? (this "extract" one and the "need post-1.1 saves for proper mission" I said in previous post) Can you play OA with pre-1.1 saves and with its bsa & esm?

You're doing something wrong then, as O:A's working fine for me using the setup as described. I made a new file and got the Outcast signal/quest update about halfway to Megaton from Vault 101. You didn't have to extract O:A's .bsa's. Also, you should use http://www.fallout3nexus.com/downloads/file.php?id=944 to forever free yourself of having to update your ArchiveInvalidation.txt file.

» Sat Apr 02, 2011 4:00 am

All of the above should be restored to their original condition and the DLC (at least O:A) does work with the fake patch plugin. I have Anchorage.esm and both .bsa's in my Data folder though, so I'm not sure how things would work out with DLC if it's left in AppData...
You don't really have to back up the Vanilla .exe or .esm. I saved them to have an easy way to compare/contrast and test them, but you only really need the 1.0.0.15 exe and esm. Just hold on to the v_1.0.0.15 patch in case you ever need it again.*To get Anchorage, you might need to have updated to 1.1, if only temporarily, as 1.1 updates that GFWL marketplace. If you've previously updated to 1.1, you might still be able to buy The Pitt using your 1.0.0.15 setup.
*If you do get the DLC's and are going to use FOSE or end up moving the three files to your Fallout3\Data folder, load FakePatch_v1.4.0.6.esm right before Anchorage.esm instead.

Other than that, you should be good to go.

Ok, still being a noob here...

To get OA, I need to update to 1.1. But that will break my Vats if I do that. So I need to:

1) Save a copy of my 1.0.0.15 exe
2) Patch to v1.1
3) Replace the v1.1 exe with my old 1.0.0.15 exe

And this will give me OA with my Vats still working correctly?

» Sat Apr 02, 2011 2:15 am

Ok, still being a noob here...

To get OA, I need to update to 1.1. But that will break my Vats if I do that. So I need to:

1) Save a copy of my 1.0.0.15 exe
2) Patch to v1.1
3) Replace the v1.1 exe with my old 1.0.0.15 exe

And this will give me OA with my Vats still working correctly?

Yup, just back up the .esm too as using the 1.1 .esm with 1.0.0.15's .exe will sometimes give you a problem letting you use your mouse in the startup menu.

» Sat Apr 02, 2011 6:11 am

So evidently the saves aren't the issue!?! That shoots down the thought of being able to update to 1.4 and somehow getting the old VATS back by just doctoring saves, but it's good news. Thanks for verifying this and posting your findings.

Yeah, you have to follow directions exactly or else one thing slightly missed and you're screwed. What I discovered was that my Fallout .esm was the 1.1 version even though my .exe was the 1.0.0.15(when moving my data folder back I accidentally overwrote the .15 .esm) so I redid it and it works fine now.

» Fri Apr 01, 2011 10:38 pm

Yeah, you have to follow directions exactly or else one thing slightly missed and you're screwed. What I discovered was that my Fallout .esm was the 1.1 version even though my .exe was the 1.0.0.15(when moving my data folder back I accidentally overwrote the .15 .esm) so I redid it and it works fine now.

HUZZAH! :foodndrink: Thank you for confirming this! I'd also noticed a few issues while using the 1.1 .esm which went away when using the matching 1.0.0.15 .esm. I'll boldify the part about saving the appropriate .esm in the OP in hopes of helping others avoid the same mistake.