Game crashes infront of Megaton

[Tarinator]

I haven't played Fallout 3 in a few months, no problems at all really. So today I got back on it after adding the Oiled Type3 body mod. For some reason Fallout keeps crashing right infront of Megaton where the Deputy robot and Mickey are (Mickey hasn't been there for quite some time) :blink: . I don't know if its the new mod or if something else is wrong. I have a bunch of mods, I can post my load order if needed.

[phoenix198730]

mine has been the same after the light mod what build of the game you running? im on 1.7 :s sometimes it crashes for no reason

[Tarinator]

Im on 1.7 as well..This is like one of those things that just get you mad even though its pointless. Usually when I want to go to Megaton I either type it into the console or fast travel if im outside. I never have a point to walk through there but I want it to work :wallbash: .

[phoenix198730]

my game has been craching less now i have taken some of my mods off like the most recent one scince it started to crash. but every so oftern it will crash after 5 min or be fine and crash after 2 hours and no perticula place it would do it.

[Tarinator]

Mine is only in the cell where the robo-deputy is. Theres always a battle between Deputy Weld, a soldier ant, and a caravan crew going on when I watch from a distance :starwars: .

[phoenix198730]

i have had a look around there seems to be 2 fixes:

 

1. game build 1.4 seems to be least bugy try that if you have no DLC's

 

FFDShow

 

There is an audio/video codec program in existence called FFDShow. Apparently, it has a conflict with Fallout 3. If you have the program installed on your computer (I didn't, but that was me), You either have to uninstall it or add Fallout 3 to the audio/video decoders exceptions list. It is possible to have this on your machine without knowing it if you have installed codec packs, like the CCCP (Combined Community Codec Pack). To fix: open the video decoder configuration window, click on the second tab labeled "Info and debug." Back on the right, find the checkbox labeled "don't use ffdshow in," Check the box, and underneath type in 'fallout3.exe.' If there's something there, just put a semi-colon in between the two (no spaces).

 

This solution has worked for quite a few people. I didn't have the thing installed, so obviously I wasn't getting any conflict problems there.

 

Setting compatibility

 

For some reason or another, this seems to work. I don't know why. Find your Fallout 3 launcher. Yes, this does mean you'll have to go into your program files. Ignore that nasty windows message about not mucking things up. Depending upon how you have it, it may be in c:/program files/Steam/steamapps/common/fallout3 or it also could just be in c:/program files/Bethesda/fallout3

 

If you can't find it, then look harder. Anyway, open the properties of the launcher, it should be an application type file (do not confuse it with the fallout3.exe security catalogue) with the little cartoon boy icon. Once inside properties, click the compatibility tab. Take whatever is currently selected, and switch it to Windows 2000. Launch your game and test it out.

 

Changing graphics settings

 

This is a bit of a gray area. It can really depend upon your graphics card type and what version you're running. Fiddle around with some of the various stuff. One of the ones that fixes a few of the random crashes you find when browsing about the environment is to change your "water multisampling" quality to Low. This is pretty much not a big deal at all anyway, so don't worry about lost quality. Other fixes in this area are pretty vague. Try lowering quality of a few things (I know it sucks to do so, but try it anyway). You might lose aesthetics, but you'll likely gain play time without crashes.

 

Also, some have said that setting displays to Default at the launcher have helped a little.

 

Changing your .NET framework version

 

Fallout 3 does some naughty things. One of them is to install a beta version of the .NET framework 3.0. This, of course, can lead to all kinds of nasty little problems that could potentially cause some crashing to occur. Uninstall the current .NET framework, search google for an older version, and install that. Will it work? Who knows?

 

Update your drivers

 

Some people have claimed that their fully updated drivers have no problems with it. Conversely, some have changed to older versions of the drivers and had success with it as well.

 

 

Refresh rate windowed mode

 

Reducing your monitor's refresh rate down to sixty, running the game in windowed mode, and turning off AA mode seemed to work for some people.

 

Try using DirectX 9

 

Some people have experienced less crash volume by using DirectX 9 instead of 10.

 

Windows Live

 

There have been some people who have been entirely unable to launch the game since the patch came out. Apparently one solution to this problem has been to install Windows Live Redistributable v2.0. Give it a shot!

 

Stupid SecuROM

 

Fallout 3 has a SecuROM Root kit in addition to a bunch of other hidden Plug'n play virtual drivers. People with more than one optical or sata drive have reported some access issues. Also, using disc imaging software tends to conflict with those virtual drivers and crash the game. Actually, if you have a fixed EXE instead of the image, you tend to have less crashing, but then the SecuROM stuff is still active. Although, if the all of the SecuROM stuff is purged, you get something like 60% less crashing. Of course they have to remain where they are as part of the end-user license agreement. Bah.

 

Of course, various implementation of many of these fixes do seem to chip away at the enormous number of crashes, but keep in mind that they don't seem to solve the problems entirely. I get crashes about every hour or so, but that's better than every 60 seconds. Hopefully they get some fixes going?