I edited my post above a little while you responded. read again please.

 

What setting did you change that made your cockpit look horrible?

 

That should not happen and might indicate other problems.

 

Are you sure you OOM?

(you hear a beeping sound before the message "FSX has run out of available memory shows" (or something like that).

 

You are not CDT-ing (Crash to Desktop) are you?

No, its OOM. I have the app that monitors vas usage. I am not sure what I changed to mess up the nighttime cockpit. I altered the settings in the fsx menu, but under the airplane tab I set it to ultra high and that didn't fix it. How can I determine if I am using HD clouds? I use opus with rex textures. I haven't changed the textures lately. 

No, its OOM. I have the app that monitors vas usage. I am not sure what I changed to mess up the nighttime cockpit. I altered the settings in the fsx menu, but under the airplane tab I set it to ultra high and that didn't fix it. How can I determine if I am using HD clouds? I use opus with rex textures. I haven't changed the textures lately.

 

I have updated REX a few months ago (free) to REX essential + HD.

 

Same here, I also use OPUS and REX :-)

 

Start REX. Under options use 1024x1024 3D clouds. (I guess you could use 512x512) as well and see what they look like.

Also tick DXT5 Optimized Clouds! (I dont know what that is but I have been adviced they are better for performance).

 

Important:

Now you have to install those clouds into FSX so it starts using them!

Under "Textures" you select the type of sky/clouds/water/etc textures you want.

Then click "install"

or

Each time you use the "Flight Center" to create a flight plan, at the end you are presented with a "weather textures" button.

Clicking this button (if I remember correctly) should install different clouds/sky/water textures each time. They are selected to fit your flight plan and are different each time.

It takes a little time loading the textures into FSX each time, but the nice thing is that when flying around tropical islands you get tropical water with corals. Next time when you fly over USA only, it will insert water/sky/clouds that are fitting for that flight, etc :-)

 

And it will select those textures according your settings under "options"

.

That is an interesting comment about GPU memory being shadowed in VAS!

 

Is that true?

I thought GPU memory only takes up (is mapped in) RAM space, not VAS?

To answere my own question: Yes that is true!!!

 

I asked a question on an other AVSIM (Hardware) forum.

 

Answere: Yes GPU with more Memory can cause OOMs because it fills VAS !!!

 

 

read here:

 

http://forum.avsim.net/topic/425856-gpu-memory-size-and-influence-on-vas/

I run all textures at 1024 and don't have my LOD radius above the native 4.5. Have AI traffic, autogen, global texture all at high settings. I run my NGX and  T7 out of some payware airports, have FTXG, Traffic 360, and REX all installed. No OOM's, ever. Learning to run FSX within the constraints of its 32 bit architecture is the key. Regards

777Simmer, I'm glad you're VAS is more stable now.

 

Let us know how your other tests get on.

Talking about OOM, is there anything that is non intrusive to display the VAS like (FPS in FSX)?

 

the Process Explorer makes my FSX stutter.    

 

Also I like the idea about disabling AI when enroute and turn them back on approach. I should try this to see if it would reduce the VAS usage.

 

Here is an opportunity for add on developers to build a nice scenery manager where you can give it a flight plan and it would disable all the scenery not on the flt plan map... Or at least make it easier for us to build seperate set of add on scenries activiated by zones and then start FSX with the particular saved flight.  

 

I have  used the freeware ones and they are not that convenient to move sceneries over.to build the scenery.cfg.   I cannot have multiple versions of scenery.cfg since if I have add a new add on scenery, now I would have to go and add them to each scenery,cfg which would cause its own headaches.

I got a response on GPU memory impact on VAS from a source I realy thrust when it comes to hardware and FSX.

 

quote:

Driver model was changed with Vista SP1/Windows7 and GPU memory is not mapped like it was with XP

 

VAS creeping up as the flight continues is normal. Time + scenery/aircraft is your enemy with FSX

unquote.

I performed a test a couple days ago,  As suggested, I turned off all my add-on airports that I wasn't flying from or to, and all UTX and GEX that I wasn't using.  I then did DAL417 KLAX-YSSY.  The flight was 14.5 hours no compression.   My VAS at FSDT KLAX was 2.6 when I loaded.  I then checked again soon after takeoff.  It went down to 2.3.  It stayed at 2.3 all the way out.  I didn't run process explorer live the entire time.  Every couple hours, I would minimize FSX (I run full screen), and then run PE to check VAS.  I was able to land fine, and all was well.  I had Ultimate traffic at 100% commercial traiffic, no GA or moving gates.  I have LOD at 4.5, and TML at 4096.

 

Hopefully it wasn't a fluke.  I'm going to try an 8 hour flight next to see if it's consistent.  Prior to disabling scenery and or add-ons I wasn't using, I could only go about 6 hours.  

 

John

