Ok guys, here is a screenshots as of how fs2004 looks and runs on my system. (aa = 4x / af = off, res = 1152 x 864)Many thanx to aeroworx for providing the aircraft and activesky for their beautiful sky.Gauges curtesy of realityXP.Believe me that the system is running fluidlySystem :Athlon XP 3200+ (@50 degrees celcius)Asus a7n8x-x512 mb pc3200 ddrMaxtor - 40 GB 7200 rpm harddriveAopen DVD+ rewriter Aopen DVD/CD RomATI (Sapphire) Radeon 9800 proWin XP PRO - SP1DirectX 9.0cCatalyst 4.8Latest Nforce drivers (4.27) - AGP 8X, Fastwrite = on, sideband adressing = enabledBIOS - AGP Aperture = 32mb / Overall settings = agressive / Ram latency settings - Cas latency = 3 Ras to Cas = 4 / Ras precharge = 4 / Cycle time = 8

The screens were only resized and cropped down (unfortunately). There was no after editing done.More screen shots to follow in the screenshot forum.I'm happy to answer all your questions.

Just a question - why did you not enable AF? I have AF at 8x even on my old 9700 Pro - it makes distant scenery look much sharper.

And another question... why are you running the CPU Interface (in the BIOS) at "Aggressive"? Most nForce2 boards (especially the A7N8X series) don't do as well in that mode. You don't say what brand/quality your RAM is, but you should do some benchmarking (in SiSoft Sandra) to check your bandwidth. The "Optimal" CPU Interface setting should allow you to increase the FSB a bit more. Finally, try a tRAS setting of 10, 11, or 12 might give you a bit more performance and stability at the same time.Greg

I have been tweaking the last couple of days alot, and finally decided to disengage the default.xml in the autogen folder.That did the trick, and frames are now up to average 30. *with pmdg 737, fswater, activesky2004 AND Anisotropic Filtering at 4X.As for the agressive, i know i get the best result with the RAM (CORSAIR - Extreme) i have because i tested it thouroughly 7 months ago.Thanx anyway.

" finally decided to disengage the default.xml in the autogen folder.That did the trick"...and Microsoft still hasn't acknowledged this problem :-rollIn addition to disabling default.xml, may I suggest that you also edit your terrain.cfg file?First, make a backup copy of your terrain.cfg file and save it somewhere safe. Then open the file with Notepad or Wordpad. Near the bottom of the file you'll see:"// autogen format// [Autogen.id.type.variant]"followed by several more lines starting with // (these are just for information).Beneath that you'll see various lines describing scenery objects, such as "// Small road with telephone poles only". Delete as many of those as possible (delete the lines starting with // and all lines belonging to that section). The only ones I *keep* are:Utility linesAll bridges + bridge test dataSmall road with telephone poles onlyI deleted the rest as they hardly add to the scenery experience. This should provide an additional 25-40% framerate. If you don't notice an improvement, or FS is still fast enough with the full terrain.cfg, just restore the backup copy.