davecessna

What I meant to say is it's not getting released anymore in P3D.

I *think* I am also seeing this issue. VAS slowly decreasing over the course of a flight.

Buyer beware of those products. You'd be better served following one of the plethora of free guides on this or many other websites.

AFAIK there is no "grace" period. I'm sure VATSIM controllers understand, but in real life I believe the PNF does the comms work while the PF does the criticial flight stage. Somebody correct me if I'm wrong.

I might be seeing another issue, but I've noticed that there *may* be memory leaks introduced. I did a SFO-EWR flight today and noticed my VAS with the 737NGX and usual settings went down to 340mb free at EWR, which is lower than the 700 I usually see in the NYC area. A fresh start in EWR is fine however.

I am also getting g2d.dll errors midflight. I highly doubt it's hardware issue because my temperatures and voltages are very stable, and all other games work fine. I've noticed if I'm a bit too cavalier changing EZDOK views, I can crash the sim running PMDG 737 NGX with the above mentioned error. Anywho, I hope somebody finds the fix.

It's a very smart move by DTG. What should be more exciting is now you have tangible proof that they are aware of and willing to collaborate with the major players in our hobby.

They should at least be giving an indication that there are delays or something...

There has been a banner for a couple of days saying the always appreciated "Fix Coming Soon" but that's about it.

What's the news? I get the feeling like the minor hotfix is turning into a real production.

Thank you for pointing this out. Guys, he's absolutely right, there is something in Vector that can potentially make VAS usage run away. I was getting OOMs flying the 777/Aerosoft A320 out of stock airports unless I disabled all options in Vector Configurator except for "Highways" (no suboptions, just the primary tick box). David Ayoub