What does this "ENABLE_MEMORY_OPTIMIZATION=1" Do?

 

I just added it... its not worse than without it...so no foul so far...but I am curious about what that does too...

Are these "tweaks" needed anymore with the latest P3D v3.3.5? I see on the page it says P3D v3.1

Totally agree with the bulk of your argument Bob - but have to disagree with the 'MaxRegionsPurgePerFrame=32' recommendation? I tried that on my 'relatively clean' 4790k/980ti setup and it introduced serious,verifiable, stutters?  Dropped it back to the default 16 and the stutters vanished.   I know!! - and before others jump in .... this isn't a poll - simply my experience, on my rig, with said 'tweak'. YMMV.

 

My understanding is that the setting needs some additional CPU headroom to work properly...it allows P3D to free up memory more aggressively, but needs some extra CPU power to make it happen smoothly.

 

 

I also think that Pro-ATC is eating up my VAS as well.

 

Probably not...Pro-ATC/X runs as a separate process (i.e. in its own VAS space) and communicates with P3D using Simconnect.

 

Regards

This VAS and OOM thingi is very intriguing!

 

My old PC: i7-3770K OC 4.5Ghz with GTX670 Video card 

 

My new Build i7-6700K OC 4.5Ghz with GTX1070 Video card

 

Both with identical P3D settings. in Fly Tampa OMDB and Chrs's Night Environment and PMDG 777

 

old PC VAS is 700K Free (reasonable space to do a flight somewhere) 

 

New Set up VAS is 350K Free (not enough to do a flight anywhere )

 

I am running into OOM issues in my new setup that I did not in my old PC.  I seem to have lost about 350K VAS somewhere... and I am trying to get them back.

 

I was not expecting to get additional  VAS with the new upgrade...but I did not count on losing some either.

I have a 6700K OC 4.7GHz with GTX980Ti running at 2560x1440 resolution. I typically have 800MB free (3.2 GB is indicated by Process Explorer) when I load a scenario at a quality airport.

 

What are you using to measure VAS?

 

 

What are you using to measure VAS?

 

FSUIPC. I have the setting that displays the VAS on the window of P3D

The reason I provided my system specs is to let you know that it's not the system update to blame.  I've used FSUIPC a long time for same purpose, but since P3Dv3.2 I've had few problems with VAS including with the 777.  I have most of the Orbx stuff as well, and with careful use of the settings for Vector the VAS stays under control.  A 350MB (I don't think you meant 350KB) change with same add-ons is hard to understand.  Are you sure you don't have some photo bgls turned on that used to be turned off?

I'm also using FSUIPC method to measure VAS in P3D. After everything loaded, and the 777 is sitting at the gate I only have around 600-700MB VAS left... By the time I'm reaching my destination it drops down to 250, at this point I'll start hearing the DING warning sound, and if I'm lucky I'll be able to land, but that's extremely rare as I always OOM at around 110MB and less. I'm sure P3D can use some better optimization methods. Because I think the previous versions wasn't this bad.

 

If it's not Pro-ATC then it has to be  either FS2Crew PMDG 777 or RAAS. I thought it was MyTraffic 6, but I am using the P3D Traffic Optimizer and it still has no effect in helping my VAS.

If it was FS2Crew, we would all be having OOM's. You can rule that out.

How can I disable the chime?

In FSUIPC.ini Chris. OOM Check=0

Sorry, should be OOMcheck=NO

15 hours ago, Travelling_Wilbury said:

Sorry, should be OOMcheck=NO

That disables VAS checking and logging completely.  OOMCheck=Quiet will disable the beep without losing VAS monitoring.

Regards

On 21/03/2017 at 1:22 AM, w6kd said:

That disables VAS checking and logging completely.  OOMCheck=Quiet will disable the beep without losing VAS monitoring.

Regards

Cheers Bob, learn something everyday :).