Sarkus
5321
The patch is only designed to fix the “crash on exit” problem where the game stops responding on exit. Apparently they prioritized that due to a request by Microsoft.
JPR
5322
I know this hasn’t been talked about in a while, but I am running Vista with a 320MB 8800GTS and haven’t had a single crash in over 20 hours of play time. I do get the error on exit (every time), but no crashes or hangs.
I get CTDs when I save very rarely (maybe once or twice in 10 hours), but thankfully the save goes through before it crashes, and Fallout 3 loads the game very very quickly, so it’s not a big deal.
anaqer
5324
I have, but I’m a bit confused (links to a single post in that other thread, not spoiling anything else).
Also, my crashes appear to be 90% fire related. Whenever somebody catches fire, the game is apt to crash in the next few minutes (strangely, burning barrels don’t seem to trigger this).
anaqer
5325
Also, my crashes appear to be 90% fire related. Whenever somebody catches fire, the game is apt to crash in the next few minutes (strangely, burning barrels don’t seem to trigger this).
Grifman
5326
You have a peculiar definition of “big” - you assume a problem that exiists for you exists for most others out there. Please note the patch fixes one problem - I don’t think most people would call that a “big patch”. And sadly, fyi, it won’t fix your problem as it relates to a crash in exiting the game, so it’s even “smaller” than you thought,
shang
5327
I’ve only had a single crash so far, and that was right after a car explosion, so you might be on to something there.
anaqer
5328
I spoke too soon - now I can’t play it for twenty consecutive minutes without it crashing, sometimes in the very first minute. Could be a savegame corruption, but I don’t think I’ll bother to tiptoe around bugs for now. I was lucky enough to get through the game for the first time with relatively few crashes (once I learned to avoid fire ants, that is). The replay can wait until they patch it up properly and the SDK is made available (and until I get a decent video card as well).
As much as I hate to say it I’ve had to put Fallout 3 aside for now. Crashing has become increasing common and none of the suggested fixes seem to work. I don’t like having to quicksave every 2 minutes because I know I likely won’t hit the 20 minute mark.
Well I guess its back to Dwarf Fortress for me.
I decided last night to throw Fallout 3 on my laptop. Its below the requirement. 1.6 ghz Core Duo, 1 gig ram, Geforce 7400 Go video. Just for reference, Hinterland is unplayable on this system.
I installed t, put all the setings to the lowest possible and… its actually playable. I haven’t ran into any significant combat beyond a few raiders and it looks like it was hit by an ugly stick from 2003 but its completely playable.
Dejin
5331
The XBox 360 version is just about rock solid. I’ve had one crash in 50+ hours of play. I know Tom said that the PC graphics are much better, but honestly the XBox 360 version looks great on my 27" monitor. I do very occasionally get pop-in but it’s pretty rare.
metta
5332
Yeah, agreed. On a 32" HDMI-fed t.v. it looks gorgeous. No crashes. No complaints.
hong
5333
Ditto here. Maybe the one issue I have with the 360 is that the computer text when you hack terminals is a bit hard to read from 10 ft away. Other than that, the graphics are plenty good enough.
How’s the draw distance on 360? On the PC with high detail, you can see the Washington Monument from damn near any high point on the lower 3/4 of the map.
Case
5335
I’ve only crashed once in 20 hours of game play, but twice on exiting the game.
However, I have run into one annoying bug more than once: my character goes into “encumbered slow motion” after a combat, even when not encumbered, and with no damage or rad effects. The only way out is to restore an earlier save and re-fight the battle.
Same on the 360. Sometimes I’ll notice some buildings drawing in when I zoom in using the iron sights, but for the most part you can see at least the outlines of buildings from any realistic location. I know that from the ‘scenic outlook’ outside of Vault 101 I could see both the Washington Monument and the dome of the Capitol.
There’s a tiny bit of pop-in when wandering the wastes on the 360, and there’s a weird flickering thing that happens with some objects on the ground sometimes, but those are both very mild. The real difference, I suspect, is the textures on many of the objects in the gameworld are pretty low-res when you get right up to them, but that’s not the kind of thing that bothers me much.
I have no doubt that when I eventually upgrade my computer in a couple of years with a new graphics card, I’ll be blown away by how much better Fallout 3 will look, but for right now Fallout 3 on the 360 is plenty purty enough for me.
Hylo
5338
Are you sure you’re not crippled? I’ve had that happen a few times, and if I go to the Status/CND screen in my Pipboy it indicates which limbs are crippled. Clicking on the affected limb uses a stimpack to “uncripple” yourself.
Case
5339
Positive. It’s happened three times now, and I’ve checked the status screen. I’m not sure as to the nature of the bug. It could be that I am crippled, but it’s not showing properly in the status screen.
JPR
5340
You could have been in combat with a Glowing One, and he irradiated you, pushing you over the boundary of radiation sickness. Or, you know, it could be a bug.