Just installed latest Taxi2Gate KSEA from my simmarket account.

 

Test #1 KSEA default with PMDG - VAS 3.52GB - VRAM 2.8GB

 

 

Test #2 KSEA Taxi2Gate with PMDG - VAS 3.40GB - VRAM 3.2GB 

 

 

As you can see Taxi2Gate KSEA actually used less VAS than default KSEA, but more VRAM which is consistent with my other tests.  Graphics settings used are at the end of the Taxi2Gate KSEA video.

 

Add-ons are the same as other tests, FTX Global, OpenLC, Vector, PILOT's mesh, MT6.  But just to be clear, I'm NOT saying one can't OOM P3D v3.x, it can be done, toss in a few more add-ons, load a Region, etc. ... starting at 3.4GB isn't going to leave much room for the actual flight.  KSEA is a VAS hot spot with or without add-ons.

 

Cheers, Rob.

I never used to have problems in earlier versions of P3DV3 of KSEA with Taxi2gate with FTX PNW and the NGX. LOD 4.5 Autogens Normal and complecity maxed out

 

VAS around 3.1-3.3GB.

 

No problems landing at FSDT CYVR as well

 

Will make a test later with 3.4

 

Michael Moe

 

 

 

 

Michael Moe

What worries me most is that the latest version seems not to free up memory of the VAS as efficiently as in previous versions. If you fly in "heavy" areas, the sim consumes VAS but it does not get unloaded if you depart several 100nm away. It appears that memory management in this aspect was more efficient in the previous versions, especially in v3.0.

If this is true then how come in my own independent test, spawning in a Taxi2Gate's KSEA, Gate B15, AS16 set in Historical Mode with a PMDG 737NGX did I see a HUUUUGE VAS loss?     Test 1; 4096 texture res. with ASCA clouds set to 4k Textures both both cloud types, No AI.   INSTANT OOM.      Test 2;  4096 texture res, ASCA Clouds set to 1k, NO AI.  400megs VAS remaining on spawn in.    Test 3;  1k Texture Res, 1k ASCA clouds, No AI, 950 megs VAS remaining upon spawn in?   

 

This is on a GTX 980.   

 

Looking at the VAS load using different sizes of the textures the way I understood it it doesn't really matter what size you're using unless you also have the max texture size set to match that in Prepar3D.cfg but someone correct me if I'm wrong.

 

So let's say you're using 4096 textures but your setting in Prepar3D.cfg is set to 1024. Then I guess you won't see much of a difference if any regardless what textures you're using.

 

If you on the other hand do have the setting in Prepar3D.cfg match your installed textures then I guess you will see a huge difference where I guess 4096 textures will put 4 times the load vs using 1024 textures.

 

Lots of guessing here as you might have noticed, just thinking out loud after reading about both your's and Rob's tests :smile:

My VAS experiences continue to be satisfactory.

 

I loaded up the 777 at Flytampa's Toronto on Saturday and flew to Heathrow.  High VAS readings at Toronto as you would expect -  but no OOM.  VAS between 89-93% at Toronto.  Dropped back to about 75-80% over the ocean. I disconnected from VATSIM halfway across, rebooted the PC and reloaded the saved situation and reconnected to VATSIM (I always do this on long flights) - managed to get into UK2000 Heathrow without an issue.

 

Also used:

 

FTX Vector

FTX Global 

FTX LC NA

AS16

 

In sim settings were sensible:

 

Autogen about halfway for everything, 

Scenery complexity halfway, 

Texture Res= 1024

My VAS experiences continue to be satisfactory.

I disconnected from VATSIM halfway across, rebooted the PC and reloaded the saved situation and reconnected to VATSIM (I always do this on long flights) - managed to get into UK2000 Heathrow without an issue.

 

But rebooting mid-flight is not a practical solution to release the content of the VAS and thus is NOT satisfactory. Of course if you reboot, you get fresh VAS but try the same flight and see whether you can sucessfully land in EGLL without a restart of the PC.

Sure, if you have the chance to reboot your PC mid-flight I think most of us would be able to complete our flights without any VAS issues.

 

Especially since the VAS issue seems to mainly be about VAS not beeing released after leaving your origin airport.

Cargostorm, on 19 Oct 2016 - 09:59 AM, said:

