Sign in to follow this  
mac44

OOM memory errors in my P3Dv3

Recommended Posts

Running P3Dv3 on a fairly high end PC (6700, 16gb memory and x2 980Ti cards) and have started getting some OOM errors since I installed a few adds - including 737NGX, orbx (global, vector, a few different airports), MT6, Active Sky Next - I typically get the errors not on every flight but occasionally usually at busy airports flying the 737 - have never had them before so just wondering if there is any way to minimise them? (note I do have many of my settings maxed out but frames are usually ok typically 20-50fps depending on the situation - also running it on a 4k monitor)

Any help appreciated.....

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

The usual suspects are to blame for OOM errors, heavy air traffic, complex aircraft, a lot of addon's. I have noticed that on my machine, Vector uses a ton of VAS. Sorry I don't have a magic bullet fix for you.

Share this post


Link to post
Share on other sites

Running P3Dv3 on a fairly high end PC (6700, 16gb memory and x2 980Ti cards) and have started getting some OOM errors since I installed a few adds - including 737NGX, orbx (global, vector, a few different airports), MT6, Active Sky Next - I typically get the errors not on every flight but occasionally usually at busy airports flying the 737 - have never had them before so just wondering if there is any way to minimise them? (note I do have many of my settings maxed out but frames are usually ok typically 20-50fps depending on the situation - also running it on a 4k monitor)

Any help appreciated.....

 

Be careful with Vector I have most items disabled only highways / primary roads / and beaches never had an OOM in P3D ;-)

 

Few other items to be careful with:

- AI aircraft

- TEXTURE_MAX_LOAD=

- Lod radius

- Cloud cover and view setting ASN

- Shadow texture size

- Play with sliders to find a nice balance for your system ;-)

Share this post


Link to post
Share on other sites

You can also use Air Traffic Manager (needs FSUIPC as well) to pare down the amount of traffic...it'll allow you to keep traffic at the fields you're flying from/to while killing off a lot of traffic off in the distance you wouldn't even see.

 

Also, make sure you've disabled ADE files in MT6 that may coincide with other add-on scenery.  MT6 has a scenery directory with ADEs (aka AFCADs) for most medium to large airports worldwide, and having duplicate airport files can cause all sorts of unhappiness.

 

HD clouds and lots of ASN cloud layers can eat your lunch as well.

 

Regards

Share this post


Link to post
Share on other sites

bob thanks

1)have heard of air traffic manager - but have seen a few of them in various forums do you have a download link?

2)Actually have a FSUIPC licence but I haven't installed it - how do I get the 2 working together?

Share this post


Link to post
Share on other sites

Link to ATM:  http://www.avsim.com/topic/451383-traffic-optimizer-for-fsxp3d/

 

Once you install FSUIPC and register it (in accordance with the instructions that come with it), it will run when P3D starts.  When it's running, ATM will connect through it automatically.

 

I also included a very compact VAS reporting tool with my QuantumLeap utility (d/l in the AVSIM library)...it also works through FSUIPC (or through WideFS over a LAN as well)

 

Regards

Share this post


Link to post
Share on other sites

OOM's can happen on super powerful computer systems too because, when you run out of the allocated 4GB's of virtual address space (VAS) that you operating system provides, you will get an OOM.  Just in case you have not seen this from PMDG - http://support.precisionmanuals.com/kb/a108/vas-management-stopping-out-of-memory-oom-errors.aspx.

If you have high setting/overclock, I would think your VAS usage would be depleted faster as it is processing things faster.  Only when we get to the 64 bit applications will we be truly able to crank up our powerful systems as VAS will still be limited in 64 bit applications but the amount of VAS Windows allocates will be almost impossible to deplete.  Lockheed Martin did do some optimizing of their graphics and other things that could be optimized but it does not eliminate OOM's.  I use the freeware tool called FSUIPC to monitor my VAS usage during a flight and, when it starts going down to a level that will cause an OOM, I will turn off things that might be causing the loss, like my weather program, ASN.  On page 3 of the AVSIM CTD Guide (link in my signature), we provide instructions for configuring the FSUIPC tool -

 

Monitor VAS (modified from the guide to show only the information you need as you have a 64 bit operating system)

Startup program and then enter the Add-on Menu and select FSUIPC.  Once FSUIPC is open, click on the Logging Tab and enter 024C under Offset and select S32 under Type. Select where you would like to have the usage displayed.  The FS Window is for Full Screen sessions.  The FS Title Bar is for Windowed Mode.  AVSIM recommends you also check the Normal log file as this provides you information on how much VAS you had to start out with and then logs usage throughout your flight. 

The VAS usage is displayed in Kilobytes (KB’s).  The value represents the amount of VAS left so, the lower the value, the more VAS being depleted.  The max amount of VAS allowed in computers with 64 bit Operating Systems is 4GB’s if running 32 bit applications like FSX/P3D. 

To convert the KB’s to the amount of GB’s, you should use one of the Byte converters on the Internet like the following:  Byte Converter. You will never see 4194304 KB’s displayed as this equals 4GB’s.  You might see around 3GB’s (3145728) remaining when you first start up FSX/P3D but that too would be unusual.  Do not be concerned with the amount of VAS remaining when you first start up. It fluctuates during a flight session.

 

One of the things I do after using FSUIPC to monitor my VAS usage is to open up the FSUIPC.log after a flight and review it (I have a shortcut to the fsuipc.log on my desktop).  It will show you how much VAS was used just to load P3D to the setup screen, then loading to your departure area in your flight plan, and then showing the VAS usage during the flight.  You will always see VAS going down dramatically as you descend to your destination.  the log will also show you the average FPS during the flight and average VAS usage.

 

Sometimes I'll run Process Monitor which I configured to run and only show P3D and P3D addon's loading (see page 4 of the AVSIM CTD Guide).  I want to make sure there are no scenery loading on the other side of the world where I'm flying.  Photoscenery will load if enabled even if the scenery is located on the other side of the world and take up valuable VAS.  I have seen FTX/Orbx stuff loading too that is far, far away from my flight plan but it is usually the Orbx/FTX Objects loading.  Nothing you can do if you are flying over FTX areas but it is upsetting to see these object loading thousands of miles away.  But, there are things I might see that I can shutdown during the flight.  Maybe that will help, maybe not. 

 

You know we really did not have these problems when FSX (P3D is basically FSX as it uses the same engine) was first released.  We had less powerful systems back then and everyone kept their settings at a modest level.  Everything was 32 bit then.  Then we heard about a /3GB switch that would give us up to 3GB's of VAS (we only had 2GB's of VAS available then to use) and we started cranking up our FSX settings thinking we had more space and power.  Some computer experts gave us tips on tweaks we could use to maximize our enjoyment of FSX.  Now, we have extremely powerful systems (compared to the systems back in 2006/2007), 64 bit operating systems, the ability to overclock, and we all think we can now max things out.  We could except for the VAS limitations.

 

Hope this helps.

 

Best regards,

Share this post


Link to post
Share on other sites

You can also use Air Traffic Manager (needs FSUIPC as well) to pare down the amount of traffic...it'll allow you to keep traffic at the fields you're flying from/to while killing off a lot of traffic off in the distance you wouldn't even see.

 

Also, make sure you've disabled ADE files in MT6 that may coincide with other add-on scenery.  MT6 has a scenery directory with ADEs (aka AFCADs) for most medium to large airports worldwide, and having duplicate airport files can cause all sorts of unhappiness.

 

HD clouds and lots of ASN cloud layers can eat your lunch as well.

 

Regards

 

 

Can you please explain how to do this?  Thanks!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this