Did you try turning off Hyperthreading yet?

Also did you try all the recommended fixes in the BIS forum in the stickied thread?

using the -cpucount=xx should be the same as disabling hyperthreading; but you don't have to enter BIOS and disable it for the whole system. Try using -cpucount=4 in your shortcut and see if that helps.

And you're right, the game is un-optimized; but I think we deal with it because it's the only game of it's kind

Forgot about the hyperthreading. I have mine turned off in the BIOS. With 64bit, 4GB plus memory,and multi-core CPU's you should never need that old Intel pallor trick. That combination will crunch through pretty much anything.

I had to use the -cpucount because Arma2 would not use my second cpu and overheat CPU #1.

NoUseForAName, I have another system just like yours except it has 6GB Ram and Win7 x64. That BFG card rocks with the latest Arma2 beta and the tweaks I listed earlier. localvram is set to the 800meg of the card. You should change to the x64 Win7. World of difference.

yea I have the 64-bit Win7 but I just don't have time to install it right now; hopefully soon. I love this card though! I still run a pretty low res (by today's standards) but so far it's been more than enough for games.

I'm not gonna jump trough hoops to disable HT everytime I play Arma2. Anandtech's i7-860 review clearly shows that HT still brings performance in 99% of applications and games.

Gonna try the CPUcount=2 and see if that improves things. Still think ATI FSAA is actually faked using super sampling, the FSAA performance is the worst I've ever seen in any game.

Okay, this is unlogical, but great: CPUCOUNT=4 truly improves framerate.

I tested it with a large AI engagement, me as civilian present but view steady on the ground (to unload the GFX card) and the difference is about 5 FPS at an average of 30, so significant.

Thanks for those fixes, now I still have to deal with "FPS Killer Trees" but the CPU side seems to run fairly well now.

A few guys were talking about running at a very high resolution, like 19x12, with no AA. For some the 1:1 pixels are small enough they don't miss the AA. Others demand AA no matter how high the resolution.

One thing to note, some players (myself included) don't seem to notice much visual difference between "low" and "normal" AA settings. No idea why. This compared to other games where I can set 2X or 4X AA through the driver and see a clear difference.

Okay, as fine as it is to finally play with decent speed (also the weird "load stutter" is gone) I'm getting some CTDs with the latest beta. Could that be the beta, or the CPUCOUNT parameter?

I might reduce to 2xFSAA as you are right Adlabs, the difference is small.

actually, the latest beta has a bug where if you drive an unarmed vehicle it will crash the game. ( look here )

You might try 60141 or wait for the next one as BIS is already aware and has fixed it for the next beta release

Thanks, I just found out. Rolling back to 60141 meanwhile, it just was a freaky coincidence with my new startup parameter.