2) VAS VAS VAS VAS VAS:
Our testing internally leads us to conclude that Lockheed Martin's development team has succesfully updated Prepar3D so that it will unload data that is no longer needed in memory. More specifically, our testing seems to conclude that data accumulation in VAS related to scenery being seen or over-flown is no longer a factor for simmers using Prepar3D.
I want to stress that our testing was done in-house, and was not scientific- but we know very well how to replicate OOM issues with Prepar3D and FSX, and running those same tests with Prepar3D v3 yielded far lower VAS volumes than we have ever seen, even when moving between very intense scenery areas.
This being the case- we are extremely excited to see how your results bear this conclusion out. (I look forward to hearing from you with trepedation- as this is truly enormous news for all of us if indeed wide use bears this out!)
Many folks have been clamoring for an x64 version of Prepar3D- and v3.x is not a 64-bit version. In my opinion, fixing VAS consumption is am much more important milestone in the short term because the massive increase in memory consumption caused when scenery developers begin stuffing greater and greater detail into the sim has lead to a proliferation of OOM issues during the past two years.
It is my sincere hope that this fix gives us all a reprieve from the OOM problem- and I also sincerely hope that all of our scenery designers will continue to use restraint on the amount of detail added to scenery so that we don't being to see OOM issues because the machine itself runs out of VAS because of growth in scenery detail. (That danger is still out there- but for now we have been given some breathing room.)