Fallout 3 Impressions and Opinions

[Enigma]

I got this off Bethesda forum about someone doing extensive testing of FO3 to see why it was crashing.

# KCPTECH — November 7, 2008 @ 12:54 pm

I get the same error. It appears that even their Patches need some sort of testing before release too. I’ve tried the patch on the US version of the DVD as well as the updated exe from SecuROM. Get the same error on both. The patch does appear to modify some files in the Windows System folder through the Command BOX; however, it doesn’t do anything to the Game exe or anything in the directory.

I have found the primary issues causing the CTD and other crashes. I’ve sent 3 e-mails to Bethesda and no responses. My Computer Science Engineering department took a shot it. I purchased 320 copies and gave them the weekend to figure it out. Here are some of the results;

1.) Fallout 3 Installer installs an older version on C++ Visual 2005 that appears to affect the way the vidcard driver communicates with the game.

2.) Fallout 3 Installer installs a Beta release of DOTNETFX3.0 (.NET Framework 3.0). For users of .NET Framework 3.0 SP1 or even SP2 (Service Pack of the Framework not the OS), upon restarting their system (when changes take place), their game will be quite unstable.
Users of .NET 3.5 or Vista should have even more random crashes.

3.) Fallout 3 Installer installs a non Plug’n Play DRM device manager (not driver but a manager) that doesn’t like any 3rd party codecs (ie K-Lite, WinAMP, etc) and will usually see a CTD when a Hardware codec comes online. This usually occurs when interactive audio (client controlled speech) initializes (ie baby walking to daddy).

4. Fallout 3 Installer installs SecuROM Root kit as well as 8 hidden non Plug’n play virtual drivers. Owners with more than one Optical drive or a sata drive may encounter random drive access issues. Also, Imaging software or any software that may use its own ASPI drive (ie NERO, Roxio, Daemon, ISO, etc.) will have one of the 8 virtual drivers causing the system to do a random CTD. Reason why clients using a cracked EXE don’t experience the same volume of CTD as those who bought the game. However, the SecuROM root kits are still on the system and active. Once the SecuROM is also purged from the system, 60% of the crashes disappear. Unfortunately, they must remain on the system in order to play the game as they are part of the EULA.

5.) Fallout 3 also has its own built in MP3 codec coupled to its DRM to protect MP3’s on the DVD (in game). Unfortunately, the codec was never tested fully with hardware decoders like those of an X-FI. This can be varied by the lack of a hardware audio switch in the game options.

6.) Fallout 3 has 14 memory leaks that we found. Most are small, but there are a few that are quite large. Some areas of the map, the memory counter just spins at over 100 MB/sec. Most memory leaks are around 5 to 10 MB/sec.

7.) Fallout 3 video graphics buffer needs to be adjustable in the options and an automatic cache purger installed for cards over 512 MBs as well as linked buffers from SLI and crossfire cards. I’ve seen areas where names on the screen start to disappear and all you see are “Input Text Here” instead of V.A.T.S. or range or etc. The cache doesn’t get dumped on some maps. Most games dump their cache when a map reload occurs. This can be noticed when fast reloads occurs from map changes. Most users will just see their graphics card run out of memory (CTD and stuttering).

8.) Most games were fault free with a basic XP Pro SP2 reload, and only Critical updates and latest stock drivers. Installed the game and played it error free for nearly 4 days. Upon a system restart, lots of errors showed up. This means that Fallout 3 significantly changes the operating system. Far beyond reasonable accounts as all you can do with the system in not to play MP3’s, watch movies, make a CD or DVD, or play other games.

[charlemagne]

OK going by the visuals and some of the rational ghoul dialog. Has it been 200 years since Nuclear War or only 20+?

200.

[MarshalFoch]

Wow, I should have seen this coming.
Spoiler

My character's name is Batman.

I just went to Project Purity with the scientists.

Enclave guy: We want your useless thingyjig!
Dad: It's MY useless thingy! [explode]
Batman: I AM AN ORPHAN!?

I noticed that the game prevents you from drawing a weapon in that scene... it didn't seem right to just watch them die without trying to intervene at all.

You are going to love the next few story missions then. Just ignore the story after you get to the Citadel until you have done everything you want to do. Getting to the Citadel is only needed because it is the only place to get trained to wear power armor.

[Oscar Wilde]

Speaking of story stupidity, (spoiler warning), the ending is completely flawed. Charon is a Ghoul, and therefore immune to radiation. Yet he won't go into Project Purity to start it up.

DE DE DE.

[PREDATOR490]

The issue with DAD blowing himself up is more lame from my perspective. Logically, I am sitting outside at level 20 armed to the teeth with perks and weaponary.
Why is it I am locked out of a room containing three Enclave guys when Dad could just open the door and let me blow the fuckers away... ?
If your really that desperate to kill James, then have him die in the firefight but noooo.... lets blow myself up while my son/daughter is standing right outside packed like a tank.

Conclusion: Selfish Jerk

And then the end comes along, where you get the 'ultimate choice'. Be noble and sacrifice yourself or be selfish.... like your father was.
It isnt like you have companions who either A) Can survive radiation (Fawkes, Charon) or B) Must do what you tell them (Clover, Charon)
It isnt like the Enclave troopers came through the front entrance of Vault 87 which is so radioactive that it kills you in seconds but somehow the Enclave has SUPER Radaway or those Enclave troopers are mutants stuck in Power Armor.

No sense in beating a dead horse anymore though.

Right now I am doing my best to play through again so I can mess about and avoid the main quest. Installing mods adds a bit of variety too but the CTDs are getting more frequent because of it. I installed a new 'custom' Vault mod for the player and everytime I try to enter the fucking thing it causes my entire computer to just lock up and need a restart.

[Jade Falcon]

The issue I have with that scene is that looks like Colonel Autumn in the chamber with Dad, so how the hell does he survive.

[Chardok]

The issue I have with that scene is that looks like Colonel Autumn in the chamber with Dad, so how the hell does he survive.

Same reason you "don't"....destiny.

[Oscar Wilde]

The issue I have with that scene is that looks like Colonel Autumn in the chamber with Dad, so how the hell does he survive.

Destiny, and he has the same rad away the rest of the enclave does. It's magical.

[Enigma]

Screw this, I'm shelving this game until the patch comes out. Browsing through Beth's forums suck because they are swamped with people complaining that the game constantly crashes and the help they get is totally ineffective. Giving tips on how to jump through hoops so you can get the game to work yet disable part of of your OS and various other programs? No thank you.