Sign in to follow this  
Nyxx

VAS what VAS? in 3.4!

Recommended Posts

After a year out, I did a freash install of everything. So after reading all the doom and gloom over 3.4 I will I liitle bothered how it would go.

 

Well

PMDG NG

AS Dubin

FT EHAM

AS16- AS Cloud art with REX Clouds=soft clouds

New caseplane(1.5) (love it)

FTX Global and vector.

 

EIDW to EHAM, landed and at gate 1.1GB VAS left

Return flight 1.3GB left.

 

So I must be lucky! or doing completely fresh install did the job?

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

You need to mention what options in Vector you have activated. There is 600Mb VAS difference between 100% OFF and 100% ON :-) 

  • Upvote 1

Share this post


Link to post

As Rob's guild as he use's same as i did.

 

It was 400 is it now 600?

 

BTW i had no AI at all but i will now change that with all that VAS free.

Share this post


Link to post

could you tell what a/c you used , please? I'm still on 3.2 and i'm really afraid of 3.4 :) :) I understand that we won't have a choice after FSL A320 is released so i'm really trying to research this 3.4 as much as possible before updating :)

Share this post


Link to post

Hi David, I was just at EHAM too and saw no VAS problems. Even so some scenery may cause issues since there's some changes under the hood that may not suit them. In order to progress with P3D there's going to be some upset.

Share this post


Link to post

I've just recently built a new 7700k system

 

I used Rob's "medium high end" settings is his Prepar3D guide.

http://www.avsim.com/topic/494633-prepar3d-guide/

 

I'm using Pilots Global Ultimate, Orbx Global, Vector, LC, PNW and the rest of the west coast.

 

Everything is looking and running awesomely. 

 

What I'm experiencing and I haven't had a chance to experiment yet is that at low altitude flights, things are just fine. But at high altitude flights I'm running into VAS issues within about 20 minutes of flight.

Share this post


Link to post

could you tell what a/c you used , please? I'm still on 3.2 and i'm really afraid of 3.4 :) :) I understand that we won't have a choice after FSL A320 is released so i'm really trying to research this 3.4 as much as possible before updating :)

PMDG NG 

 

Hi David, I was just at EHAM too and saw no VAS problems. Even so some scenery may cause issues since there's some changes under the hood that may not suit them. In order to progress with P3D there's going to be some upset.

Hi Steve good to see your still around :) the only "tweak" I am using is you 116AM ;) I was amazed at the amount of VAS left after reading these forums and 3.4. EHAM is very sweet.

Share this post


Link to post

PMDG NG 

 

Hi Steve good to see your still around :) the only "tweak" I am using is you 116AM ;) I was amazed at the amount of VAS left after reading these forums and 3.4. EHAM is very sweet.

 

I thought I read here somewhere that LM is recommending users to not put in the AM tweak as their code is better optimized without it to use all cores.

Share this post


Link to post

understand that we won't have a choice after FSL A320 is released so i'm really trying to research this 3.4 as much as possible before updating :)

You will be happy to know, the bus will work in 3.35. This is from the horses mouth. Not sure about 3.2 though. You can always update to 3.35, now that LM make the client installers (previous available ).

Share this post


Link to post

You will be happy to know, the bus will work in 3.35. This is from the horses mouth. Not sure about 3.2 though. You can always update to 3.35, now that LM make the client installers (previous available ).

That's really soothing :) Thank you for the info. I wonder for how much longer i'll be able to dodge 3.4 :)

Share this post


Link to post

That's really soothing :) Thank you for the info. I wonder for how much longer i'll be able to dodge 3.4 :)

Yes, that is the 60 million dollar question :)

Share this post


Link to post

I am at 300 MB VAS left sitting at the gate at FlyTampa EHAM in the NGX, with FS2crew, AS2016, FTX Global and OpenLC activated.

 

I have absolutely no idea what to do at this point. Tweaking seems pointless. Version 3.0 was definitely best for my part providing me an extra 250-300 MB to work with. Was also under the impression that version 3.4 struggled with VAS issues. 

Share this post


Link to post

