Sign in to follow this  
MDF86

Crazy High VAS Usage

Recommended Posts

Hi Guys

 

I am struggling with really high VAS usage and don't know what I am doing wrong.

 

As an example, I just spent ages planning a flight, and couldn't even get to the runway of my departure airport before I got an OOM. My VAS was 3.85GB just sat at the gate.

 

I was at Flightbeam KSFO with ORBX NCA enabled, in the NGX, using UT2. I know these are all demanding addons but everyone else seems to be able to manage to use high quality addons and keep their VAS to a reasonable level.

The only real tweaks I've used in the fsx.cfg are:

 

AffinityMask=14

 

DX10 mode enabled

 

TEXTURE_BANDWIDTH_MULT=80

 

TEXTURE_MAX_LOAD=2048

 

HIGHMEMFIX=1

 

I know that TML could be reduced to 1024 but surely it's not going to make that much difference. Surely something is wrong if I'm at nearly 4GB just sat at the gate before I even depart!

 

Anyone got any tips?

 

Thanks

 

EDIT - I also use scenery config editor so that just my departure and arrival airport are enabled, I thought this would help - obviously not much!

 

Also, when I first start FSX, when I'm at the free flight menu, my VAS usage is already 1.7-1.9GB - is that normal? It seems really high, before I've even gone anywhere other than the main menu. That's with the default trike loaded! So that's before the NGX, UT2 rendering AI traffic, ORBX, Flightbeam KSFO loading etc...seems very high.

 

FURTHER EDIT - TML of 1024 makes no difference. Still 3.8-3.9GB before I've even taken off from KSFO...

Share this post


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

Have you tried it with NCA disabled ? I don't have NCA, so cannot test that for you. But I can fly KSFO to OMDB in the T7, with a save and restart 100nm before TOD.

Share this post


Link to post
Share on other sites

Have you tried it with NCA disabled ? I don't have NCA, so cannot test that for you. But I can fly KSFO to OMDB in the T7, with a save and restart 100nm before TOD.

 

No I haven't, will test and report. But seems crazy that I would have to disable something like that just to be able to even take off. I see people with poorer hardware setups than me able to use plenty of demanding addons all at once, and it's not like I'm running everything maxed out.

 

20% airline density, low 2x water, normal autogen....something seems not right.

EDIT - Disabling NCA saved me around 400MB of VAS, which says to me that I will need to disable the ORBX regions when flying the NGX. That's very disappointing indeed.

 

I know they're designed for GA flyers, but even so....

Share this post


Link to post
Share on other sites

You quote 1.7-1.9 GB - is that starting in NCA? If not it's too high - in default areas mine starts at around 1.1 - 1.2GB.

 

Those addons seem like a recipie for disaster. I don't run with UT2 or any traffic addons.

Share this post


Link to post
Share on other sites

Just did a few tests at KSFO to see how the various addons affect VAS (my set up also uses UT2 traffic at 50% and has most sliders close to being maxed out except autogen scenery at very dense so I am perhaps pushing FSX a bit too far!)

 

No addons + default Baron at KSFO                                 Max VAS  = 2.29

Add FTX-NCA                                                                    Max VAS  = 2.58

Add FTX-NCA + FB KSFO                                                 Max VAS = 3.06

 

So it seems that FTX-NCA does not have a huge impact on VAS although FB KSFO has a bit more. Add to that however the VAS requirement of one of the resource intensive PMDG aircraft and you will not be far from the 4GB critical point.

 

Bill

Share this post


Link to post
Share on other sites

You quote 1.7-1.9 GB - is that starting in NCA? If not it's too high - in default areas mine starts at around 1.1 - 1.2GB.

 

Those addons seem like a recipie for disaster. I don't run with UT2 or any traffic addons.

 

That's not even with a flight loaded Ryan, that's at the free flight menu with the default trike selected.

Just did a few tests at KSFO to see how the various addons affect VAS (my set up also uses UT2 traffic at 50% and has most sliders close to being maxed out except autogen scenery at very dense so I am perhaps pushing FSX a bit too far!)

 

