I guess I will switch back to SYSTEM MANAGED Page File size as I altered it manually awhile ago.

This has NOTHING to do with OOM errors. So altering it either way will do nothing. Your page file is in no way connected to your Virtual Address Space. They call it Out Of Memory but it should be called Out Of Virtual Address Space! Once you hit near 4GB of VAS you will get an error....

 

A couple things I have recently learned that helped with lowering my VAS size...

 

A) Activating only the scenery that I am using for a particular flight using Scenery Config Editor.

 

For example, if I do a flight OMDB-VHHX, only those two sceneries are active in my Scenery.cfg (of course the needed FSX default entries are active as well). But no other addons are active. My CFG had over 600 entries (some V1 MSE titles had 80-90 entries alone), using this little tip I saved over 1GB of VAS.

 

B ) Having only the needed dll's active in the dll.xml file.

 

If you have ORBX addon airports those object flow dll's are hungry little buggers. Activating only the needed dll's in my dll.xml and omitting the ones I ado not need for a particular flight saved me 200MB of VAS.

 

This may not be the be all and end all to OOM problems but I can fly into and between some pretty intense addon sceneries (T2G MMMX, FSDG LGTS)with some VAS hefty planes (ABX, PMDG NGX/777) and have loads of VAS headroom now.

 

And with SCE being FREE, so intuitive and easy to use, it is a no brainer. 

 

I have actually found no effect whatsoever from video card settings in my VAS testing at PMDG. Those operations (AA, AF etc) are all done internally on the video card and from what I've seen stay there - they don't come out into the FSX process's VAS.

This is good to know Ryan.

 

I recall a discussion we all had (a while back) about the "video memory override" tweak and how it had no effect on VAS usage. At that time it was discussed weather or not AF/AA settings got mapped into the FSX.EXE 4GB VAS.

 

It is nice to know that it is not

Agree that OOMs are more an issue with add-ons, not with FSX itself.  I get OOM's in only one region.  Los Angeles.  Where I admittedly have too much going on with add-on.  And even then the OOMs seem more prevalent with one add-on aircraft model (and I am not a PMDG owner).

Two things cured my limited OOMs:

 

BP=0 and affinity mask at 14.

 

This combo of settings shaved about 600mb off my VAS.

Must be a system-system basis... More AA I use the faster I get OOM's - especially in Orbx areas.

 

Gotta love FSX.

 

Is that just your impression or did you actually test it by monitoring the VAS numbers? I set up a controlled scenario where I was loading the NGX and 777 into the exact same situation each time - VAS was consistent within a few 10s of megabytes each time. I then varied the GPU settings and rechecked the scenario numbers each time - they didn't change in anyway outside of the normal little bit of variation I was seeing.

 

Agree that OOMs are more an issue with add-ons, not with FSX itself.  I get OOM's in only one region.  Los Angeles.  Where I admittedly have too much going on with add-on.  And even then the OOMs seem more prevalent with one add-on aircraft model (and I am not a PMDG owner).

 

It absolutely is an issue with FSX itself though - there is a hard limit for how much you can force it to allocate due to it being a 32-bit application. Go over that limit and you're going to get the OOM error every time. I can cause it almost instantly after loading the sim if I activate a bunch of photoscenery and AI traffic and 4096 weather textures and then load the 777 on top of all of that. It's not the literal fault of the addons, it's just the mathematics of how 32-bit memory allocation works. We're at the point where people have to make decisions about what's most important to them in the sim - you can't just throw every single high detail thing at it and expect it to work given the VAS limitation.

Just want to add another voice to what Al and Ryan have posted directly above. In my experience with OOM's, which I actually never had an issue with until this past year, using SCE to limit what was active, and balancing your sliders, was the true solution.

 

With hundreds of addon sceneries installed, it took only one or two sceneries to make the OOM's start happening. I went into research and testing mode, and found by using SCE and only having active the 1) departure addon, 2) the arrival addon, and 3) the alternate addon if applicable, I reduced my VAS load by 400-500mb average.

 

