Orbx scenery is a mess. You are getting OOM because Orbx doesn't bother to tell you that you need to edit the airport files yourself when installing many airports as well as their base scenery. First the obvious duplicate afcad files if you run Ultimate Terrain, and also most important the duplicate afcads in the base Orbx region scenery folder if you purchase other airports like KJAC.

 

Flight1 AFX does a good job giving you a list of duplicates that you can scroll through to see if you only have 2 instances of airports which is usually okay since one will be the afcad and the other the approach or altitude info, but bad if you have 3 or 4.

 

I removed all duplicate files and ran dxtfixer available in the avsim library and have no crashes or errors at all since.

You are referring to the .bgl files.. so if there are 3 or 4, this is not so grand, even if elevation fixes?

 

Example.. I open FSX Airport Scanner.. "show duplicates" hit scan..

 

Scroll down till a few with 3 items in the right box show up..

 

0S9.. I see Orbx_0s9_apx.bgl and ADE_ftx_pnw_0s9_jefferson_co_intl.bgl and ade_ftx_pnw_0s9_elevation_adjustment.bgl

 

A few others have 3 as well.. in some cases two FTX related and one UTX.

 

A few FTX related have 4.. but i'm not real keen on deleting bgl files? How do you tell if they are not needed or causing an issue?

 

Another with 3:

80WA

 

Orbx_80wa_apx.bgl; ade_****.bgl ; orbx_80wa_apx_alt.bgl

 

I ran dxtfixer not long ago as well.

 

 

This is where I think you are wrong. One day I was using FSX and saw that it took a long time to load FSX to the startup screen and then load the flightplan. I went into the Task Manager and found that 2 or 3 tabs for Internet Explorer did not shut down properly when I closed my browser. I closed all of the IE processes and FSX was running great again. So, the next time you are near an OOM, you might want to check out the processes running in the background. There are a lot of services/processes that are scheduled at the wrong time to go on the Internet to make sure any software is legal, get weather data, etc. You can also run Process Monitor or Process Explorer to see what is running in the background. If you own the PMDG777, they have an excellent write up in their 777 Introduction Manual starting on page 21 about VAS and they provided several possible solutions which won't stop you from getting an OOM CTD but will reduce the chances. In addition, I think I read earlier you set the size of your swap file. Not good. I have found that setting it at System Managed Size for all HDD's is the best.

 

Best regards,

Jim

I can simulate this same scenario on my test drive which is a bare FSX install and put the same aircraft and addon and see how the VAS free appears.. but in terms of other processes stealing cpu cycles or fps.. i always check in task manager before launching that nothing else is above 1% cpu, preferably 0%.. i would think that the VAS used in FSX would not relate to other processes consuming memory (not talking cpu cycles here).. especially when there are 16GB of free memory on the system and maybe 10GB free before running FSX.. if that seems right.. isnt the VAS free in FSX completely related to FSX processes only (dlls, addons etc). IE: if you have a process consuming 1GB of memory elsewhere (non FSX related) it shouldnt correlate to the VAS usage in FSX.

 

I read too that running fsx with unlimited frames can lead to OOM.. any proof? Would running unlimited in FSX and using NI lock be the same.. if so.. this could be why i suddenly ran into this (besides LOD being too high etc), because i've been externally locking (2 fps boost overall).

 

I didnt set the size manually.. i thought i read that many had done this though.. mine is still set to system managed all drives (but swap file is only on C at moment apparently).

I use all standard settings. LOD at max (4.5), only 1024 textures, have lots of great scenery and aircraft which you can see in my signature profile and I have never once experienced an OOM is FSX since I got it in 2006.

 

Lower your expectations in terms of what the sim can do in terms of throwing ever more increasing demands of it. That is the only answer for now.

I got dings from FSUIPC when I'm flying over the PNW and near Seattle (and I have a much more powerful system).  My LOD_Radius is 6.5.  It is a known fact that you will get dings or an actual OOM if you increase the LOD_Radius over the FSX max of 4.5.  Even doing so will not stop the dings or OOM's especially if you are flying in real weather and in a commercial aircraft addon.  You have to look at what tweaks you employed.  Some, like the Bufferpool tweak will take up resources if not employed properly.  You have to look at what scenery you have enabled.  Too much and you will find that it is loading in the background taking up VAS whether you fly there or not.  Check out the new AVSIM Basic FSX Configuration Guide (link on front page) for some tips and suggestions.

 

Best regards,

Jim

Jim, you specifically mentioned the bufferpool tweak. I have it in my fsx.cfg file as listed below. Is this the correct way to use it?

 

[bufferPools]