No addons + default Baron at KSFO                                 Max VAS  = 2.29

Add FTX-NCA                                                                    Max VAS  = 2.58

Add FTX-NCA + FB KSFO                                                 Max VAS = 3.06

 

So it seems that FTX-NCA does not have a huge impact on VAS although FB KSFO has a bit more. Add to that however the VAS requirement of one of the resource intensive PMDG aircraft and you will not be far from the 4GB critical point.

 

Bill

 

Seems I will need to disable all of my ORBX areas when flying with the NGX, what a bummer. Have tried with UT2 on and off and UT2 seems to make very little difference. I will have to hope that ORBX OpenLC makes flying at high altitude a bit more interesting, the default (even with FTX Global) looks garbage.

Share this post


Link to post
Share on other sites

What is your Autogen setting?  FTX/Orbx scenery likes trees (as well as Orbx/FTX users!!) and, in a previous version of the Lockheed Martin P3D, Autogen was eating up VAS and many were suffering OOM's. Lockheed Martin changed the VAS memory footprint per tree and reduced the footprint from 276 bytes to 16 bytes (a 17x reduction in system memory per tree). So, if you have Autogen turned up to the max or above "normal", this could be taking an enormous amount of VAS and you will suffer an OOM faster the higher you place the Autogen setting. Check out the FTX scenery guides for Autogen recommendations and/or lower your settings.

 

Texture_Max_Load above 1024 and LOD_Radius above the 4.5 max will also use a lot of VAS during the flight. You have to compromise. I would suggest that the TML and LOD_Radius are based on the FSX defaults the FTX developers used for their products. Going higher is only going to cause issues.

 

Best regards,

Share this post


Link to post
Share on other sites

What is your Autogen setting?  FTX/Orbx scenery likes trees (as well as Orbx/FTX users!!) and, in a previous version of the Lockheed Martin P3D, Autogen was eating up VAS and many were suffering OOM's. Lockheed Martin changed the VAS memory footprint per tree and reduced the footprint from 276 bytes to 16 bytes (a 17x reduction in system memory per tree). So, if you have Autogen turned up to the max or above "normal", this could be taking an enormous amount of VAS and you will suffer an OOM faster the higher you place the Autogen setting. Check out the FTX scenery guides for Autogen recommendations and/or lower your settings.

 

Texture_Max_Load above 1024 and LOD_Radius above the 4.5 max will also use a lot of VAS during the flight. You have to compromise. I would suggest that the TML and LOD_Radius are based on the FSX defaults the FTX developers used for their products. Going higher is only going to cause issues.

 

Best regards,

 

Jim - autogen set to normal, one of the first things I dialled back to try and improve the situation.

 

I tested TML of 1024 vs 2048 and noticed almost nil difference in my reported VAS usage in Process Explorer. Could you do me a favour and load up the free flight menu and see what your VAS usage is before you even start a flight? In the default trike I'm showing 1.7GB of VAS usage before anything's even loaded and I've begun a flight. That's almost half gone before I start loading up complex scenery, aircraft and AI. This seems really high, is it normal?

 

Thanks

Share this post


Link to post
Share on other sites

If you're in Seattle that's probably right...

 

I forgot to mention mine is in the boonies away from any payware scenery...

Share this post


Link to post
Share on other sites

I got similar results with OrbX PNW at Seattle, with the PMDG 777. I would get the low VAS ding from FSUIPC right after taking off. That's with OrbX standard KSEA and no traffic add ons.

 

edit: Why the heck am I commercial member? hahah

Share this post


Link to post
Share on other sites

edit: Why the heck am I commercial member? hahah

If you're not a commercial member, let me know. Sometimes our big thumbs hit the wrong key....

 

Could you do me a favour and load up the free flight menu and see what your VAS usage is before you even start a flight? In the default trike I'm showing 1.7GB of VAS usage before anything's even loaded and I've begun a flight.

