3. What I have noticed for the first time, that FS2Crew on both NGX/T7 swallows between 250-400 Mb depending on its stage (idle or active) and bleeding VAS like a hell during the flight (all these times I blamed P3D native VAS poor management for that). Yesterday I did FT EHAM - FT EKCH flight with NGX and FS2Crew OFF I had truly stable 900-1000 VAS leftover during the entire flight. Plus - EHAM's weather yesterday was total hell, AS2016 was quite busy on the background. Therefore, for the first time since 2006 (when the first FS2Crew was released for LDS767) I have to put it away to my biggest regret in order to give more room for nicer visuals.

...and I forgot to add - I use 100% custom made AI Traffic with TFS/FSP/FAIB/AIG/CDAI models and textures from AIG fan groups. EHAM is typically packed with ~150 AI planes. Nicer 35FPS from NGX/T7 anyway :-)

 

 

I dont see anymore than 90-115MB VAS difference for FS2CREW in the NGX.

 

Are you sure its not your 100% AI that leak VAS sometimes ?

 

Thanks

 

Michael Moe

In my case biggest VAS leaker proved to be FTX Vector. Leaving only highways, main roads and beaches on for IFR jet flights allows me to save few hundred megs of VAS.

 

Second one was LOD radius (always keeping it on high for jets) and third one autogen (never go over dense).

 

I can set 25% with MT 6.0 which gives me sh(*&*oad of traffic and I'm fine VAS-wise. So to me, the holy VAS killing trinity is:

 

1. FTX Vector

2. LOD Radius

3. Autogen

 

For A2A flights I max almost everything out but that's a different story (shorter flight distance, less complex aircraft vas-wise) 

In my case biggest VAS leaker proved to be FTX Vector. Leaving only highways, main roads and beaches on for IFR jet flights allows me to save few hundred megs of VAS.

 

Second one was LOD radius (always keeping it on high for jets) and third one autogen (never go over dense).

 

I can set 25% with MT 6.0 which gives me sh(*&*oad of traffic and I'm fine VAS-wise. So to me, the holy VAS killing trinity is:

 

1. FTX Vector

2. LOD Radius

3. Autogen

 

For A2A flights I max almost everything out but that's a different story (shorter flight distance, less complex aircraft vas-wise) 

+1

 

Next would be some shadows options

 

Michael Moe

I dont see anymore than 90-115MB VAS difference for FS2CREW in the NGX.

 

Are you sure its not your 100% AI that leak VAS sometimes ?

 

Thanks

 

Michael Moe

Nope, I carefully manage all of my AI textures.

 

As I mentioned above, yesterday's flight without FS2crew was like living in another universe (in terms of VAS usage). Also, it very easy to test FS2Crew ON and OFF on idle (meaning first 45 seconds on initial load). Even in the idle mode it eats 200 Mb immediately. I agree however that it's my mileage as I have separate Logitech sound card that perhaps contribute into overall VAS usage

 

LOD - 3.5 always despite blurry textures on a horizon.

 

 

 

 

 

Next would be some shadows options

 

What about shadows? Yes, they eat up FPS, but not VAS as far as I know.

Shadows themselves should not impact VAS. Also, if you change cloud shadow texture size from 512 to 256 MB you get instant 30% fps boost (sometimes more, mileage may vary). I currently use vegetation shadows as they really add to immersion.

Also,

As dedicated AI fan for many years since FS2002 times, I can tell that AI traffic in P3D consumes resources and behaves overall slightly different than it did in the past with FS2004/FSX. Yes, it still eats FPS, meanwhile proper models and textures' management bring a lot of efficiency in this area. However, in terms of VAS usage it's totally different picture - I have all the "heavy-metal" add-one airports that exist in P3D environment so far and I barely see VAS difference with AI Traffic set to 0% and 100%. Something has been changed internally in P3D for sure.

 

As I said, at FT EHAM with the settings per above post I have stable 28-35FPS (depending on angle of view) from NGX VC and between 1.1 - 1.2 stable VAS leftover. With FS2Crew Option I start with 900Mb letfover and after 30 minutes of pre-flights procedure I have 650-700Mb left meaning there is no chance I finish my flight ;-)

 

 

I dont see anymore than 90-115MB VAS difference for FS2CREW in the NGX.

 

That is also what I get on my machine. FS2Crew consumes nowhere near 200Mb on my system.

Shadows themselves should not impact VAS. Also, if you change cloud shadow texture size from 512 to 256 MB you get instant 30% fps boost (sometimes more, mileage may vary). I currently use vegetation shadows as they really add to immersion.

 

 

Interesting...how do you guys change the shadows' texture size?

In P3D.CFG

 

Find cloud_shadow_texture size line and change it. Results can be amazing especially with heavy overcast. Don't touch ground shadow texture size though, or you will get X-plane shadows in cockpit with all jaggies and stuff.

In P3D.CFG

 

Find cloud_shadow_texture size line and change it. Results can be amazing especially with heavy overcast. Don't touch ground shadow texture size though, or you will get X-plane shadows in cockpit with all jaggies and stuff.

 

 

Wow...thanks for the hint. Going to try it later tonight. 

Shadows themselves should not impact VAS. Also, if you change cloud shadow texture size from 512 to 256 MB you get instant 30% fps boost (sometimes more, mileage may vary). I currently use vegetation shadows as they really add to immersion.

They should not i guess as it should impact only GPU memory  i guess but i have seen VAS decrease with options turned off.

 

I have textures at 256 as mentioned . I think Robs guide mentioned it.?

 

But again my system and FS2CREW is only eating 90-130MB actually

 

Thanks

 

Michael Moe 

Sorry this a little off topic but steve if you could please explain.

I am using AM 116 thou i notice core 3 is really being utilized. Compared tonrest of cores are evenly spread.

Most of my addons are in 1.3.7

 

Cheers

Mike

That is also what I get on my machine. FS2Crew consumes nowhere near 200Mb on my system.

 

Same here, have been forced to stop using it between two VAS heavy airports.

Just out of interest, do you use FS2Crew alone or you have RAAS loading in background? RAAS in triple 7 or NGX if you have standalone version can eat up to 200 mb vas and that would justify why you have this issue.

 

You can either uninstall RAAS (standalone) or disable in XML file (triple 7 version)

Nope, RAAS is turned off via EXE.dll for all add-ones