I ran a few tests on AH2 to try and figure out why everyone was griping about framerates. My conclusion: The trees are the big framerate killers.
I conducted my test by changing vid settings and returning to the same field, runway and aircraft and comparing the fps. I found that changing the game resolution, max texture size, preloading of memory onto system memory and/or vid card memory, detail level, object display size level, killing background processes (using FSautostart), all had only a minor (<5%) effect on frame rate.
However, changing the ground detail display range from max to min changed the framerate from approx 30 to almost 50. I also noted that my framerates were pretty much maxed when looking around at towns, field objects and smoke but as soon as I looked at a hill with lots of trees my fps would drop from 70 (monitor limited) to mid 30's.
What's up with the trees? Why are they such a huge performance drain?
I also noticed that if I alt-tab out of AH2, my system is running like a dog even though over 300MB of memory is still free...
My rig is a P4 2.4 with HT, 1024MB RAM, WinXP, ATI Radeon 9600 vid card with 128MB RAM, latest ATI catalyst drivers, Dx9b.
I think I'll hold off a little longer on resubbing until AH2 is more than a slower version of AH1...