FWIW, I start off with 3.34GB and, after loading the default flight 2.73GB. I think normal. I use the SceneryConfigEditor and only load the scenery I will be using during a particular flight session as I have a ton of Photoscenery. Photoscenery continues to load and take up resources even when not being used so it must be disabled. A lot of Orbx scenery is photoscenery. Unfortunately, you cannot mess with what loads/does not load with Orbx/FTX scenery as that will mess up FTX Central and your scenery.cfg. But, if you are real careful, I have disabled Orbx/FTX scenery I won't be using before a flight and had no problems as long as I remembered to reenable and restart FSX before going into FTX Central and enabling/disabling the Orbx settings. You can also disable FTX scenery you will not be using in the Scenery Library but don't forget to reenable it before shutting down FSX.

 

VAS will fluctuate up and down during a flight. I have all of my VAS usage sent to the FSUIPC log and I can immediately analyze what I started out with and what I had when I ended the flight. I saw many times where the VAS would increase. It all depended where I was located.

 

Best regards,

Share this post


Link to post
Share on other sites

If you're not a commercial member, let me know. Sometimes our big thumbs hit the wrong key....

 

Indeed I am not a commercial member. Thanks for the help!

Share this post


Link to post
Share on other sites

That's not even with a flight loaded Ryan, that's at the free flight menu with the default trike selected.

 

It might help if you add the "DisablePreLoad" tweek in the fsx.cfg under the MAIN section. Like this:

 

[MAIN]

DisablePreLoad=1

 

That should keep the scenery in your default flight from loading.

Share this post


Link to post
Share on other sites

You have duplicate afcad files. In the NCA scenery folder remove the 2 KSFO bgl files, do this for any other adddon airports you have in the area. That's the main cause of your oom errors.

Share this post


Link to post
Share on other sites

You have duplicate afcad files. In the NCA scenery folder remove the 2 KSFO bgl files, do this for any other adddon airports you have in the area. That's the main cause of your oom errors.

 

A nice thought, thanks, however these are already named to "OFF" files per the NCA instructions, so that they don't conflict. So they won't be loading anyway.

Share this post


Link to post
Share on other sites

I've found the problem, folks!!

 

I have an awful lot of ORBX regions and airports (Australia, England, USA, Canada....) and disabling all of the regions and airports other than NCA has saved me nearly 1GB of VAS under the same testing scenarios.

 

I always disable the addons I'm not using during a particular flight, but was warned not to touch the ORBX stuff in Scenery Config Editor, however I thought I had nothing to lose, so made a backup of my scenery.cfg and then disabled all of my other ORBX products other than NCA.

 

Result? 3.1GB sat at the gate at FB KSFO instead of 3.9-4.0GB.

Share this post


Link to post
Share on other sites

Did you put in the disable pre load as Jesse posted ?

Share this post


Link to post
Share on other sites

Did you put in the disable pre load as Jesse posted ?

I already had that, meant to say. However since disabling all the ORBX scenery I'm not using during that flight, my VAS on loading FSX has gone from 1.7gb to ~1gb.

 

Crazy how this stuff can consume so much VAS when you're hundreds, if not thousands of miles away from it!

Share this post


Link to post
Share on other sites

I already had that, meant to say. However since disabling all the ORBX scenery I'm not using during that flight, my VAS on loading FSX has gone from 1.7gb to ~1gb.

 

Crazy how this stuff can consume so much VAS when you're hundreds, if not thousands of miles away from it!

Yes, I know, amazing. I disable Orbx airports in Scenery cfg editor without any problems  So you should be good to go now.

Share this post


Link to post
Share on other sites

Yes, I know, amazing. I disable Orbx airports in Scenery cfg editor without any problems So you should be good to go now.

Does it cause issues switching between regions in FTX Central if you have particular regions deactivated?

 

For example if I'm flying between two airports in Australia I will now have only those two airports activated in SCE, plus the AUS region areas.

 

If I then go into FTX Central and switch to North America whilst my NCA, PNW and various airports are disabled, is that going to screw things up?

 

Thanks.

Share this post


Link to post
Share on other sites

Does it cause issues switching between regions in FTX Central if you have particular regions deactivated?

 

