FPS in free flight for me is same but have problem when in 6 to any planes i have big fall of FPS from 40 to 5 FPS, like stuttering and i cant shoot on him because is slide show :( when plane get out from my sight FPS back to normal.
sound is great now :)

Very interesting, it seemed to me as well that raising the FSB has the best effect, then raising the mutiplier. Nice clockincrease without raising the voltage. Going to order a cooler tomorrow and then it's overclocking time :grin:.
If you don't mind, are you raising (if at all) the multiplier in bios or with a program in windows. I was planning on FSB overclock in bios and then maybe a little multiplier increase in windows.
Ughhh, and I need a new mobo :rolleyes:.

It would be helpful if you could post your system specs.

Are there any planes in particular that cause the framerate drop?

Yup, this one too. I did a small experiment very early on (i had the game for less than a week), i wanted to see which one can give me more FPS with less loss of visual quality: land detail or land shading?

In the end, i found out that lowering land detail is fine and gives me some FPS to spend on land shading. I think land detail has something to do with draw distance too (how far away from you the LOD transitions happen for the landscape) which means that only the far away landscape is degraded. Shading on the other hand seems to be a blanket effect and it affects all visible landscape.

So, i turned down land detail and in return for some blurriness across the horizon i could turn up land shading, shading is more important for navigating and depth perception anyway (especially when flying low).

I use the AOD utility in Windows as my clever mobo resets the RAM timings if I raise the bclk in the BIOS. For eg, I can set the RAM to run at DDR 1600, but then the mobo resets the timings to 11, which results in a big drop in performance. Using the same settings mentioned above in the BIOS causes the RAM to run at cas 10, instead of the default 9. I can set the individual timings in the BIOS, but experimenting to find the limits is very time consuming. If I use AOD, the timings remain unchanged, although they can also be set using this utility.

I don’t like changing the multiplier as this disables the PowerNow feature and leaves the cpu screaming along at maximum all the time, irrespective of whether it’s doing anything or not. This is probably not really something to be concerned about, but being a pedantic Virgo, it annoys me. And previous testing has shown that there is little to be gained in terms of gaming performance by running the cpu faster on its own.

I am also not much of an overclocker, preferring to spend time playing games on my rig rather than trying to extract the last drop of performance out of it. But it is nice when you can achieve a worthwhile gain without too much hassle.

Lets not forget this is a BETA patch...it's not final yet. So maybe when it does go final the code will be tightened up and it won't be a hit to fps.

I'm going to keep playing my older version until this goes final.