I seem to be running into an issue i've never had before.. the dreaded out of memory errors.. where the VAS of FSX gets too high..

I have 16GB of memory.. and yeah I know FSX will use up to 4GB on 64bit acceleration.. which i guess it gets near that limit when this happens..

 

I'm pretty sure i've tried lowering the LOD a bit.. but at the same time i've seen many on here that run with a higher setting than mine in fact..

I'm in Windows 8.1, and I dont run in compatibility mode for Windows 7 as of yet.. havent seen a real need.

 

 

The latest example of when it occurred..

 

I had a saved flight somewhere above 1s2 Darrington with FTX scenery.. i was in the bonanza f33 GA craft.. at one point i decided to slew to setup a saved flight situation.. after un-slewing, i had the blurries after unslewing (textures flat and unloaded) and then the ding dongs came warning of memory being low.

 

In another situation i was in the NGX at Toulouse france (addon).. simply getting ready to take off and using Fspassengers.. then it occurred..

 

I usually run with scenery complexity at max, autogen at normal.. LOD at 7.5 (with the 780ti 3GB)..

 

In the first example LOD was still at 7.5.. i'm pretty sure i've lowered that to 4.5 before too though.. or perhaps i need to setup a swap file that is dedicated on a drive (1.5x the memory so 32GB).. as of now its set to automatically manage paging size for all drives, but appears only the C drive has one set and that is currently set to 2432MB but recommended is only 5627 which both seem way low.. 

 

My next step might be to uncheck the automanage and put a 32GB size one on my "D" drive.. my FSX resides on another drive.. "O".

So if anyone has any other suggestions, that would be great..

 

Thanks

I used to get them in FTX PNW + FSDreamTeam's CYVR using DX-9. Since moving over to DX-10 and following the DX-10 tweak advice, FSX runs a lot better and zero OOM's.

I used to get them in FTX PNW + FSDreamTeam's CYVR using DX-9. Since moving over to DX-10 and following the DX-10 tweak advice, FSX runs a lot better and zero OOM's.

 

I'm already running DX10 though.. so something is amiss I guess

You could try Steve's DX10 Scenery Fixer (payware). I haven't as I don't need to at this time.

You could try Steve's DX10 Scenery Fixer (payware). I haven't as I don't need to at this time.

Thats done too.. i may try disabling some addons (scenery) while in a certain region to see if it conflicts.. and/or the swap file change.

What exactly do you hope to accomplish with mucking around with your swap file size and having OOM problems? I'm not that techie anymore, but I don't see any correlation between the two? Do you really think a 32gb swap file pertains to FSX and it's running out of VAS?

 

Check this thread about keeping track of VAS; http://forum.avsim.net/topic/426462-process-explore-vas-usage-bar/

 

Best thing you can do is quit thinking you can run hyper settings and hyper LOD, throwing in either taxing scenery and/or taxing aircraft. As the much younger crowd might say, "Get real, dude!" :lol:

What exactly do you hope to accomplish with mucking around with your swap file size and having OOM problems? I'm not that techie anymore, but I don't see any correlation between the two? Do you really think a 32gb swap file pertains to FSX and it's running out of VAS?

 

Check this thread about keeping track of VAS; http://forum.avsim.net/topic/426462-process-explore-vas-usage-bar/

 

Best thing you can do is quit thinking you can run hyper settings and hyper LOD, throwing in either taxing scenery and/or taxing aircraft. As the much younger crowd might say, "Get real, dude!" :lol:

 

Yeah I have process explorer, plus in FSUIPC you can view it in the command console window.  Oh and i just read you can set it to show in the FSX taskbar, the VAS count.. nice

 

True on the swap.. i read somewhere about dedicating a swap, but perhaps that wasn't OOM related..

 

Most likely my issue was having overlapping addons or other scenery areas that i could unload using SceneryConfigEditor.. i've seen many able to pull off 6.5 for sharp textures, but I need to tweak to figure out what the cause truly was. Probably trying to do too much at once for the sake of "set it and forget it"

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

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

 

I guess there is no way to turn off the dings tho.. (looked into that)..

 

I tried many things so far.. such as turning off all scenery other than the area I was in.. the VAS didnt change.. for instance.. in a non addon area in a default cessna i'm starting off with 2,400,000 or so..

 

Tried cleaning dll and exe.xml's to nothing except FUIPC.. no change.. vas remained same..

Next i switched LOD from 7.5 to 4.5.. it got interesting.. my initial VAS, same situation, started at 2,939,848.. much higher..

 

I was going to start tweaking more in the cfg to see if i can bring the initial numbers down.. or maybe this is just typical initial vas, but i suspect its not (or maybe addon aircraft in the aircraft and simobjects folder can bring the vas up too?).

 

EDIT: oops i think the value displayed was free.. so going from 4.5 to 7.5 free'd up that much more.

Probably unrelated but just for reference.. my 780ti 3GB was using 56% GPU load and 2041MB of ram to and through the initial load point. (if i use 4xSGSS instead of SS, the load becomes 99% but memory still at 2450 max with FTX PNW, rain and clouds)

I guess there is no way to turn off the dings tho.. (looked into that)..

..

I don't think much more can be said than what meshman said above in post #6.  You need to stop looking at all this data and fly.  You are not going to be able to fix it.  Not with high fsx/display driver settings, real weather, FTX PNW, and a commercial aircraft addon running (not to mention all the things in Windows running in the background too).  There have been a lot of members here who have spent much of their time looking at the fps counter and it just creates even more frustrations.  Turn them off and go fly!  Good luck with all of your testing!

 

Best regards,

Jim

When PNW first came out there were many problems with OOM's and after denying it for a while, they finally admitted it and supposidly fixed it. Sounds like the same problem as before, turn it off and see what happens.

I don't think much more can be said than what meshman said above in post #6.  You need to stop looking at all this data and fly.  You are not going to be able to fix it.  Not with high fsx/display driver settings, real weather, FTX PNW, and a commercial aircraft addon running (not to mention all the things in Windows running in the background too).  There have been a lot of members here who have spent much of their time looking at the fps counter and it just creates even more frustrations.  Turn them off and go fly!  Good luck with all of your testing!

 

Best regards,

Jim

 

Well yes, appears that way, however.. hard to fly if FSX suddenly crashes because it runs out of memory  But yes by turn off.. I could turn down the LOD radius.. i dont think background services would affect the VAS size that FSX uses though, could be wrong.  Flying wont truly get back to normal till after the weekend.. have a haswell 4770k and some overclocking to do.. and decide which video card to keep

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.

 

 

i dont think background services would affect the VAS size that FSX uses though, could be wrong

 

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