Rob,

 

Whatever your findings, thank you for taking the time to test.

 

I look forward to your results.

......

Apart from being wrong, it simply becomes confusing if some people say VAS dropped when VAS actually went up. That's all. In one post someone might say VAS went up and in the next post someone might say VAS went down while they actually meant the same… that's what I'd call confusing!

Don't tell me that this is wrong because the VAS is in our case always 4 GB and the monitor shows what's left for the FS!

 

I'm sure everybody understand this and if you get confused with this term then you need to adapt yourself instead of trying to convince me using other terms to make you feel comfortable.

Spirit

 

 

Like I suggested elsewhere, log the FSUIPC VAS to the FSUPIC logfile and graph it in a spreadsheet. Picture shows clearly then exactly what is happening. VAS is being depleted / used / memory space is dropping! I call that depletion in VAS just as firehawk does i.e the byte count is going down (well not always hint hint)!

 

Great post and clarification of the issue Robin!  I'm off right now to go and celebrate President's Day with friends and family so I won't be able to test for a while but actually my testing is done and I have submitted my results.  I think everyone needs to log it to the fsuipc log and they'll be able to see the depletion much better.  Unfortunately you need the registered version to get this VAS reading during your flight.  Perhaps Col (Ret) Bob Scott's freeware version has a log too.  Good luck on your testing!

 

Best regards,

 

The FSUIPC log stated I had 2.37 GB's of VAS when the flight started.

 

The rest of your post makes clear that you had 2.37 VAS remaining… and not a VAS of 2.37. VAS was 1.63. LOL I meant to make things more clear but it only seems people are getting more confused. ^_^ Maybe it's because I started off with Process Explorer with shows currently used VAS so I start off with for instance 2.1 and slowly it climbs to 4. I just thought it was confusing that everyone is using different terminology but it seems we can't get a consensus on this. The next time I read a post about VAS I will double-check the numbers and simply see for myself if the poster is talking about VAS used or VAS remaining.  ^_^

Don't tell me that this is wrong because the VAS is in our case always 4 GB and the monitor shows what's left for the FS!

FSUIPC displays the remaining "free VAS" out of the possible 4GB. That is why it decreases in value, and rarely increases.

 

Right now for example:

1,552,480 = Process Monitor: VAS Used

2,641,696 = FSUIPC VAS: Free

_________

4,194,176 = Total VAS

 

As the VAS Used reported by Process Monitor increases, the VAS Free reported by FSUIPC will decrease by the same amount... :Nerd:

I have W 8.1 and Prepar3D V2.1 when the VAS is just over 3.000.00 more o less I get a OOM. I can see in this foro that the limit is 4.000.000. How could I increase my VAS to this limit?

 

Thank in advance,

 

 

Francisco Mateos

I have W 8.1 and Prepar3D V2.1 when the VAS is just over 3.000.00 more o less I get a OOM. I can see in this foro that the limit is 4.000.000. How could I increase my VAS to this limit?

 

Thank in advance,

 

 

Francisco Mateos

 

You can't. The max VAS is 4 GB but somehow P3D gives an OOM long before it reaches that 4 GB: could be fragmentation or maybe a memory leak (but the jury hasn't decided on that yet ^_^ ).

Thanks for clarifying the FSUIPC VAS number.     So I flew from east coast to west coast in a very complex aircraft and my 'remaining' VAS was 580450.  It actually went up and down a small amount around 600000 most of the flight.  

 

So what is so different about my 3yr old PC that allows me to run smooth long flights with no OOM???   I am not being a smart a$$, legitimately trying to understand to help others!

 

Rob

 

 

So what is so different about my 3yr old PC that allows me to run smooth long flights with no OOM???

 

Must be your settings and your scenery! Simple as that! My PC is 3 1/2 years old and I can fly the A2A C172 above FTX Global and finish my regular flights (around 30 to 45 minutes) without an OOM as long as I keep tree autogen at Dense (buildings at Dense: other settings are medium to slightly high). Trees at Very dense is on the edge and flying above FTX AU is impossible so I uninstalled that one. It all comes down to making the right choices.