I tested my vas usage again today. I went into rex and switched to the non-hd clouds and used opus. Flying the 737 ngx out of cyul I was at 3.2 to 3.3 usage before takeoff. This is with all traffic turned off. There was an overcast of clouds and there is snow on the ground in montreal. I am using ftx global. I don't know if my vas usage was always so high or what, but that number seems very high before I even get in the air. It stays around 3.3 for the climb and cruise. When I landed at fsdt jfk I was at 3.8 (it jumped up from 3.3 on the approach). On a side note I noticed my night lighting graphics problem occurs when I use the panel lighting in the 737ngx, its really noticeable when I turn the background light dial.  I did recently install EMBSerie HDR Bloom Plugin per the flytampa montreal airport manual and I am wondering if that could be the cause. . 

Using REX (Non HD cloud texture), OPUSfsx and FTX Global.

Only activating the departure and arrival sceneries, the rest of them are disable.

My FSX.cfg setup is based on all the Word Not Allowed's suggestions.

 

Here are my VAS on the following aircraft:

 

* PMDG744  2.900

* LVLD767   3.100

* PMDG737  3.400

* PMDG777  3.800

 

All other payware aircraft are all below the above VAS numbers.

 

Now these are based on the highest dense sceneries like FSDreamteam Vancouver and Wing Creation Narita.

No OOM even on a longest flight which is 16 hrs from Flytampa OMDB to FSDreamteam KDFW.

 

 

 

My system:

Intel i7-3770k CPU

8gb Win7 Home 64 bit

AMD Radeon HD7800 Series

 

 

Kin M.

(Klax)

Using REX (Non HD cloud texture), OPUSfsx and FTX Global.

Only activating the departure and arrival sceneries, the rest of them are disable.

My FSX.cfg setup is based on all the Word Not Allowed's suggestions.

 

Here are my VAS on the following aircraft:

 

* PMDG744  2.900

* LVLD767   3.100

* PMDG737  3.400

* PMDG777  3.800

 

All other payware aircraft are all below the above VAS numbers.

 

Now these are based on the highest dense sceneries like FSDreamteam Vancouver and Wing Creation Narita.

No OOM even on a longest flight which is 16 hrs from Flytampa OMDB to FSDreamteam KDFW.

 

 

 

My system:

Intel i7-3770k CPU

8gb Win7 Home 64 bit

AMD Radeon HD7800 Series

 

 

Kin M.

(Klax)

This is what your vas is at the end of the flight or starting out? How are you disabling your other airports? Using the program mentioned in the 777 manual or the fsx scenery list?

This is what your vas is at the end of the flight or starting out? How are you disabling your other airports? Using the program mentioned in the 777 manual or the fsx scenery list?

This is at the end of the flight. They usually start at 2.300 and if you use a lot of spot outside view the number increases.So i stick my view inside the virtual cockpit using EZdok and short cut command outside view on my joystick hat switch.

Before starting a flight, i go to library setup and activate the airports i will be using example KLAX to OMDB. Then launch it using my default single prop aircraft on my home airport, then exit. Setup my flightplan using flight commander, send it to my EFB, launch FSX again, select a PMDG aircraft and my departure airport which in this case LAX. If i have time i will do a cold start or just with engine running before pushback. Setup my FMC and take off config..etc.

 

Kin M.

(Klax)

This is at the end of the flight. They usually start at 2.300 and if you use a lot of spot outside view the number increases.So i stick my view inside the virtual cockpit using EZdok and short cut command outside view on my joystick hat switch.

Before starting a flight, i go to library setup and activate the airports i will be using example KLAX to OMDB. Then launch it using my default single prop aircraft on my home airport, then exit. Setup my flightplan using flight commander, send it to my EFB, launch FSX again, select a PMDG aircraft and my departure airport which in this case LAX. If i have time i will do a cold start or just with engine running before pushback. Setup my FMC and take off config..etc.

 

Kin M.

(Klax)

I thought it was determined that the exterior views didn't increase vas usage. I love looking at my plane from the outside and never noticed vas going up when I did so. 

I thought it was determined that the exterior views didn't increase vas usage. I love looking at my plane from the outside and never noticed vas going up when I did so.

 

Same here, when outside VAS increases by 100-150Mb and when returning to inside the VC, after a few seconds, VAS decreases again by the same amount.

 

So NO, outside does not increase VAS.

Refrase: No, ON MY SYSTEM, going outside does not decrease VAS.

 

The discussion about VAS has become real interesting here:

 

http://forum.avsim.net/topic/425856-gpu-memory-size-and-influence-on-vas/

 

And it has been confirmed that the problem is that FSX does not defragment or clean up garbage in VAS which causes it to fill up untill FSX stops working.

And this is worse if you use 4096 textures in scenery/aircraft.

 

So with that in mind, if one person uses 4096 textures and another does not....their results in VAS defragmentation/use could be quite different when going inside/outside several times. One persons VAS could be quickly depleted (4096 user) while the other users VAS stays at the same level (1024 user).

(I am using the word "could" because I dont know if users with 4096 textures have the inside/outside VAS increase problem or not. All I am saying is that that could be the case!)

 

This is something each user can easily test on his/her system with Process Explorer though!

I find what works for me, and I'm running Windows 8.1 with dual monitors at full screen in FSX. As I am approaching my destination I'll start hearing the Windows bling warning and know OOMs is imminent I do a ALT Enter and switch to windowed view full screen and the OOMs don't occur. Bit of a band aid solution but at least I can land and get to the gate.