Hi,

I'm a week into P3D, I've been on FSX for 2 years. I bought a beefed up machine (6700k, gtx 1080 etc) with the intention of bringing my love of FSX to P3D. After reinstalling everything from my AI traffic (WoAi), PMDG 777, to Orbx Global and Vector and about 50+ Airports, I have yet to complete a long haul, 8hr plus in my case, something I was so used to in FSX.
For those with a similar configuration and experience in P3D, what should I be doing differently?

An example of my last long-haul failure:
Imagine Sim's WSSS to FlyTampa EHAM with PMDG 777, about a 13-hour flight (A flight I somehow pulled off in FSX). I took off with 27% VAS remaining, about 3 Hours into the flight VAS had jumped to 14% remaining, 7.5 hours in over Turkmenistan at the break of dawn I get an OOM error and eventual CTD.

Any help would be really appreciated.

Best,
Leon

Hi,

I'm a week into P3D, I've been on FSX for 2 years. I bought a beefed up machine (6700k, gtx 1080 etc) with the intention of bringing my love of FSX to P3D. After reinstalling everything from my AI traffic (WoAi), PMDG 777, to Orbx Global and Vector and about 50+ Airports, I have yet to complete a long haul, 8hr plus in my case, something I was so used to in FSX.

For those with a similar configuration and experience in P3D, what should I be doing differently?

An example of my last long-haul failure:

Imagine Sim's WSSS to FlyTampa EHAM with PMDG 777, about a 13-hour flight (A flight I somehow pulled off in FSX). I took off with 27% VAS remaining, about 3 Hours into the flight VAS had jumped to 14% remaining, 7.5 hours in over Turkmenistan at the break of dawn I get an OOM error and eventual CTD.

Any help would be really appreciated.

Best,f

Leon

 

I suggest using scenery configurator and disable unnecessary scenery you are not flying to.

 

Otherwise the oom's will persist.

Thanks! I'll give the scenery configurator a try during my next attempt tomorrow.

Apart from the already suggested, selective scenery activation, a few other things that might help to prevent OOMs: 

 

* Vector can be a VAS hog, maybe try Rob's settings and see if that free's up some precious VAS: http://www.robainscough.com/P3D_Orbx_Vector_Settings.html

* Check your NVIDIA driver version, some people are suffering from VAS leaking with 378.49 and 378.66. I suggest to either use the recent .72 hotfix (https://forums.geforce.com/default/topic/994534/geforce-drivers/announcing-geforce-hotfix-driver-378-72/) or roll back to v376.33

* Turn off shader cache in NVIDIA control panel, this free'd up to 300mb for some people

 

Good luck, and dont give up, VAS hunting can be a frustrating exercise, especially for long haul flyers