... the right choices. LoL 

 

FTX AU is more valuable than trees at very dense. :rolleyes:

Ok... VAS neither increases nor decreases for a 32-bit application. It is either 3GB or 4GB depending on OS and compile flags in the application.

 

The only thing that changes is the amount of allocated VAS. How you 'view' it is kind of like the glass half full versus glass half empty argument. You can either view it as the amount in use or as the amount yet to be used. FSUIPC displays the amount yet to be used whereas most applications display the amount in use.

... the right choices. LoL 

 

FTX AU is more valuable than trees at very dense. :rolleyes:

 

LOL Well, yeah, it all depends on ones personal preference... ^_^ I can't stand autogen lower than Dense: that's my limit! :rolleyes:

Ok... VAS neither increases nor decreases for a 32-bit application. It is either 3GB or 4GB depending on OS and compile flags in the application.

 

The only thing that changes is the amount of allocated VAS. How you 'view' it is kind of like the glass half full versus glass half empty argument. You can either view it as the amount in use or as the amount yet to be used. FSUIPC displays the amount yet to be used whereas most applications display the amount in use.

 

Correct. Thanks for this crystal clear explanation. I was only hoping we could all agree on the same terminology to prevent confusion, that's all. When you read in one post 'VAS is 2.6' and in the next post that 'VAS is 1.4' and they actually mean the same, I find that confusing...! So I was hoping that we could agree on calling allocated VAS 'VAS' and remaining/free/available VAS 'remaining/free/available VAS'. ^_^ I also thought this was the most commonly used terminology hence my preference for calling it like that. If it's more common to call it the opposite, then let's all do that. The same goes for 'VAS going up' and 'VAS going down'. Usually allocated VAS goes up and free VAS goes down.

 

Obviously all this isn't a big deal, at least not as big as it is becoming now LOL

You can't. The max VAS is 4 GB but somehow P3D gives an OOM long before it reaches that 4 GB: could be fragmentation or maybe a memory leak (but the jury hasn't decided on that yet ^_^ ).

I've been doing fine with VAS @3,8GB in v2.1. I never reached more than 3,4 before OOM in v2.0. That said, I've had some strange CTDs, so we're still a long way from P3D being anything like MS Flight was in terms of stability.

Here's a very un-scientific  test.  Since I have been reading all these threads (and blogs) on how P3Dv2 practically causes instant OOM's and crashes and the like, thought I would try a little flight.  Well, I am in the middle of it right now.  Been goin' on for 1 1/2 hours.  Still smoooth as a baby's butt and no OOM.  Heard of the "tree theory" OOM so I took off from Seattle and headed East.  Altitude 12,500 feet at 250 knots.  Veg autogen slider at Dense.  At this altitude seeing 1000's of trees as a ramble along.

 

Now here is something,  after one hour in flight I decided to use the overhead "world view"  to see where I was.  So I zoomed out to see the whole USA.  Guess what.  Started  to hear the FSUIPC warning bell going off.  So I went back to outside spot view and and the bell kept dinging.  Wast expecting to OOM any second.  But I let it continue for 5 more minutes with it still dinging so I knew I was close.

 

SO what I did was use my hat switch and move my view under the aircraft (an Airbus A318), so only the sky was in the shot.  And the "dinging stopped".  Does that mean P3D cleared up some extra VAS space for me?   So pointed my view back to the ground with all those 1000's of trees and still no ding now.  Flown now an additional 1/2 hour.  Still silky smooth.  FPS in the 50's.  About 2 hours into flight.  Using one display to do my work while the other display is simming. 

 

Granted, this is using pretty much default stuff.  But was to test the "memory leak" squabble due to autogen trees.  Not seeing it. 

I also see VAS increase when changing to top-down view and zooming-out. After resetting to spot view, the VAS gradually reduced to its previous level.