I am at 300 MB VAS left sitting at the gate at FlyTampa EHAM in the NGX, with FS2crew, AS2016, FTX Global and OpenLC activated.

 

I have absolutely no idea what to do at this point. Tweaking seems pointless. Version 3.0 was definitely best for my part providing me an extra 250-300 MB to work with. Was also under the impression that version 3.4 struggled with VAS issues. 

is this on departure ? what gate ?

 

I have 3.4 Client installed and HD2048 enabled in 4K and with Dense autogen but complexity maxed out and LOD at 4.5 i have 1.1GB free VAS in the NGX with same add-ons as you. 

 

using Vector on low setting would bring it down to 850MB left and using GSX,FS2CREW down to 650-700MB left (therefor i disable Vector at EHAM - Room for weather /clouds instead)

 

Something must be wrong

 

Update:

 

Anyone using FTX Global 2010 edition ?  -Some places like at EGLL i saved 300 MB VAS disabling it .

 

I have not tested around EHAM

 

 

Michael Moe

Share this post


Link to post

My experience with 3.4, just to mention one instance.....

Aerosoft EGLL Stand 518...PMDG T7......Flightbeam KIAD.....FTX Global....FTX Vector (all options enabled except Tertiary road and Traffic).....FS Global 2010.....FTX EU and NA LC......AS2016 + ASCA clouds ....max texture resolution in .cfg = 2048...ASCA clouds res 1024, DXT5.......PMDG T7 external model disabled......monitor resolution 3440x1440

P3D LOD radius 5.5.....scenery complexity Extremely dense, Autogen Normal....no AI traffic (airplanes/cars...etc....).....online traffic only (VATSIM)...

Flight duration 8.5 hrs.....residual VAS on flight loading 1400Mb......residual VAS at the end of the flight 850 Mb.

For me P3D 3.4 is OK....stunning visuals (enhanced by PTA) ....great FPS...smooth as silk....no VAS issue...and it is not a one off case....this is consistent on all flights.

There must be some game changer, settings or addon, or a combination of both that becomes a game changer for some people...

 

Ezio

Share this post


Link to post

 

 


I am at 300 MB VAS left sitting at the gate at FlyTampa EHAM in the NGX, with FS2crew, AS2016, FTX Global and OpenLC activated.

I have absolutely no idea what to do at this point. Tweaking seems pointless. Version 3.0 was definitely best for my part providing me an extra 250-300 MB to work with. Was also under the impression that version 3.4 struggled with VAS issues.

 

Which version of P3D?  What is your AI traffic set to?  Do you have FTX Vector turned on?  Do you have FS2Crew RAAS on?  What resolution of clouds are you using?  What are your texture settings set to (first page of your Options in P3D)? 

Share this post


Link to post

I have shuttled between UK2000 EGLL and FT EHAM in the PMDG737 and 777 with a fair amount of weather and VATSIM traffic with no VAS issues. P3D3.4 is pretty stable for me.

 

Using FTX Global and Vector(many of the road/rail options turned off)

Share this post


Link to post

I thought I read here somewhere that LM is recommending users to not put in the AM tweak as their code is better optimized without it to use all cores.

Except if you have HT enabled. If you actually read the documentation yourself you will see information whereby it shows how when the sim has four logical processors the rendering stage is at it's leanest because the simulator splits its processes out across four parts.

 

If you have more than four LPs the background parts divide to utilise more data loading, if you have less than four those parts combine onto less cores.

 

So with four cores leave it with no AM.

 

With four cores +HT you have 8 LPs and so the rendering stage, although leanest appears on a core with a sister LP with another part of the sim and so reduces back the rendering similarly as it would with HT disabled on three cores.

 

The reason 116 is good on the four core +HT is that 116=01,11,01,00 (8 LPs) from the right we have two zeros representing LPs 0 and 1, these are unused by the sim and so completely available to the weather engine, next left we have 01 which shows that only one LP is used by the sim (ones represent on LPs) that's the main rendering part on a core to itself, next left we have two ones ,11, which shows both LPs of that core being utilised by the sim, finally next left we have 01 which means that final part of the sim has a core to itself, no more sim processes on that core.

 

