That group policy edit only applies to Pro/Enterprise editions of Win 10, and the article says it stopped working after the Anniversary Edition update.  BTW, your sig says you're running Win 10 "Ultimate"...they ain't no such thang!  Pro, maybe?

 

Regards

 

Didn't realize, thanks Bob.  Ultimate was a Win7 thing wasn't it, thanks for pointing that out.

I also had huge vas problems,if I ran FSTramp I would oom out in 30 sec.Started using flightsim commander,took the NVidia control off the task bar,have orbx vector to minimums,shader cache off in NVidia control panel,after a 3 hr flight I consistently hyave 1300 mb left.

I had one yesterday, I've never seen such a huge oom drop before and it was 200nm off the coast of NE Canada.

 

I'm not convinced with the driver thing. Did the textures change yo winter time last week? Or am clutching at straws.

 

I know its a long shot but by closing down active sky next it released a big chunk of vas

Are you using the AS2016/ASN version (6255 for AS2016, I think) that released Feb 15th?  Several reports suggest that it has some major problems fixed.

 

Regards

Are you using the AS2016/ASN version (6255 for AS2016, I think) that released Feb 15th?  Several reports suggest that it has some major problems fixed.

 

Regards

What does this mean ?

Do you mean that VAS problems in AS16 are already fixed, or the newest 6255 has VAS problems?

mike

The reports say the problems have been fixed. 

 

Or to rephrase, the new beta has fixed some major problems. 

 

Or to be perhaps more clear, there were some major problems, and they have been fixed. 

 

Or to be crystal clear, the major problems that existed before have been fixed now.

 

Or...

The reports say the problems have been fixed. 

 

Or to rephrase, the new beta has fixed some major problems. 

 

Or to be perhaps more clear, there were some major problems, and they have been fixed. 

 

Or to be crystal clear, the major problems that existed before have been fixed now.

 

Or...

You are very classy and patient man.

I am glad there is not a note of sarcasm in Your reply.

Thank You for Your clarification.

There is a lot of people here for whom English is not a first language.

It really helped the way You explained it.

Happy Landings

mike

Reverting back to Nvidia driver 376.33 did not solve the leak.
I re-installed P3D and the VAS leak has gone away, I'm none the wiser as to what caused the problem, strangely the 376.33 Nvidia driver I reverted back to, has changed to version 37635? (GTX 1080).

 

Mick Partlett

Reverting back to Nvidia driver 376.33 did not solve the leak.

I re-installed P3D and the VAS leak has gone away, I'm none the wiser as to what caused the problem, strangely the 376.33 Nvidia driver I reverted back to, has changed to version 37635? (GTX 1080).

 

Mick Partlett

 

If you're using Win 10, it probably automatically updated the driver in the background.  The last one MS pushed to my machine without asking was 378.53.

 

Regards

Same here, allowed MS to update Win10 and there's the 376.53 WHQL driver again.  I wish MS would stop updating video drivers.  Display Driver Uninstall app here I come!  

Same here, allowed MS to update Win10 and there's the 376.53 WHQL driver again.  I wish MS would stop updating video drivers.  Display Driver Uninstall app here I come!  

Google says that ....

maybe that will help

HL

mike

I had major issues with Windows 10 installing drivers after every restart. Ended up disabling it in registry.

For those who like to experiment, nVidia now has another HF driver out, 378.77. I doubt any of these will actually fix the VAS leak in P3d though. I think that Bob Scott explained the situation correctly above in Post #21.

Here's what I did to reduce the chances of OOM errors with the 378.xx drivers. Personally I'm not big fan of rolling back nVidia drivers to older versions, even if one uses the DDU (Display Driver Uninstaller) in safe mode.

First, in your CMOS setup, turn off hyperthreading. As others have pointed out, this gains ~200 MB VAS. Second, beyond the usual plea to turn settings down in both the P3d UI and ORBX vector (which at least for me doesn't do a whole lot). Make sure your prepar3d.cfg file has these settings:

[GRAPHICS]
...
ENABLE_MEMORY_OPTIMIZATION=1

[SCENERY]
...
MaxRegionsPurgePerFrame=32

[TERRAIN]
...
UseGlobalTerrainView=True

People that have followed Rob A's P3d tuning guide probably already have these settings active but it doesn't hurt to check. YMMV, but this worked for me as a stopgap measure since P3d V4 is still a dream.

I still don't buy this driver issue.