Hi Folks:

I'm really curious to investigate why I'm having two very different VAS consumptions in my two setups (one is my main PC sim machine, a desktop, and the other is a gaming laptop that I use for testing, traveling, etc.; both specs are described on my forums signature). Both machines are running P3Dv3.4.9 and the scenery and add-ons are mostly the same, with very minor differences. The desktop PC is running Windows 7 Ultimate and the laptop is running Windows 10 Home.

The fact is than in my laptop, the VAS consumption is 400-450 MB higher in average, in comparison to my desktop.

I thought everything was more or less similar between the two machines, until I did several tests going to default airports after installation of the newly released REX WWA HD, when I realized those differences.

Anyone can help to point me in a direction to find the root causes of this?.

Thanks.

Cheers, Ed

 

Ed,

 

Desktop: "GeForce GTX980 4 GB"

Just for info, what is it on the Laptop?

 

Just to verify .. you are not getting OOM's , correct?

 

Maybe the textures are handled different Win7 vs Win10.

 

Maybe a pilot using Win10 could test.

Ed,

 

Desktop: "GeForce GTX980 4 GB"

Just for info, what is it on the Laptop?

 

Just to verify .. you are not getting OOM's , correct?

 

Maybe the textures are handled different Win7 vs Win10.

 

Maybe a pilot using Win10 could test.

 

On laptop, GTX980M 8 GB.

I'm not usually getting OOMs, but when I go to KEWR (for instance), on my laptop, the VAS remaining gets quickly to 100 KB (and to 500 KB on desktop, same scenario) when panning around the aircraft (you know, that's a congested area, and I have NYC Drzewiecki installed), and you can hear the classic ding coming out FSUIPC.

Cheers, Ed

On laptop, GTX980M 8 GB.

I'm not usually getting OOMs, but when I go to KEWR (for instance), on my laptop, the VAS remaining gets quickly to 100 KB (and to 500 KB on desktop, same scenario) when panning around the aircraft (you know, that's a congested area, and I have NYC Drzewiecki installed), and you can hear the classic ding coming out FSUIPC.

Cheers, Ed

 

Maybe Rob can chime in Ed  :wink:

Ed,

 

How do you check your VAS remaining?

Hi Martell, I use FSUIPC offset 024C, it gives you the VAS remaining in your main display.

Cheers, Ed

I've almost given up trying to discover why idling at default KEWR (/w all the Orbx, REX, AS etc standard addons) in the NGX starts at 1.3 gigs remaining and decreases over time to 700 megs. Really hoping either P3D goes 64 bits soon or DTG's flight sim surpasses it. It's not so much the FS developers at fault here, it's the addon developers who only test their products in vanilla FS installations instead of trying to work together.

Hi Martell, I use FSUIPC offset 024C, it gives you the VAS remaining in your main display.

Cheers, Ed

Ed,

 

Ok, thanks for the information.

Ed,

 

Ok, thanks for the information.

 

Welcome, Martell. If you eventually need more details on how to setup FSUIPC to display the VAS, just send me a PM with your email.

Cheers, Ed

Welcome, Martell. If you eventually need more details on how to setup FSUIPC to display the VAS, just send me a PM with your email.

Cheers, Ed

Ed,

Thanks for the follow up.

I have used it but not always displayed in the sim.

 

I have two PCs but cannot afford to purchase the P3D additional license for second PC .. plus future P3D upgrade costs and other software that would require an additional license to basically duplicate the Sim setup on the second PC.

Maybe Rob can chime in Ed  :wink:

 

Hi Rich, yes, hopefully he'll do!.

Thanks, Ed

Hi Folks,

For those interested, during the upgrade to P3Dv3.4.14.18870, I've discovered that on my gaming laptop the parameter OPTIMIZE_PARTS was still set to 1 (default), while on my desktop this same parameter was set to 0 (zero). This explains the difference in VAS consumption between the two machines. With the OPTIMIZE_PARTS=0 in P3Dv3.4, as explained by Rob Ainscough on a previous post here at Avsim (back on October), you can lower your VAS consumption by approx. 250 - 350 MB.

The parameter OPTIMIZE_PARTS is set under the [sIM] section of your Prepar3D.CFG file, and for P3Dv3.4 Rob recommended to be set to 0 (zero), while for previous versions of P3D (v3.3 and lower), this parameter should be set to default (=1).

Case closed for me!.

Cheers, Ed

Glad you got it sorted.

 

 

Vic