So as you can see with only three cores available with the magic of HT we can split the sim across four parts.

 

What of LPs 4 and 5? The two ones on the same core 2 (core zero on the right followed by 1,2,3). Well if you watch the graphs in Task Manager you can see that these don't require maximum throughput of their LP at the same time.

 

It's one of those hard to understand things about Windows, takes a lot of thought and careful reading of my posts.

Share this post


Link to post

There always seems to be a steady stream of posts about VAS issues in P3D, irrespective of the version or hotfix, but I think that's largely because those with issues post.  

 

I have no issues.  I automatically dump the VAS figure to a csv file every minute, so I can check afterwards, but it's been months since that go below 1GB remaining, and I now also often see these nice curves back up after I leave a memory intensive area.  So count me as one more otherwise quiet voice saying I reckon it's pretty good now.

 

B.

  • Upvote 2

Share this post


Link to post

 

...Now let's look at the situation on the four core +HT with no AM = 11,11,11,11 and so the first four parts exist on only two cores (remember this is P3D not FSX) core 0 has parts one and two the rendering process on LP0 is interrupted by the second job of the sim on LP1. Next core 1 we have two background data loading processes, next two cores we have those data loading processes split over six LPs. This increases scenario loading speed decreasing the time to get to the cockpit, but the rendering stage is baulked slightly by the activity on the sister LP of core 0.

Share this post


Link to post

I had some VAS problems, but that was because I'm running Flyinside/VR. Now that I´ve optimized my settings, I usually with 500-800mb left after a long haul flight using the PMDG 777 and FSDT/FlyTampa airports. I am also using ORBX Global and AS2016+ASCA. If you are having issues, lower your settings and disable VAS hungry addons such as VECTOR, OpenLC, RAAS, AI Traffic etc. No other way.

Share this post


Link to post

 

Using more than four LPs increases VAS use slightly but not significantly enough to be a major factor in VAS issues.

Share this post


Link to post

There is one simple answer to VAS pain that has been beaten to death - switch to UTX instead of FTX stuff and you have both LC, Vector and zero VAS issues. You can enable MOST of the roads (in USA I'm able to fly with ALL roads set to ON), ALL railroads and you;ll have beautiful night lighting FTX has never had. One more thing - i'm using 100% custom made AI Traffic at EDDF/EHAM/EGLL/KJFK/KLAS without issues.

 

There is only one detriment for UTX as it's limited to USA, Canada and Europe.  

Share this post


Link to post

 

 


There is one simple answer to VAS pain that has been beaten to death - switch to UTX instead of FTX stuff and you have both LC, Vector and zero VAS issues. You can enable MOST of the roads (in USA I'm able to fly with ALL roads set to ON), ALL railroads and you;ll have beautiful night lighting FTX has never had. One more thing - i'm using 100% custom made AI Traffic at EDDF/EHAM/EGLL/KJFK/KLAS without issues.

There is only one detriment for UTX as it's limited to USA, Canada and Europe.

 

There's probably some truth there.  I remember rebuilding my P3d and, before I installed anything, my framerates were in the 100s...way, way up there.  Adding more stuff and then more stuff on the stuff brought it down, down, down.  After that, you have to start fighting back...less of this, less of that...until it gets where you want.  I suspect UTX might be a much less VAS/frame intensive solution for folks.  Doesn't mean I'm going to switch...I've got it working with Global okay...but I suspect you're right.

Share this post


Link to post

One thing where FTX beats UTX easilty - HD Trees and forests LC. Meanwhile, as far urban LC concerns, UTX is the champion. Also, to my biggest regret I cannot mix beautiful FTX regions outside of UTX coverage with UTX/GEP3D, as FTX badly messes with default P3D LC files and autogen definitions. In other words, either you belong to FTX sectarian organization completely or you're completely out :-)

Share this post


Link to post

What I really want to try is the sandwich of FTX Global, UTX without LC and FTX Open LC Europe/USA. 

Share this post


Link to post

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