I did a comparison of P3D 3.3 and the latest P3D 3.4 hotfix 2.  I wanted to really challenge the VAS so I flew from Heathrow to Frankfurt.  Here are the details:

• Flight was from Heathrow (UK2000 EGLL) to Frankfurt (Aerosoft EDDF).
• Aerosoft A320
• AS2016+ASCA+ENTEX
• OpenLC Europe

Took some doing to get set up:

• Uninstalled 3.3 Client and installed 3.4
• Updated FSUIPC to the latest
• Updated AS2016+ASCA to the latest
• Updated Orbx Object library
• Updated EZDoc
• Updated PTA from 1.x to 2.0 (I haven't adjusted the 2.0 shaders yet...not sure if this would change the results.)

I flew the same exact flight, same exact parking spots.  Apart from the updates above, everything else was the same.

 

The result:

• VAS at end of 3.3 flight: 3.690 GB
• VAS at end of 3.4 hotfix 2 flight:  3.444 GB
• Performance was very good throughout the flight...better framerates in 3.4.

 

So, VAS usage was actually less with 3.4 Hotfix 2 than it was with 3.3.  Your mileage may vary, of course, but that's what I got.

 

I had to reinstall OpenLC because the depiction of the scenery was totally different.

 

 

I had to reinstall OpenLC because the depiction of the scenery was totally different.

 

I hadn't noticed anything.  What differences did you see?

I hadn't noticed anything.  What differences did you see?

 

Actually the one in US, I've checked an area I knew before and it was different from what I remembered, then reinstalled, and voila, it came back to "normal". I'm afraid other products might be affected as well, such as HD Trees and even the regions. As for the Vector, I just "reapplied" (using the configurator) and I hope it suffices. :-)

One more good thing I saw yesterday.  I took a flight from FSDreamTeam KJFK with Drz New York City enabled in the PMDG 777.  My VAS went way up to 3810 (something I do NOT recommend as P3D mucks things up when it's that high.)  About 70 miles away from the airport, my VAS had dropped 450 MB to 3350 or thereabouts.  So it did free up quite a lot.   

One of theses days I took off from CYVR FSDT (a scenery/area that is known for its high VAS usage) and wasn't able to get to KMRY. When I was nearing the TOD (SFO surroundings) there was the OOM. I didn't "ding" anywhere prior to that, though.

 

 

One of theses days I took off from CYVR FSDT (a scenery/area that is known for its high VAS usage) and wasn't able to get to KMRY. When I was nearing the TOD (SFO surroundings) there was the OOM. I didn't "ding" anywhere prior to that, though.

 

With Orbx Norcal, the SFO area is pretty tough and can cause an OOM all by itself.  I love the regions but they can have a heavy cost both in framerates and VAS.