No need to reinstall windows and fsx. Just update all your drivers, delete your fsx.cfg file, and go through your scenery and other textures for any problems. You just have to find the sweet spot that your computer likes. Otherwise you will run into the exact same problem when you start adding payware and freeware again.

I was battling poor FSX performance for months. The absolute best thing I did to speed things up was reinstall it, and rebuild the PC whilst I was at it!

 

Sorry it's most probably not the suggestion you were after, but believe me I tried many things and gave up. A fresh install is the way to go.

 

I'm not sure if this is just general advice not targeted at me, but my system runs great, including FSX. 16-17 FPS for a few seconds in the absolute worst case scenario that will virtually never be encountered and 20's or 30's at the worst everywhere else is perfectly acceptable.

 

No need to reinstall windows and fsx. Just update all your drivers, delete your fsx.cfg file, and go through your scenery and other textures for any problems. You just have to find the sweet spot that your computer likes. Otherwise you will run into the exact same problem when you start adding payware and freeware again.

 

Again, not sure if this is just generic advice not directed toward me but I've done all these things in the search for more performance and what I found is that a tirelessly tweaked config file and the couple little extras I mentioned in my original post are the keys. Deleting my config file actually resulted in either lower performance or OOMs.

Dear me........ :rolleyes:

Again, not sure if this is just generic advice not directed toward me but I've done all these things in the search for more performance and what I found is that a tirelessly tweaked config file and the couple little extras I mentioned in my original post are the keys. Deleting my config file actually resulted in either lower performance or OOMs.

 

What addons do you run? There must have been a problem with some of them in your old install. For example one scenery had an empty texture folder. That's a known memory leak. Some of my AI had corrupted night light files. I stopped using AI completely. Orbx is well known for having duplicate afcad files. I searched and removed duplicates. I rebuilt my fsx.cfg file and only did a few tweaks at a time. Everything runs great now! No OOM or crashes.

I have no OOMs or crashes with DX10. The reason DX9 crashed with a default config file was because of the settings and add-ons I run. We're talking NGX @ FSDT KJFK w/Aerosoft Manhattan X + UTX, Experience X, GEX, UT2 w/high traffic settings, etc. etc. That's enough memory usage to make anyone's DX9 FSX run out of address space.

Notice I noticed dropping below 15 fps minimum is 20 fps is acceptable, but run fs9 and fsx, xplane. FSX 20 fps is acceptable for GA, and FS9 it's 40 fps, Xplane is 30 fps. Do not worry about fps it's making things smoothing working with computer limitations. Do reduce water, autogen, clouds to get acceptable balance.

When speaking of memory usage is this in reference to RAM as its a 32Bit Program, or is this more of a pagefile usage problem?

I have no OOMs or crashes with DX10. The reason DX9 crashed with a default config file was because of the settings and add-ons I run. We're talking NGX @ FSDT KJFK w/Aerosoft Manhattan X + UTX, Experience X, GEX, UT2 w/high traffic settings, etc. etc. That's enough memory usage to make anyone's DX9 FSX run out of address space.

 

Still none of that should crash FSX. Do you run a system managed page file? Have you added any AI repaints that might have bad night textures?

When speaking of memory usage is this in reference to RAM as its a 32Bit Program, or is this more of a pagefile usage problem?

 

Memory = address space (virtual addressing) and the 3GB limit for 32-bit applications on modern O.S.es.

 

Still none of that should crash FSX. Do you run a system managed page file? Have you added any AI repaints that might have bad night textures?

 

I invite you to perform the same test with the same add-ons and see for yourself. VAS usage will exceed the 3GB limit in no time when using DX9 in this scenario. Not so with DX10.

Memory = address space (virtual addressing) and the 3GB limit for 32-bit applications on modern O.S.es.

 

That's about what I figured, I know some programs use pagefile and have had crashes over that, which is why I asked the question, thanks!

 

I have heard rumors that P3D 2.0 may have a 64Bit version, of course they are along the same rumors that it will also be fully DX10 supported and that it will focus more on GPU than CPU, whether any of this is true, I have not 1 single clue.

I really hope P3D 2.0 switches to a 64-bit executable and maintains some level of backward compatibility, I'll be among the first to switch if it does.