Theoretically, my system should be able to run FSX with settings on medium (please pop my bubble if it shouldn't). My system specs are:OS: Windows 7 Ultimate 64 bitMotherboard: ASUS Crosshair III FormulaCPU: AMD Phenom II X4 955 processor Video Card: ATI Radeon HD 5770RAM: 8.0 GBFree Disk Space: 786.0 GBI have all my settings set to the bare minimum. Here are what my settings currently are.:I also have 2x AA set in the ATI Control Panel and I am running an external FPS limiter set to 40 FPS to prevent studdering. I only have SP1 installed since SP2 seems to make the studdering worse. In addition, I have also used/using Bojote's automatic tweaking tool. On top of all of this, I have Game Booster running (not sure if this has any effect). Initially with these settings and tweaks, I saw a significant improvement. But I was barely running FSX with smooth frame rates, even though I was getting a relatively consistent FPS of 35-40. Simply panning around the cockpit and taxing sparked a lag storm at times. However...that was before. Now, the problem is 10x worse. FSX is now virtually unplayable. In addition to getting noticeably lower performance as compared to before (even though the FSX FPS counter is still showing a constant 35-40 FPS), FSX keeps on crashing either due to a "fatal error" (caused by NTDLL.DLL, apparently) or that I somehow ran out of memory. Prior to the latter warning, my textures would become extremely blurred and weird effects such as this would happen. The temperatures for my CPU and GPU are in safe ranges, around 50C-60C for both while under load.I have already uninstalled FSX and all my add-ons (which is really just the PMDG MD-11) using Revo Uninstaller (which cleans all leftover files) tons of times already to no avail. If anyone could help me, it would be wonderful.

Is this FSX SP2? I recommend running FSX in 32 bit colors, I see that you run it in 16 bits. 16 bits is really old now, and it would not surprise me if its not properly implemented in a title like FSX and that it would cause crashes. To select 32 bit colors make sure you select 1680x1050x32 instead of 1680x1050x16

Is this FSX SP2? I recommend running FSX in 32 bit colors, I see that you run it in 16 bits. 16 bits is really old now, and it would not surprise me if its not properly implemented in a title like FSX and that it would cause crashes. To select 32 bit colors make sure you select 1680x1050x32 instead of 1680x1050x16

I will try that, thanks!

Your system should run FSX fine.I suggest that you delete your FSX.CFG so that a new configuration file will be created. The settings of these new file will be adapted to you hardware. Then you should use the "Tweaking and Tuning tool for (FSX SP2/Accel - ESP/Prepar3D)" from ******* Altuve. You find it here: http://www.venetubo.com/fsx.htmlFinally you could take the settings for your graphic card from my guide "Guide to setup and tune the flight simulator X": http://www.happy-art.../FSX-guide.html That should rectify your problem.

There is no need to delete your cfg file; simply clicking on "Reset Defaults" will accomplish the same thing. Which is probably to raise the levels of display settings, possibly making everything worse.You are running the game with an very high resolution monitor, which might explain your memory problems; the more pixels to fill, the more memory required. If you have a smaller monitor, you could try connecting it and seeing if that makes any difference.Best regards.Luis

Which is probably to raise the levels of display settings, possibly making everything worse.You are running the game with an very high resolution monitor, which might explain your memory problems; the more pixels to fill, the more memory required. If you have a smaller monitor, you could try connecting it and seeing if that makes any difference. Luis

I agree with RelaxX: I've been running 3840 x 1024 x 16 bit for years without issue, Luis. The monitor should also be at the same memory size - but running 16bit should not noticeably impact your performance. I cannot discern the difference now that I'm running an i7-64 at 4gig+. Yes - it quadruples the memory usage, but to affect FSX this seriously would seem to me - to be something else.

1680 x 1050 pixel is not a high resolution nowadays. The ATI Radeon HD 5770 card can easily drive such a monitor. :(

You are running the game with an very high resolution monitor, which might explain your memory problems; the more pixels to fill, the more memory required.Best regards.Luis

What you say about requirements is true, however as others have said 16x10 is in no way a large screen size especially given his video card. 1920x1200 is pretty standad fair on a single display these days on any decent 24" panel and has been the the resolution I prefer, but to each his own. As for 16bit color? No no and no, why? these days there is little perfromance difeerence for one, but the real problem is that the side effect is banding, especialy going into dusk/dawn and night time. there is no room left to display alphas and you have reduced available colors by a huge margin.See image 32 vs 16 hereHowever I dont think FS uses true 32 bit color, if I recall it is something like 24 bit with 8 bits resereved for bump maps and alpha non color data.just check out FSX skyline at night with decent amount of clouds, compare at 16 vs 32.

Alright guys. I just tried this with 32 bit colors. Doesn't seem to have any impact on my frame rates. I haven't had time to test out and see if I still get fatal errors or memory issues.As for my resolution, that is my native resolution. If I set it to anything lower, the image will either be distorted or become too blurry to read my instruments.I will try and install SP2 again to see if it will improve my performance this time.

has been the the resolution I prefer, but to each his own. As for 16bit color? No no and no, why? but the real problem is that the side effect is banding, especialy going into dusk/dawn and night time. However I dont think FS uses true 32 bit color, if I recall it is something like 24 bit with 8 bits resereved for bump maps and alpha non color data.

You're right on the 24 bit, except that on many LCD displays - even that may only be 18 bit, dithered. Yes - banding occurs at dusk or at night, and if I flew during those periods I might use 32 bit, but for me, who almost never flies at that time - it has ZERO effect, and that's the way I want it - so you can "No no and no" all you want freebird. :biggrin:I fully understand the vagaries of color depth - I've been a sysadmin for twenty-odd years, and electronics / airborne avionics - since 1960.

Ok, I just uninstalled my PMDG MD-11 and the HD AA repaint. I'm right now in the process of uninstalling FSX via Revo Uninstaller for the 9th time now I believe. Then I will install SP1 and SP2 and finally the MD-11.

Just remember to install fsx rtm, load up the default flight and exit the sim, then install sp1 and again load the default flight and exit and finally install sp2.

Just remember to install fsx rtm, load up the default flight and exit the sim, then install sp1 and again load the default flight and exit and finally install sp2.

Please excuse my newbishness, but what is FSX RTM and where do I download it? I ran a Google search and found nothing.

Please excuse my newbishness, but what is FSX RTM ...

Release To Manufacturingthis is FSX without SP1 nor SP2 installed.--

Release To Manufacturingthis is FSX without SP1 nor SP2 installed.--

Thanks for the explanation.Anywho, my frame rates are now in the playable range again. The only thing I did differently was not use the auto-tweaking tool this time, except to force VSync. All my settings are as seen in the OP.My question now is...should I be expecting more from my system or is this what I should be seeing?