...tweakers might want to verify before posting results, config files, etc.i start fsx, load a flight--fixed camera, autopilot--get 20 locked 20, smoothi close fsx, i make absolutely no changes to the configurationi start fsx, load the same flight, get 16, a bit stutteryi close fsx, i make absolutely no changes to the configurationi start fsx, load the same flight, get 12, quite stutteryi close fsx, i make absolutely no changes to the configurationi start fsx, load the same flight, i'm in single digitscool, eh?cheers:-)

:--)))))))))))yes, that's true for me too!and if you reboot your PC, launch the same flight you will have again smooth and nice fps!that's "magic"!! *:-*

interesting... guess I'm lucky i've never have problems like that... I'll fly for an hour, get off, get on a few min later, and have the same locked 20 fps I had before...

not a "problem"--just neutral behaviour. probably related to memory/swap file managementunlock. i bet it will go from 50 to 40 then 30... there goes your luck :-)a good number of posts in performance threads says, "nah, it doesn't work for me, it makes it even worse." this could be the reason for many of these postsanyway... enjoy the weekend :-)

A program like FSX may leave memory and virtual memory in a mess when it exits. The next startup may take awhile to sort out the memory, or it may never, resulting in semi-permanent low FPS. This is where Microsoft's other product Windows comes in. There may be a setting there that is causing the memory mess to be a longer term problem. I would try one of the memory optimizers as a good way to see if you can break the cycle. You may not want to run it every time you start FSX (takes too long anyhow) but you will at least know the cause of the deterioration.Regards,Dick BoleyA PC, an LCD, speakers, CH yoke

>A program like FSX may leave memory and virtual memory in a>mess when it exits.I doubt that because when i do, i notice that FSX loads a lot faster the second time (completely quicting to desktop before the re-load) so parts of it must still be in memory (same happens in Lock On).I also noticed the same effect (lower FPS the next startup) but it mostly settles back to normal after a wait.On the other hand, if i exit out of a flight but stay in FSX and then re-load the same flight again, 50% chance that i end up with an error which needs to be send to MS and the question of restarting FSX yes or no. Again then there is a 50% chance that the next load works fine or comes with the same error again. Think it has somehow something to do with the latest version of FSUIPC4 but i'm not certain. But since that's the only thing i added upon a clean install of FSX and SP1...?