Since using SCE, I've not seen a single OOM since. So I truly recommend doing the same to everyone. Be smart with your setup. Only run what's needed, balance your sliders, and find that sweet spot. In all honesty with today's average systems among what I see users have, those steps are all that are needed. My opinion of course but as you see, more than one testify.

"Two things cured my limited OOMs:

BP=0 and affinity mask at 14.

This combo of settings shaved about 600mb off my VAS."           

 

 

Same thing for me.

 

IAN

It absolutely is an issue with FSX itself though - there is a hard limit for how much you can force it to allocate due to it being a 32-bit application. Go over that limit and you're going to get the OOM error every time. I can cause it almost instantly after loading the sim if I activate a bunch of photoscenery and AI traffic and 4096 weather textures and then load the 777 on top of all of that. It's not the literal fault of the addons, it's just the mathematics of how 32-bit memory allocation works. We're at the point where people have to make decisions about what's most important to them in the sim - you can't just throw every single high detail thing at it and expect it to work given the VAS limitation.

 

Ryan Maziarz

 

FSX platform is obviously dated, and I have seen OOM word creep up over recent years, but never really had to deal with the issue till I started using the excellent PMDG 777.

 

Even when I was flying around in NGX never had OOM, just AppCrashes from sliders or OC being too high.

 

Froogle has a good short vid on OOM , its great starting point for those new to dealing with OOM. Generally the lesson of the video is OOM is directly related to Graphic detail you demand from the sim.

And Always test with bad weather for maximum clouds.

 

Its been said folks need to be selective about their graphic detail sliders to fix avoid OOM, its has nothing to do with how fast CPU or GPU is . And Addon devs can help this situation by developing addons that allow user to switch off parts of addon simulation not required for flight. 

 

Example PMDG allows user to switch certain things FO display from FMC etc, I think it would be noce for new PMDG FMC to have a VAS control section, so user can switch off unneeded aspects of simulation that use more VAS.

 

Currently software technology allows addon devs to maximise resource usage to produce best graphics , but best addons for FSX platform will be those that balance complex Graphics with options to configure VAS usage. For example how much VAS is used up by some of the deep internal PMDG systems simulation that could potential be optional, even at certain phases of flight.

 

Currently technology is too powerful for the 32Gig VAS limit For FSX platform, this means add-ons may need to get creative in what options to provide user interms of VAS management. Offering the latest and greatest graphics is not good enough for the now dated FSX, unless user has some control  VAS consuming options of the simulation.

 

Or we could all simmers and devs just Hop to Xplane at the same time to make life easier for all, but I hear FSX still looks better than Xplane considering FSX 32bit and other 64.

 

If FSx has any future, I suspect future complex addons will have gui screens to control VAS usage options. CPU/GPU are no longer the limiting factor for FSX its now just the dreaded VAS. Am running [email protected] with GTX Titan, 12 Gigs of RAM, currently my only bottle neck is VAS.  

 

FSUIPC always leads the way, we already have the FSUIPC VAS limit warning ping, all we need now Is config options to prevent ever hearing that sound, by setting sliders, not just in FSX detail but also in the addon detail. 

Two things cured my limited OOMs:

 

BP=0 and affinity mask at 14.

 

This combo of settings shaved about 600mb off my VAS.

 

Probably that's why I never, ever had any OOM...

Probably that's why I never, ever had any OOM...

I use BP = 0 for years, but T7 in bad weather, you best off to save your flight before the dreaded the ping.

 

 

This has NOTHING to do with OOM errors. So altering it either way will do nothing. Your page file is in no way connected to your Virtual Address Space.

 

I didn't say it was connected to VAS.  I do not think you have read this topic properly.  Please do not get upset but if you have an out of range page file, you can get OOM's.  We are trying to explain why the OP is having OOM's and his settings are set to way below normal.  An out of whack page file can do this.  I have found that system managed size is the best. 

 