PoolSize=0

 

Jim, you specifically mentioned the bufferpool tweak. I have it in my fsx.cfg file as listed below. Is this the correct way to use it?

 

//[bufferPools]

//PoolSize=0

 

Remove it or at least comment it out by placing two slashes in front of the entries as shown above in RED in your quote and run fsx a few times without it.  It's a major problem here in the FSX Community where someone recommends a tweak and everyone throws them into their system configuration without really knowing the damage it will do to FSX (or the good it will do to FSX).  The so-called "tweak" does not work in every system and, if you look up at many of the topics in the CTD forum, it has caused CTD's for some.  I really do not think your system needs any tweaks.  Tweaks are for the older, before Sandy Bridge, systems.  I don't use any except I have set my LOD_Radius to 6.5 and my Texture_Max_Load to 2048. 

 

Hope this helps,

 

Best regards,

You are referring to the .bgl files.. so if there are 3 or 4, this is not so grand, even if elevation fixes?

 

Example.. I open FSX Airport Scanner.. "show duplicates" hit scan..

 

Scroll down till a few with 3 items in the right box show up..

 

0S9.. I see Orbx_0s9_apx.bgl and ADE_ftx_pnw_0s9_jefferson_co_intl.bgl and ade_ftx_pnw_0s9_elevation_adjustment.bgl

 

A few others have 3 as well.. in some cases two FTX related and one UTX.

 

A few FTX related have 4.. but i'm not real keen on deleting bgl files? How do you tell if they are not needed or causing an issue?

 

Another with 3:

80WA

 

Orbx_80wa_apx.bgl; ade_****.bgl ; orbx_80wa_apx_alt.bgl

 

I ran dxtfixer not long ago as well.

 

 

I can simulate this same scenario on my test drive which is a bare FSX install and put the same aircraft and addon and see how the VAS free appears.. but in terms of other processes stealing cpu cycles or fps.. i always check in task manager before launching that nothing else is above 1% cpu, preferably 0%.. i would think that the VAS used in FSX would not relate to other processes consuming memory (not talking cpu cycles here).. especially when there are 16GB of free memory on the system and maybe 10GB free before running FSX.. if that seems right.. isnt the VAS free in FSX completely related to FSX processes only (dlls, addons etc). IE: if you have a process consuming 1GB of memory elsewhere (non FSX related) it shouldnt correlate to the VAS usage in FSX.

 

I read too that running fsx with unlimited frames can lead to OOM.. any proof? Would running unlimited in FSX and using NI lock be the same.. if so.. this could be why i suddenly ran into this (besides LOD being too high etc), because i've been externally locking (2 fps boost overall).

 

I didnt set the size manually.. i thought i read that many had done this though.. mine is still set to system managed all drives (but swap file is only on C at moment apparently).

 

 

Just to see how this played out for the record..

 

I took the exact same FTX PNW scenario on a "bare minimal" win 8.1 install.. (no extra services running)..at initial start of the saved flight..

The VAS free is reported as 1682364

 

Then the same situation on my full blown install..

The VAS free is reported as 1663036 

 

Virtually no difference here, even with minimal services (these values will vary at each start up as is too).

You are referring to the .bgl files.. so if there are 3 or 4, this is not so grand, even if elevation fixes?

 

Example.. I open FSX Airport Scanner.. "show duplicates" hit scan..

 

Scroll down till a few with 3 items in the right box show up..

 

0S9.. I see Orbx_0s9_apx.bgl and ADE_ftx_pnw_0s9_jefferson_co_intl.bgl and ade_ftx_pnw_0s9_elevation_adjustment.bgl

 

A few others have 3 as well.. in some cases two FTX related and one UTX.

 

A few FTX related have 4.. but i'm not real keen on deleting bgl files? How do you tell if they are not needed or causing an issue?

 

Another with 3:

80WA

 

Orbx_80wa_apx.bgl; ade_****.bgl ; orbx_80wa_apx_alt.bgl

 

I ran dxtfixer not long ago as well.

 

 

 

Did you purchase 80WA as an addon airport? If so, you now have in the orbx scenery folder an afcad I believe in a folder with 05scenery in the title. Both an afcad and an cvx file for 80WA while if you purchased 80WA it has its own scenery folder in the same main orbx folder with an afcad and cvx file. You need to go through and for every addon airport you have, remove all the files associated with that airport from the base orbx scenery folders. When my flight is done I will post a few screenshots.

Here is an example of what I mean. I have removed all these bgl files because they are duplicate. I already have purchased the addon airport and it came with its own cvx and afcad file. I have done this for all the folders with scenery in their name in fsx\orbx