Fallout/2 broken on Vista?

Phil the Nuka-Cola Dude

Sonny, I Watched the Vault Bein' Built!
Fired up F1/2 for the first time on this rig, had installed TeamX's F1 patches and Killap's F2 patch/restoration pack. Went to create a character and noticed some odd mouse lag when the age/name tabs had been selected so I attempted to alt tab (failed), windows key (failed) and finally CAD.

To my surprise, Fallout was using over a gig of memory, and absolutely thrashing both cores of my CPU.

Opened up Fo2 and experienced the exact same problem.


Is the engine broken on Vista or what? This can't be right.

falloutpp1.jpg


8800 GTS 512
X2 6000+
2gigs (ddr2/800)
Vista 32
 
Most games will use your entire cpu. That's completely normal. It looks like 50% to you because you have two cores, and windows balances out the load between them. Set fallouts affinity to a single core and usage for that core will jump to 100%.

On the other hand, most games don't try allocating a gb of memory, but for some reason fallout does. It does it on xp too. It doesn't cause any problems, even if you don't actually have a gb of memory.
 
Phil the Nuka-Cola Dude said:
Any idea about the mouse lag at the save+load / name selection / age selection screens?
There's a direct input/direct draw interop bug that can cause that on xp. Don't know if it's related to your problem, but the xp version can usually be fixed by turning down the render ahead setting or vendor specific equivalent in the graphics drivers.

Failing that, try turning off direct draw hardware acceleration.
 
How many frames would you recommend? 3 is the default.


It should probably be noted that I just added your fix for the blackscreen problem and it works marvelously on fullscreen at the default res (and hilariously enough, talking heads/videos work fine).


*edit*

Scratch that; Changing the 'frames rendered ahead' to 2, 1 and 0 didn't fix it, and unfortunately these drivers (175.19 WHQL) don't allow the ability to change the level of hardware acceleration.

Blah.
 
Back
Top