But rebooting mid-flight is not a practical solution to release the content of the VAS and thus is NOT satisfactory. Of course if you reboot, you get fresh VAS but try the same flight and see whether you can sucessfully land in EGLL without a restart of the PC.

 

I agree it is not satisfactory nor realistic. However, I don't really mind that so much.

 

I'm out in the middle of nowhere in cruise with no ATC and I have discretion as to when I disconnect and reboot. I managed to fly out of a VAS heavy area without OOMing for about three hours and I managed to fly into a VAS heavy area without OOMing (for about three hours). (In many previous versions of P3D, this wasn't possible for me). I consider it a fair compromise until 64 bit

 

Apart from this flight, I have also flown to and from large European (addon) airports with the 737 without OOMing - with no reboots - similar settings, same global addons.

 

 

Especially since the VAS issue seems to mainly be about VAS not being released after leaving your origin airport.

 

But as mentioned, the VAS indicator dropped from 90% to 75%.  

 

 

But as mentioned, the VAS indicator dropped from 90% to 75%.

 

Sorry, missed that.

 

Sure is very interesting how some have huge issues where others have not using what seems to be very similar setups but happy to hear things are working fine for you :smile:

 

 

ure is very interesting how some have huge issues where others have not using what seems to be very similar setups but happy to hear things are working fine for you

 

I will try a full unbroken flight this weekend.  

So the message is don't move to 3.4 right now.

mmmmmmmmmm the only way for you to know is to try it, test it, love it and to live with it

.....or stick with the version you have now because it works just fine.

Posted this over in LM forums minutes ago and looking forward to their comments if any...

 

http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=122226

 

I have seen that your post has been removed over at the LM forum. Do you know the reason?

On what version are you currently? I am considering to go back to 3.2, which was best in regard of VAS management.

Here is a quick IN THE RAW departure out of Taxi2Gate KSEA with AS16 this time ... VAS was around 3.4GB.  ATC had aircraft taking off from both directions on the same runway and I guess I encountered AS16 wake turbulence on takeoff (that was weird)?

 

Graphics settings included in video as well as showing VAS usage and VRAM usage.

 

 

Cheers, Rob.

My VAS experiences continue to be satisfactory.

 

I loaded up the 777 at Flytampa's Toronto on Saturday and flew to Heathrow.  High VAS readings at Toronto as you would expect -  but no OOM.  VAS between 89-93% at Toronto.  Dropped back to about 75-80% over the ocean. I disconnected from VATSIM halfway across, rebooted the PC and reloaded the saved situation and reconnected to VATSIM (I always do this on long flights) - managed to get into UK2000 Heathrow without an issue.

 

Also used:

 

FTX Vector

FTX Global 

FTX LC NA

AS16

 

In sim settings were sensible:

 

Autogen about halfway for everything, 

Scenery complexity halfway, 

Texture Res= 1024

 

I did the same thing the other way round last week end...EGLL (Aerosoft) to CYYZ (Fy Tampa)...........I am running an [email protected] + GTX970 + Win10 latest build....P3D V3.4

 

FTX Global

FTX Vector

FTX OLC EU

FTX OLC US

REX TD textures for sky and water (DXT5)

AS16+ ASCA with Clouds @ 1024 (DXT5)

P3D Textures @ 2048

Tessellation Ultra

Scenery complexity and autogen dense

LOD 5.5

Mesh and textures resolution at the highest setting

Water detail high and shadow detail high 

 

PMDG T7 (with external model disabled)

 

All sceneries disabled except departure and arrival airports (using Scenery Configurator Editor)

 

7:30 hrs flight duration..no interruptions/reloads....on Vatsim all the time....started sitting at Stand 518 in EGLL with 1340 Mb VAS remaining.....dropped to 1100 during taxi and take off from Rwy 27L.......increased to 1280 during the oceanic crossing....started to drop around 1000 while getting closer to NA mainland and ended up at 700 Mb left after landing in CYYZ.

 

Yesterday I flew from EGLL to UUDD...same a/c ....same settings...same VAS consumption until after take off but then dropped rather unexpectedly half way to Moscow during cruise to 850 Mb VAS left.....and equally unexpectedly remained stable getting closer to UUDD (MDesign) which is usually a big VAS eater ...ended up my flight with 850 Mb left

 

In conclusion...I am not having VAS/OOM issues but sometimes VAS management seems to be a little bit weird... 

 

Regards