I imagine a lot of this is FO3's inability to handle multiple cores - for me it runs about as well as skyrim (which I have to use that neat automatic resolution switching addon thing to play) thanks to a relatively mediocre dual CPU being hyperthreaded to 4 sub-2ghz cores and HP not providing any means to disable this. Between that and things like NVAC and NVSR it runs at least as well (though it did take a tonne of tweaking to make that the case). Personally I prefer the Mojave (cowboys are neat ok) but yeah if anyone I knew was looking at playing FO3 I'd direct them to TTW right off the bat, and wish I had been myself (I heard about it but was discouraged by the Alpha tag, though that may have been before the 2.1 update which was what I started with).
[quote=rockitten]
it depends on how messy/clean the programmer(s) coding the game.
One thing I noticed in FO3 is that, they use the "resizing" function a lot to use the same model mimic different items, so a room full of "small" stuffs may have a huge polygon count. And compare with the "empty" Mojave, downtown DC has way more objects.........
[/quote]
I wonder if that might be something to look at an addon for when TTW is finally out of alpha. TTW has helped a lot but I definitely still feel like DC is a lot more resource intensive than it should be when I'm playing.
That said, to make an uneducated guess, using different models would demand more from the CPU/RAM, right? In that case, if your bottleneck is one of those instead of your GPU, something like that would only make it worse, no?