Crashes to Desktop (CTD) after the 1.1 patch

[Thorn79]

Anybody else notice more CTD after the latest "patch"?

 

I have the STEAM version of the game.

 

Vista Home Premium 32-bit

ATI 3870 512MB DDR4 latest Catalyst drivers

4GB RAM

RealTek onboard 5.1 HD audio

 

 

Game didn't have nearly as many CTD prior to the patch. I use to only get them if I had mods installed incorrectly but I haven't changed any mods or added any new ones. The only thing I've done is update the game to version 1.1 and downloaded and installed the latest FOSE beta 4 to run the mods on version 1.1

 

Funny how they are suppose to "fix" the game with patches - not break.

 

Plus, VATS is running a heck of a lot slower than the previous version. I enter VATS and I have to wait a few seconds for the percentages to show up on the targets. This patch is crap!

 

After reviewing and reading other problems on here about CTD prior to the 1.1 I'm thinking there is a memory leak that didn't get fixed. It has to be a memory leak since so many people are having the same issues using various forms of hardware. My system stays VERY cool. Core temps usually read 45c under load while playing the game or running a stress test. I can usually play FO3 for about 30min-1hr without a CTD and sometimes even longer. It's just a lot more noticable to me since I used to never get any with the original unpatched game. So it's either a memory leak that was added to the game by accident or the Bethesda added more bugs than they took out.

 

I usually live by the saying "Don't fix it if it isn't broke" by I forgot to turn off that feature with STEAM, so when I logged into STEAM yesterday it automatically "updated" the game to 1.1 and I couldn't do anything about it. So shame on me for not remembering to turn that stupid feature off. I guess I was thinking that the game was running great and an update might actually improve the game even more some how. Guess I was wrong as I haven't noticed one thing that the patch has done to make this game better than it was other than not getting stuck in the upgrade sceen with assign -249 points to your skills. At least that crap is gone.

[Thorn79]

bump :(

[kengiczar]

I also have this problem, it happens at least once every 20 minutes. Also was fine before the patch and forgot to check the "do not automattically update this game" feature on steam. I've searched on the net but couldn't find any solutions. I have downloaded the latest windows live, and I did download the accursed patch into the fallout3 directory under steam/steamapps/common/fallout3 blah blah..can't remember exactly but it's in the right place ^_^

[Aragron]

After the patch,the Fallout3.esm get the last load order,and Fallout3.esm NEEDs to get load first than any other mod.

so,use some program like FOMM to change the load order.

if this don't work... Re-install Fallout and don't use the patch. :D

[nosisab]

All modders and mod users must be aware that things may become unstable with each new patch release. Bethesda patches the game upon vanilla, sensible utilities like FOSE in special are vulnerable to them and happily the team is knowledgeable and quick to adapt to the changes.

 

But is not the time, yet, to blame Beth or mod. The softhouse have the precedence, it need not be aware of the mods when patching. The community is very active (ad this is good) and were this active even before the files structures were well known, even before GECK was released and surely even before the game engine takes it's final shape.

 

In a parallel Oblivion got sensibly stable at 1.1x patch and so many mods existed at the time and suddenly SI is out and with it some deep changes in the engine and a new patch with new resources and 1.2 was available as obligatory with SI and optional with Oblivion. This patch introduced such changes than even some modders that deserves my greater respect got a hate for it and actively opposed to mod for it. I fear we will see something like such in fallout 3 too.

 

So, if you are experimenting troubles with new patches know such should be expected and be certain than things will be back in the rail soon. Not a time to blame someone, just report the troubles so to help the modders correcting their works.

[Guest]

I just installed the newest patch so I could play Operation Anchorage. I noticed that if I play in the simulation, my CPU usage (quad core 2.4) shoots up to 80-90% and as it approaches 100% it crashes to desktop. When I'm regularly playing, outside of the OA simulation it runs at 30-40% and I do not get the CTD. OA is now unplayable as it crashes every few minutes. I got through the first section of the simulation, but can't proceed as the crashes are too frequent.

 

I noticed after 1.1 VATS is very slow, taking a few ticks to load up the body parts and percentages just as Thorn described. I do not have the steam version, but the regular retail. I updated my nVidia drivers (8800 GTS), got the non beta .NET. Later tonight I'll try moving the OA files from the Windows Gaming folder to the F3 folder (described in post #48 http://www.bethsoft.com/bgsforums/index.ph...8894&st=40) or just reinstalling the game.

 

I had absolutely no problems playing fallout 3 prior to this patch. I also don't use any mods.

[Smosh]

I've noticed that the F5 quick save now takes upwards of 20 seconds to complete whereas before it was instantaneous.

 

EDIT: This appears to have been caused by my old save game loading (now with the patch) while there was an enemy cell still operating. Once I had killed the remnants my game went back to normal.