Yes, very strange. I've had other simmers check - for instance, in situations where they consume around 2800 MB virtual memory (sitting at the gate, NGX, Fly Tampa Copenhagen), I usually consume 500 MBs more with the exact same settings.

 

As note, the handling of virtual memory was for me FAR better in P3D v3.0. Somehow it got worse in v3.2. 

 

Just realized, that my settings in FlyTampa-Configurator are quite sparse... ONLY Neglible and Low are checked... ALL Moderate and above are not checked... could that explain something?

 

Don't know how you set it up

Just realized, that my settings in FlyTampa-Configurator are quite sparse... ONLY Neglible and Low are checked... ALL Moderate and above are not checked... could that explain something?

 

Don't know how you set it up

 

 

In fact, it could. Will try to do a quick flight tonight with these settings! Thanks for checking btw :wink:

I flew the PMDG 777 from FlyTampa's Toronto (moderate settings) to FSDT's JFK over the weekend. I also use FTX Global and Vector.  While taxiing out at Toronto, I got the VAS alarm pings, until about 5000' after t/o, at which point they stopped. Managed to land at JFK without any further VAS stresses.   

 

I've not yet had a VAS crash with 3.2.

 

.

 

 

While taxiing out at Toronto, I got the VAS alarm pings, until about 5000' after t/o, at which point they stopped. Managed to land at JFK without any further VAS stresses.

 

While taxiing out?  Have you turned off anything in Vector?  I know it's bad around Toronto even without FlyTampa.  My thought is to, maybe, turn Vector off if I'm flying into/out of there but, so far, I avoid it like Los Angeles. 

While taxiing out? Have you turned off anything in Vector? I know it's bad around Toronto even without FlyTampa. My thought is to, maybe, turn Vector off if I'm flying into/out of there but, so far, I avoid it like Los Angeles.

Yes, in Saturday's case I was taxiing out when the pinging first started. I have everything unchecked in Vector except main roads, water features, golf courses. (Bridges, tunnels, railways are turned off) - and of course P3DV3.2 is a massive help with VAS management too. I couldn't get away with anything using 3.1

My experieince, just "bumbling" about in the A2A T-6 Texan (awesome aircraft by the way) in the Orbx North America (NA) Pacific North West (PNW) scenery with their Friday Harbour and a few other local small airfields within a 45 minute radius of Friday Harbour installed, it is hugely demanding on the system.

 

VAS in P3Dv3.2 is quickly down to 400MB-500MB or so after just 60 minutes. Fantastic scenery but I don't think the PC would tolerate the NGX flying around there for long. The sim seems to fight for VAS space once it gets to these low levels as it is up and down around there for a while but it will eventually lose the fight and the warning ding dong will sound and or graphics anomaly's start to show like black textures.

 

Yet I can manage a 5 hour flight in NGX between two complex airports elsewhere in the world on the same settings, with some bad ASN weather, GSX, Vector, Global and custom mesh.

 

In my opinion, if you don't have VAS issues, it is not because you have a fantastic system, it is because your settings/add-on's are well tuned to the sim / scenario you are flying. With some of the add-on's mentioned here, there is no system that will survive on max settings for long. We wait on 64bit for that.

Just realized, that my settings in FlyTampa-Configurator are quite sparse... ONLY Neglible and Low are checked... ALL Moderate and above are not checked... could that explain something?

 

Don't know how you set it up

 

 

Well, it seems as I save around 250-300 MB of virtual memory by checking only neglible settings within the configurator. My settings were relatively cranked up from before. To bad we can't enjoy those new features like people on apron moving around etc because of an horrendous 32-bit limitation.