26.09.2009, 11:13
Okay, now I just went back and compared again my FPS with threaded opt. turned on or off in the Nvidia CP and with either PAM=0, PAM=3 and ;PAM= and ran an N track of an Okinawa airbase attack. This airbase attack for some reason really messes with my FPS (and I use the newest Platinum effects with water=2) so I figured it's a good test.
With threaded set to off I start with 60FPS with v-sync on dipping down at one point to 33(!). Probably 98% of the time it is 55-60. Whenever optimisation was set to on I got anywhere between 42-55 FPS dipping to well under 20 when I strafed some planes on the runway. I also got a CTD.
I have no doubt whatsoever that if you're running a dual core setup you need to keep Nvidia's threaded optimisation off with ProcessAffinityMask as either =0 or =3. Course, when I go quadcore next month I look forward to going through all of this again(!)...
With threaded set to off I start with 60FPS with v-sync on dipping down at one point to 33(!). Probably 98% of the time it is 55-60. Whenever optimisation was set to on I got anywhere between 42-55 FPS dipping to well under 20 when I strafed some planes on the runway. I also got a CTD.
I have no doubt whatsoever that if you're running a dual core setup you need to keep Nvidia's threaded optimisation off with ProcessAffinityMask as either =0 or =3. Course, when I go quadcore next month I look forward to going through all of this again(!)...