For example if I'm flying between two airports in Australia I will now have only those two airports activated in SCE, plus the AUS region areas.

 

If I then go into FTX Central and switch to North America whilst my NCA, PNW and various airports are disabled, is that going to screw things up?

 

Thanks.

 

Hello!

From my perspective and "experience" all i can say is this:

I have almost all ORBX regions and airports installed and whenever i fly with rather demanding planes such as the PMDG 777 or NGX or so, i do undertake the following steps in advance:

 

1. Load FTX Central and set it to the ORBX-region i intend/plan to fly at (North Americ, EU, ...)

1a. Start up FSX and let it load the then new scenery libary - shut down FSX again right away afterwards.

 

2. Open up the scenery config editor and disable ALL sceneries (not just the ORBX ones!) where i am not going to fly at, yet only leaving the ORBX region and the departure and arrival airports i am going to fly around at enabled.

It is furthermore important though to leave two ORBX entries always enabled, if You intend to fly at any ORBX region or airport.

These two entries are labeled "ORBX libraries" and "airports" or so - Sorry, i do not have the exact name at hand now, but if it is to unclear which two entries i refer to, then please let me know and i will check out when i am at my FSX-PC again).

2a. Save this new library in the scenery config editor, start up FSX again and let it build the new scenery library - and now all should work like a charm!

Hope that helps - if any more information is required, then please let me know and i will try to offer a more detailed answer as soon as possible.

 

P.S.: There is no need to always undertake these steps as outlined here above - it is only required if You are changing between various ORBX "continental-regions", so:

If You for instance want to fly in any North American-ORBX region (PNW, SAK, ...) and let's say from KSEA to PAJN at one day and from, let's say KSEA to KJAC the other day, then all it takes is to enable/disable the various airport sceneries (PAJN or KJAC in this case) and nothing else!

If You want to fly in Australia however the other day, then undertaking the steps outlined above are mandatory to have it all working properly.

 

Hope i could help a bit to clarify all that stuff.

Share this post


Link to post
Share on other sites

Hello!

From my perspective and "experience" all i can say is this:

I have almost all ORBX regions and airports installed and whenever i fly with rather demanding planes such as the PMDG 777 or NGX or so, i do undertake the following steps in advance:

 

1. Load FTX Central and set it to the ORBX-region i intend/plan to fly at (North Americ, EU, ...)

1a. Start up FSX and let it load the then new scenery libary - shut down FSX again right away afterwards.

 

2. Open up the scenery config editor and disable ALL sceneries (not just the ORBX ones!) where i am not going to fly at, yet only leaving the ORBX region and the departure and arrival airports i am going to fly around at enabled.

It is furthermore important though to leave two ORBX entries always enabled, if You intend to fly at any ORBX region or airport.

These two entries are labeled "ORBX libraries" and "airports" or so - Sorry, i do not have the exact name at hand now, but if it is to unclear which two entries i refer to, then please let me know and i will check out when i am at my FSX-PC again).

2a. Save this new library in the scenery config editor, start up FSX again and let it build the new scenery library - and now all should work like a charm!

Hope that helps - if any more information is required, then please let me know and i will try to offer a more detailed answer as soon as possible.

 

P.S.: There is no need to always undertake these steps as outlined here above - it is only required if You are changing between various ORBX "continental-regions", so:

If You for instance want to fly in any North American-ORBX region (PNW, SAK, ...) and let's say from KSEA to PAJN at one day and from, let's say KSEA to KJAC the other day, then all it takes is to enable/disable the various airport sceneries (PAJN or KJAC in this case) and nothing else!

If You want to fly in Australia however the other day, then undertaking the steps outlined above are mandatory to have it all working properly.

 

Hope i could help a bit to clarify all that stuff.

That's perfect, thanks! That's basically what I do anyway (with the exception that I never disable ANY ORBX stuff through SCE).

 

But since I re-did my test with the ORBX sceneries and airports I'm not using disabled, it's clear how much VAS they are hogging just from being enabled.

 

Thanks for outlining the FTX central part of the process, that all makes sense to me. Here's to OOMs becoming a thing of the past!

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