After trying to play Oblivion and spending 2 days tweaking it until it ran without having a seizure after every single kill (Thanks Havok & dodgy sound coding) I thought I would try Fallout 3 again.

It worked perfectly for 5 minutes. That was after an hour of twiddling with the .INI. I awoke this morning to find it no longer works.

I mean this is a Win 7 x64 with 4gb of DDR3 and a tri-core with a HD4890. Its not a sluggabed I can run every game I play at high in 16:10 on a 1440x900 thats not even a big monitor. Yet this engine grinds and chugs along when it works which is a rarity ?

It went from random seizes to wont even launch now :/

I probably wont even buy New Vegas due to the issues having recently cancelled my pre-order. Dont make me pirate

Tell me its a total fix of that crappy engine ?

I don't know a lot about computer but isn't it possible yours isn't capable of playing them?
My computer is truly brilliant but it has a reaaaally crappy graphic card so I can't play games on it.
Have you thought about upgrading yours or getting a new one completely?

Apart from maybe 1 freeze every 3-5 months, I dont know what you mean about the engine being crappy, maybe it's just your computer.

How exactly did you tweak your .INI?

I do know alot of computers, mine is handbuilt and overperforms for its size & it isnt overclocked. Its only drawback is the HDD transfer access speeds and they are normal. On Windows (useless) benchmark I am 7.5 out of 7.9 on all but HDD access which is a respectable 5. Also I have previously played Fallout 3 on this machine. Additionally I play more demanding games on higher settings.

Its really more a problem of code and ini than hardware. I dont really wanna downgrade back to XP tamper with a whole bunch of dx files and jury rig working sound files back into FO3 just to make it work. Bear in mind FO3 was released when Win 7 & Vista showed up so its hardly credible that the designers couldnt account for those OS's vagaries.

Concerning New Vegas, if they are using the same engine the same problems will appear. Common sense is fabolous isnt it

If A works in X & B=A, and A is superceded by W=A(& therefore B), then (X=W)=(A=B). Insert WP, Win7, FO3 & FONV into A,B,X,W where it makes the most sense for you.

I too hope they've smoothed out some of the problems with the engine. I still have fairly severe crashing problems on both Oblivion and Fallout 3, and this is my third system since Oblivion came out (second since Fallout 3).
That said, I also think Fallout 3 was in itself waaaay better optimized than Oblivion. I have a really respectable framerate, stuttering is almost non-existant and the loading times are extremely quick.

But yeah, if they can make it even smoother and maybe remedy some of the crashes, that'd be great.

Replace his B) with B ).

And I couldn't understand any of that... I'm a nerdy person who knows nothing about computers.
Heh, I'm not good for anything I guess.

The multi core, killed sound, & tried sound unkilled just scaled down to 0.0 volume, higher ram inclusions. Havent tried excising GFWL just about to do that cause I am crashing at that point.

Goes without saying I tried the defaults first.

Im more concerned that NV will be a buggy POS as well :/

@Colonel Martyr - My computer runs FO3 fine in XP after multiple tweaks. Its also pretty flawless in bigger games.

It was a good geuss , & you can work a forum emoticon better than me . But yah no help here. We dont want them grinding out another game with the same issues the last one had. No desire to pay ￡40 for a big mod of a game I already own .

I am running FO3 pretty well at maxed out graphics with 4 gig (DDR2), HD 4830, and a quadcore factory clocked at 2.4 ghz, with Win7. You exceed me in everything except the processor. It must be an individualized problem. It may also be because you run an obscene amount of mods without a merged patch or etc.

Funnily enough it did go totally [censored] up after mods installed. I shall look at merging patches etc. However the problem remains. With mods removed it still doesnt work

If I buy NV I want it to work. Thats not a lot to ask of a game built on an older established engine.

Computer power shouldn't really be an issue unless you're pushing your settings too high (which I'm sure isn't your problem).

I mean, I run the game fine (yeah, the occasional CTD, but nothing beyond expected for a Beth game) on somewhat low settings with XP SP3, 2.66ghz Core 2 duo, 2gb ram, ATI HD2600XT/256mb. At 1680x1050. WIth a variety of mods & FOSE.


So it's got to be something else. An incompatibility in hardware/drivers/mods or an .ini mistake somewhere. Or something.

The engine is very sensitive about stuff in the background. Codecs, programs using up resources, this kind. It's a problem that you can fix on your end by running the game booting the cleanest Windows possible. Both games work just fine on my similar machine.

We have no idea what they have done to the engine nor how it will behave with the new game. In the meantime I suggest that if the OP is having problems it is best to post in the http://www.gamesas.com/index.php?/forum/36-fallout-3-pc-issues/ and try to sort things there.