I lock my frame rates at 24 FPS as stated in my previous post I only use payware planes PMDG 738, LVLD 763, Flight1 ATR and the Maddog 2006 accompanied by AV6, SB3, sometimes FS Passengers.
You are really not evaluating KORD but, instead, a rather complex combination of addons, each one with a significant impact on its own.
Dual monitors set at 1280 by 1024. You are correct my computer is three years old WinXP, FS9, PD 3.4, 3GB, 8800GT/512,
I think that, with the addons you are using, your system is unbalanced: your video card is *very* fast, but the Pentium D can't fully push it.
Most of the addons you are using (expecially Active Sky, SB3 and FSPassengers) are not really graphically intensive, but are more CPU bound, because they most of their work in the background. In this scenario, a Dual Core CPU, even with a lower mhz count, would get you much better results.
fsdreamteam KORD 13-16 FPS with some stuttering (No AI planes or vehicles)
Fly Tampa TNCM 22-24 FPS
Fly Tampa KBOS 22-24 FPS
Fly Tampa KSFO 22-24 FPS
Fly Tampa KMIA 22-24 FPS
You make it sounds much simpler that it is. It's not like that: performance results are not so linear as they seems. With this test you get the wrong impression that, testing under the same configuration a scenery and another, and seeing different final results, the net verdict is "this scenery is slower".
Is more complex than that: with a given system, and a given combination of addons used, and how they impact on *your* machine, there is a point up to performances are satisfactory. You go further, and performances drastically go down, because you exceed a certain level of "total system bandwidth" and after that, your system with your addons combination, can no longer cope, and fps will go down very fast from there on.
You should wonder why, with a card similar to mine (GTX is not much faster than GT, and certainly not in FS9), you get only 1/3rd of the fps I'm having.
That's probably because you are using a single-core CPU in the worse possible conditions: several addons which are more CPU than GPU bound.
FS9 itself might not fully use a Dual Core (which is far more efficent even in sigle threaded programs anyway), but addons that do background operations like Active Sky, SB and FSPassengers WILL benefit from it. This means, with a Dual Core, you might be able to afford more additional programs running in the background, before their combination AND the scenery, will start impacting on fps.
I'm using a Dual Core without any addons, which is probably wasted in FS9. I guess that, if we exchanged hardware, you'll probably be able to get your 24 fps back, even at KORD and even with all your addons.
I did read this but thought it would be a separate program or setup.exe not something added to the menu bar in FS. No biggie I just didn't like it.
Many addons adds to the menu bar, how you were supposed to operate the program without access to its interface ?
Since the whole point of the Trial is to let you Install, then Try the product, then Buy it, it wouldn't do much sense doing all of this at setup time, because it would have required to run Setup again (why?) to purchase it, after having already installed to Try it.
Not to mention the fact there are other options in the Addon Manager (like turning on/off animated jetways, ground traffic, etc.) which are needed at runtime inside FS9, so a menu is needed, and it doesn't have any side effect like, for example, having an hot-key to activate its interface, because that would risk conflicting with something else.
So again I thank you for the opportunity to try your scenery. Maybe someday when I can afford to upgrade my computer I will try it again.
That's the whole point of having a Trial. And, since the Trial doens't have any expiration date, and doesn't have any limitation on the number of times it can be launched, you can always going back to it, when updating hardware, and the unlimited number of times it can be launched (giving another 5-6 minutes of testing time), is specifically designed for the Flight Sim user, that likes to tweak, launch FS, exit, tweak again, re-launch FS9, and so on...