I apologize in advance but this really gets my dander up when people go off and do not read the whole post and understand it fully before commenting.  Now you have people thinking that someone said that page files is connected to VAS and we all know for a fact it is not.  And no one said that or indicated that. 

 

Best regards,

All I did was sit at KSEA with 8xS read vas with process explorer, quit FSX. Changed to 2xSGSS did the same. Just sitting at KSEA was higher (default c172)... Probably a few hundred MB.

 

Other than I've done nothing to compare except time. I've noticed OOM's happen faster if flying with SGSS - I haven't scientifically done any testing though for number of minutes etc.

I didn't say it was connected to VAS.  I do not think you have read this topic properly. Please do not get upset but if you have an out of range page file, you can get OOM's. We are trying to explain why the OP is having OOM's and his settings are set to way below normal.  An out of whack page file can do this.  I have found that system managed size is the best. 

 

I apologize in advance but this really gets my dander up when people go off and do not read the whole post and understand it fully before commenting.  Now you have people thinking that someone said that page files is connected to VAS and we all know for a fact it is not.  And no one said that or indicated that. 

 

Best regards,

I too apologize in advance but it gets my dander up as well when people contradict themselves and start to chase red herrings.

 

I did read this properly and you are confusing me here (that is not hard to do really!).

 

On one hand you say

 

"if you have an out of range page file, you can get OOM's"

 

And on the other hand you say that this is not true and that you agree with me,

 

"Now you have people thinking that someone said that page files is connected to VAS and we all know for a fact it is not. And no one said that or indicated that"

 

So please forgive me Jim. Which one is it?

I too apologize in advance but it gets my dander up as well when people contradict themselves and start to chase red herrings.

 

I did read this properly and you are confusing me here (that is not hard to do really!).

 

On one hand you say

 

"if you have an out of range page file, you can get OOM's"

 

And on the other hand you say that this is not true and that you agree with me,

 

"Now you have people thinking that someone said that page files is connected to VAS and we all know for a fact it is not. And no one said that or indicated that"

 

So please forgive me Jim. Which one is it?

I did not say anything about VAS and that is all I'm trying to clarify.  OOM's can be caused by other things than running out of VAS.  A bad OC, overheating, a not so powerful PSU, bad memory modules, AND an incorrectly configured page file.

 

I do appreciate your help though as I'm NOT the expert here.  The OP has a conservative fsx configuration, no overclock, and he's still getting OOM's.  In any case, I'm just trying to cool things down and get the assistance back on track.  I apologize for being blunt in my first post back to you but it hit a nerve ending when I saw what you were writing.  I'm now going to sit back, take a deep, deep breath and remove myself from further comments.  I hope my recommendations above our comments will help the OP track down his problem and no one should be getting OOM's with his settings.

 

Best regards,

"Two things cured my limited OOMs:

 

BP=0 and affinity mask at 14.

 

This combo of settings shaved about 600mb off my VAS."           

 

 

Same thing for me.

 

IAN

 

Hmmmm,

 

I already have BP at 0

 

But am using:

 

AffinityMask=84

 

Based on my i7 dual core processor using Bojote's automated FSX Tweaking & Tuning Service.

 

OOM's can be caused by other things than running out of VAS.  A bad OC, overheating, a not so powerful PSU, bad memory modules, AND an incorrectly configured page file.

 

I'd venture that absolutely none of these situations would cause an OOM - if they're going to cause an error, it's likely to be in the form of a BSOD. Overheating (of the CPU) is likely to do absolutely nothing except cause it to throttle. In theory an incorrectly configured page file that's too small will cause you to run out of total virtual memory, but I can't even think of an edge case to trigger this that wouldn't make the machine unresponsive from swapping like crazy first.

 

I agree with you that something is funny - I would start with disabling add-ons one by one until one can make the problem start and stop at will. Once one has conclusively identified the problem and can control it, only then can one define the cause. Too many times folks make a series of changes (sometimes forgetting them) after which the problem goes away and they attribute it to an unrelated change.

 

Cheers!

Luke