In my experience, one should not expect Prepar3D to aggressively reduce the VAS consumption after leaving a complex area (maybe by 100 - 300 MB, depending on how far you are away from that area). However, compared to FSX (SE) DX9-mode, the VAS usage does not pile up incessantly at a high rate as you fly along over various sceneries over land.

Last year, I did a video where I directly compared the VAS usage in FSX-SE DX9, DX10 and Prepar3D v3.2 under identical circumstances on a test flight from KIAD to KJFK. You can take a look at it if you like:

https://www.youtube.com/watch?v=M8taw2AJl8Q

 

11 minutes ago, Afterburner said:

In my experience, one should not expect Prepar3D to aggressively reduce the VAS consumption after leaving a complex area (maybe by 100 - 300 MB, depending on how far you are away from that area). However, compared to FSX (SE) DX9-mode, the VAS usage does not pile up incessantly at a high rate as you fly along over various sceneries over land.

Last year, I did a video where I directly compared the VAS usage in FSX-SE DX9, DX10 and Prepar3D v3.2 under identical circumstances on a test flight from KIAD to KJFK. You can take a look at it if you like:

https://www.youtube.com/watch?v=M8taw2AJl8Q

 

Thanks ab. Will do later on. I've had to pause a flight from ENGM to EGLL as the footie is about to start. There was a reduction in VAS usage soon after crossing the Norwegian coast.

Perhaps it only tries to retrieve it when it gets extremely low. Time and various flights will tell.

1 hour ago, Paul_ said:

Ray .... 

 

The bottom line is ... are you suffering from OOM messages which are interfering and stopping you completing flights? 

Paul 

No, not yet. But it seems awfully close to doing that. Maybe something magical happens when VAS < 200Mb.

Hi Ray,

Speaking of excellent resources, few come better than Rob's superlative AVSIM Prepar3D Guide. Unlike many of us, Rob's approach has always been strictly methodical and most of the information documented in his guide is the result of extensive testing and proven results. Those 'grey' areas are included for completeness and are left for the user to decide what value they may have when employed in their particular Prepar3D/hardware/software setup. As you know, the guide includes a section with some useful guidelines for avoiding OOMs.

Tweaking recommendations are made sometimes without solid evidence of efficacy. On the other hand some are made without realising that such tweaks already exist as default, but don't appear in the Prepar3D.cfg file. If the default condition for a particular setting = 1 (Active) and LM consider it to be correct and of value for good performance then adding the entry is only necessary when you wish to try the effect of turning it off (= 0). An example would be ENABLE_MEMORY_OPTIMIZATION=1, which does not appear in Prepar3D.cfg but exists in the sim's software as the default state. Another example would be TextureMaxLoad=6 (default). I use a value of 30 so have added the entry to the Prepar3D.cfg file. As is stated in Rob's Guide, I have found on my setup 'this improves texture loading performance and reduces low quality textures (blurriness)'. In fact I see no blurries these days. I doubt whether this is wholly responsible, but seems to complement the balance of other configuration values as set throughout the sim.

Edit: Capping frame rates in the sim is a way of reducing the load on the GPU while helping to reduce the number of long frames (stuttering). If the limiter is set to unlimited then don't be surprised to see your GPU working upwards of 90% with the consequent heat implications. I have turned off VSync and Triple buffering and performance remains very fluid most of the time. I cap at 31fps which seems effective but, again, this is system specific.

Regards,

Mike

 

1 hour ago, Cruachan said:

Hi Ray,

Pulling your hair out yet? If so, I wouldn't blame you as we've all been down this road at some time or another and know only too well what you are experiencing. Many of these are System specific and may not help you. It can all get a bit confusing when assailed from all sides with suggestions and/or 'recommendations'. Don't forget you can always get back to the sim's pre-tweak default state by renaming Prepar3D.cfg (preserves your previous settings for reference) and deleting the Shaders folder (NOT the ShadersHLSL folder in Prepar3D root. There is a strong case for starting again and building up your settings bit by bit while witnessing the effects produced by each change.

I noticed you are using AffinityMask=255 with HT=ON (11,11,11,11). Actually this entry is not needed as it's the same as AffinityMask=0, the sim's default setting. When you have time to explore this setting a bit further there is no better resource than Steve Waite's excellent article over at his CodeLegend website:

http://www.codelegend.com/forums/viewtopic.php?f=2&t=532

Regards,

Mike

Mike,

Appreciate the advice but it still doesn't answer my question. Why doesn't P3D release VAS once out of complex areas?

I'm very tempted to leave this as it is now and just fly. If I get an OOM then I'll investigate further but quite frankly adjusting the settings in P3D makes no difference to VAS being released.

On the AF thing I have all 8 processors working so see no need to change the current setting.

I spoke too soon... My vas just halved in about 2 seconds coming out of Gatwick on the lam sid...

I can do 10 hours from hk to moscow in the 747 but can do 10 mins out Gatwick. 

 

 

hi all

Ray, have you see in the avsim guide certain tweak who can help you about vas release.

i don't remember exactly but you will be able to find them easily.

You can do a backup of your p3d cfg and erase all inside this file and save with nothing inside, restart P3D and check after close it what is write inside.

I did this few weeks ago and remark there is some tweaks wrote by default

affinity mask you be 85, maybe 116 and reduce /2 ground shadow and cloud shadow

in my case i can start a flight at amsterdam with a very poor vas like 400mb free, took of and arrive at TOC with 1000-1200mb free...

all these posts about tweaks and this and that...

 

Ray a simple yes or no question... are you only getting getting VAS issues when ONLY using the concorde and or fsl ??  

Do you get them using the 777 or 747...

Im getting a nagging feeling its FSL  spotlights.  As its only the FSL i get the issue with on the new drivers,  with the .33 drivers the vas is stable.  With the new drivers its not.  but only in the FSL using spotlights

maybe someone can look at this... thanks in advance

 

[AContain]
LabelColor=FFFF0000
LabelDelay=1000
ShowLabelAirline=0
ShowLabelAirlineAndFlightNumber=0
ShowLabelAirspeed=0
ShowLabelAltitude=1
ShowLabelContainerId=0
ShowLabelDistance=1
ShowLabelFlightPlan=0
ShowLabelHeading=0
ShowLabelManufacturer=1
ShowLabelModel=1
ShowLabels=0
ShowLabelTailNumber=0
ShowUserLabel=0

[ATC]
AutoOpenAirTrafficWindow=0
COMM_MSG_AI_ATC_COLOR=0XFF8C00
COMM_MSG_ATC_AI_COLOR=0X00008B
COMM_MSG_ATC_USER_COLOR=0X006400
COMM_MSG_ATIS_COLOR=00000000
COMM_MSG_USER_ATC_COLOR=0XA52A2A
PilotVoice=0
ShowATCText=0
UsePilotVoice=0

[ATTACHMENTS]
AutoWeaponSwitching=False
HighlightDuration=1.000000
IgnoreAttachmentForces=True
IgnoreAttachmentWeight=True
UnlimitedCountermeasures=False
UnlimitedWeapons=False
WeaponHighlight=False

[Avatar]
DefaultAvatar=Airport Male Falconer

[CONTROLS]
Controls_Current=Standard
Controls_Default=Standard
force_crash_enabled=1
force_gear_bump_enabled=1
force_ground_bumps_enabled=1
force_machinegun_enab led=1
force_master_gain=10000
force_stick_force_enabled=1
force_stick_shaker_enabled=1
JOYSTICKS=0
KBDAIL=64
KBDELEV=64
KBDRUD=64

[DEBUG]
ReportLoadErrors=0

[DISPLAY]
ActiveWindowTitleBackGroundColor=0,28,140,64
ActiveWindowTitleTextColor=255,255,255
BLOOM_EFFECTS=0
ChangeTime=4.000000
Fullscreen=False
FullScreenAutoFill=1
FullScreenBackground=1
FXAA=0
InfoBrakesEnable=True
InfoCountermeasureEnable=True
InfoLowerLeftBackGroundColor=255,0,0,128
InfoLowerLeftTextColor=255,255,255
InfoLowerRightBackGroundColor=255,0,0,128
InfoLowerRightTextColor=255,255,255
InfoOverspeedEnable=True
InfoParkingBrakesEnable=True
InfoPauseEnable=True
InfoSlewEnable=True
InfoStallEnable=True
InfoUpperLeftBackGroundColor=0,0,0,0
InfoUpperLeftTextColorNonUser=255,127,0
InfoUpperLeftTextColorUser=255,0,0
InfoUpperRightBackGroundColor=0,0,0,0
InfoUpperRightTextColor=255,0,0
InfoUpperRightTextEnable=True
InfoWeaponSystemEnable=True
MSAA=8
NonActiveWindowTitleBackGroundColor=24,33,87,64
NonActiveWindowTitleTextColor=255,255,255
SKINNED_ANIMATIONS=1
SSAA=0
TEXTURE_BANDWIDTH_MULT=30
TEXTURE_FILTERING=16
TransitionTime=4.000000
TRIPLE_BUFFER=1
UPPER_FRAMERATE_LIMIT=0
VSYNC=1
WideViewAspect=0

[DISPLAY.Device.NVIDIA GeForce GTX 980 Ti.0.0]
Mode=1920x1080x32

[DynamicHeadMovement]
HeadMoveTimeConstant=1.000000
LonAccelOnHeadLon=-0.020000
LonAccelOnHeadPitch=-0.010000
MaxHeadAngle=5.000000
MaxHeadOffset=0.300000
RollAccelOnHeadLat=0.010000
RollAccelOnHeadRoll=0.100000
YawAccelOnHeadLat=-0.100000

[FACILITIES]
CITY=
COUNTRY=
GTL_BUTTON=4096
STATE=

[GRAPHICS]
AIRCRAFT_REFLECTIONS=1
BUILDING_SHADOWS_CAST=1
BUILDING_SHADOWS_RECEIVE=1
CLOUD_SHADOW_CAST_DISTANCE=1
CLOUD_SHADOW_TEXTURE_SIZE=512
CLOUD_SHADOWS_CAST=1
COCKPIT_HIGH_LOD=1
CONTENT_NO_SHADOW=0
DAWN_DUSK_SMOOTHING=1
DYNAMIC_REFLECTIONS=0
EFFECTS_DISTANCE=0
EFFECTS_QUALITY=0
ENABLE_MEMORY_OPTIMIZATION=1
EXTERIOR_SHADOWS_CAST=1
EXTERIOR_SHADOWS_RECEIVE=1
GROUND_SHADOW_TEXTURE_SIZE=2048
HDR=0
HDR_BLOOM_BLUR_SIGMA=0.800000
HDR_BLOOM_MAGNITUDE=1.000000
HDR_BLOOM_THRESHOLD=3.000000
HDR_BRIGHTNESS=0.700000
HDR_SATURATION=0.800000
HIGHMEMFIX=1
IMAGE_QUALITY=0
INTERIOR_SHADOWS_CAST=1
INTERIOR_SHADOWS_RECEIVE=1
LANDING_LIGHTS=1
LENSFLARE=0
MIPMAP_VC_PANELS=1
NUM_LIGHTS=4
OBJECT_SHADOW_CAST_DISTANCE=1
See_Self=1
SHADOW_LOG_PARTITION_HIGH=0.850000
SHADOW_LOG_PARTITION_LOW=0.850000
SHADOW_LOG_PARTITION_MID=0.850000
SHADOW_LOG_PARTITION_ULTRA=0.850000
SHADOW_NUM_CASCADES_HIGH=7
SHADOW_NUM_CASCADES_LOW=4
SHADOW_NUM_CASCADES_MID=5
SHADOW_NUM_CASCADES_ULTRA=12
SHADOW_QUALITY=3
SIMOBJECT_SHADOWS_CAST=1
SIMOBJECT_SHADOWS_RECEIVE=1
TERRAIN_SHADOW_CAST_DISTANCE=0
TERRAIN_SHADOWS_CAST=0
TERRAIN_SHADOWS_RECEIVE=1
TESSELLATION=1
Text_Scroll=1
TEXTURE_MAX_LOAD=1024
TEXTURE_QUALITY=3
TONEMAP_DAY_EXPOSURE_KEY=0.280000
TONEMAP_NIGHT_EXPOSURE_KEY=0.130000
VEGETATION_SHADOWS_CAST=0
VEGETATION_SHADOWS_RECEIVE=0

[INTERNATIONAL]
ASLAT=2
ASLON=1
MEASURE=1

[MAIN]
HideMenuFullscreen=1
HideMenuNormal=0
LabelsSupported=Airplane, Helicopter
Location=440,129,1480,908,\\.\DISPLAY1
LocationFullScreen=0,0,1920,1080,\\.\DISPLAY1
Maximized=2
ShowInfoText=1
SimObjectPaths.0=C:\ProgramData\12bPilot\SODE\SimObjects
SimObjectPaths.1=C:\Program Files (x86)\12bPilot\SODE\data\SimObjects
SimObjectPaths.10=SimObjects\Avatars
SimObjectPaths.11=SimObjects\Rotorcraft
SimObjectPaths.12=SimObjects\GroundVehicles
SimObjectPaths.13=SimObjects\Boats
SimObjectPaths.14=SimObjects\Animals
SimObjectPaths.15=SimObjects\Misc
SimObjectPaths.16=SimObjects\Submersible
SimObjectPaths.2=SimObjects\Weapons
SimObjectPaths.3=SimObjects\Countermeasures
SimObjectPaths.4=Aerosoft\Mega Airport Prague\simobjects
SimObjectPaths.5=Aerosoft\Mega Airport Zurich V2.0\simobjects
SimObjectPaths.6=Simojects\UT2 Aircraft
SimObjectPaths.7=SimObjects\UT2 Aircraft
SimObjectPaths.8=Aerosoft\Split X\simobjects
SimObjectPaths.9=SimObjects\Airplanes
SimObjectPathsRemarks=These entries were automatically added from SimObjects.cfg by Migration Tool. Set RepairConfig=0 in MigrationTool.cfg to disable.
User Objects=Airplane, Helicopter, Submersible, ExternalSim, Avatar

[MISC]
Com_Rate=7

[MOUSE]
EnableGestures=False

[MULTICHANNEL]
condAccountPassword=0

[MULTIPLAYER]
condAccountPassword=0
FrameSyncRate=0
VoiceVolume=-1.000000

[PANELS]
IMAGE_QUALITY=1
PANEL_MASKING=1
PANEL_OPACITY=100
PANEL_STRETCHING=1
QUICKTIPS=0
SAVE_AND_LOAD_PANEL_STATE=0
UNITS_OF_MEASURE=1

[PointOfInterestSystem]
CycleSetting=0

[REALISM]
AllowEngineDamage=False
AutoCoord=False
CrashDetection=False
CrashTolerance=1.000000
CrashWithDyn=True
GEffect=False
General=1.000000
GyroDrift=False
GyroEffect=1.000000
ManualLights=True
OnCrashAction=0
PFactor=1.000000
RealMixture=True
StressDamage=True
Torque=1.000000
TrueAirspeed=False
UnlimitedFuel=False

[RECORDER]
RecordAirportVehicles=True
RecordAITraffic=True
RecordLeisureBoats=True

[SCENERY]
AUTOGEN_BATCH_LOD=2
AUTOGEN_TREE_MAX_DRAW_DISTANCE=9500.000000
AUTOGEN_TREE_MIN_DISTANCE_TO_LOD=2500.000000
IMAGE_COMPLEXITY=5
MaxRegionsPurgePerFrame=16
POP_FREE_AUTOGEN=1

[SIM]
OPTIMIZE_PARTS=0
SYSCLOCK=0

[SlewTextInfo.1]
AirSpeed=1,5
Altitude=1,3
Heading=1,4
Latitude=1,1
Longitude=1,2

[SlewTextInfo.2]
FrameRate=1,1
LockedFrameRate=1,2

[SlewTextInfo.3]
AirSpeed=1,5
Altitude=1,3
FrameRate=2,1
Heading=1,4
Latitude=1,1
LockedFrameRate=2,2
Longitude=1,2

[SOUND]
PrimaryPlaybackDevice={428E18B3-D736-45DF-A075-8949C6F53CE7}
SOUND=1
SOUND_FADER1=0.503801
SOUND_FADER2=0.500000
SOUND_FADER3=0.500000
SOUND_FADER4=-0.500000
SOUND_LOD=0
SOUND_QUALITY=2
VoiceCaptureDevice={51C48E1E-D519-4B71-8A70-BE81B7387E82}
VoicePlaybackDevice={428E18B3-D736-45DF-A075-8949C6F53CE7}

[STARTUP]
DEMO=0
LOAD_SCENARIO_TOOLS=1
LoadCorePlugins=1
LoadWindow=1
STARTUP_DEMO=

[TERRAIN]
AUTOGEN_BUILDING_DENSITY=1
AUTOGEN_VEGETATION_DENSITY=0
DETAIL_TEXTURE=1
ENABLE_BATHYMETRY=0
LOD_RADIUS=3.500000
MESH_RESOLUTION=25
TESSELLATION_FACTOR=60
TEXTURE_RESOLUTION=29
UseGlobalTerrainView=False
WATER_CLARITY=30
WATER_DETAIL=0
WATER_REFLECT_AUTOGEN_BUILDINGS=0
WATER_REFLECT_AUTOGEN_VEGETATION=0
WATER_REFLECT_CLOUDS=1
WATER_REFLECT_SIMOBJECTS=1
WATER_REFLECT_TERRAIN=0
WATER_REFLECT_USERAIRCRAFT=1
WATER_REFRACT_AUTOGEN_BUILDINGS=0
WATER_REFRACT_AUTOGEN_VEGETATION=0
WATER_REFRACT_CLOUDS=0
WATER_REFRACT_SIMOBJECTS=0
WATER_REFRACT_TERRAIN=0
WATER_REFRACT_USERAIRCRAFT=0

[TextInfo.1]
AirSpeed=1,5
Altitude=1,3
Heading=1,4
Latitude=1,1
Longitude=1,2
WindDirectionAndSpeed=1,6

[TextInfo.2]
FrameRate=1,1
FuelPercentage=1,4
GForce=1,3
LockedFrameRate=1,2

[TextInfo.3]
AirSpeed=1,5
Altitude=1,3
FrameRate=2,1
FuelPercentage=2,4
GForce=2,3
Heading=1,4
Latitude=1,1
LockedFrameRate=2,2
Longitude=1,2
WindDirectionAndSpeed=1,6

[TrafficManager]
AirlineDensity=100
AIRPORT_SCENERY_DENSITY=0
FreewayDensity=0
GADensity=0
IFROnly=0
LeisureBoatsDensity=0
ShipsAndFerriesDensity=0

[USERINTERFACE]
Map_Orientation=2
MUTE_ON_LOST_FOCUS=0
PAUSE_ON_LOST_FOCUS=0
PROMPT_ON_EXIT=1
RestoreTimeOnMove=1
SHOW_MISSION_CAPTIONS=0
SHOW_SCENARIO_WINDOW=1

[VirtualCopilot]
VirtualCopilotActive=0

[WEATHER]
AdjustForMagVarInDialog=1
CLOUD_COVERAGE_DENSITY=7
CLOUD_DRAW_DISTANCE=8
CLOUD_FACING_MODE=0
DETAILED_CLOUDS=1
DisableTurbulence=0
DownloadWindsAloft=0
DynamicWeather=0
MaxGustRampSpeed=200
MaxGustTime=500
MaxVarRampSpeed=75
MaxVarTime=50
MinGustRampSpeed=1
MinGustTime=10
MinVarRampSpeed=10
MinVarTime=5
OPTIMIZE_DENSE_CLOUDS=0
THERMAL_VISUALS=0
TurbulenceScale=1.000000
VolumetricFog=0
WeatherGraphDataInDialog=0
WindshieldPrecipitationEffects=1

 

26 minutes ago, tooting said:

all these posts about tweaks and this and that...

Ray a simple yes or no question... are you only getting getting VAS issues when ONLY using the concorde and or fsl ??  

Do you get them using the 777 or 747...

Im getting a nagging feeling its FSL  spotlights.  As its only the FSL i get the issue with on the new drivers,  with the .33 drivers the vas is stable.  With the new drivers its not.  but only in the FSL using spotlights

 

I only have Concorde so can't comment on 737 or 777. I don't have Spotlights installed either so we can forget that.

I'm going to do as Fred suggests and use Rob's P3D VAS guide. That should help.

Do you have spotlights..Yes or no? 

7 minutes ago, tooting said:

Do you have spotlights..Yes or no? 

I've already said I don't have it installed.

P3D has OOM's over the City of London inbound to EGLL. Not impressed. Never had this problem with FSX:SP2.

Clearly I'm going to have to dial back some settings. Rob's P3D guide now being opened.

I did the following:-

Loaded Nvidia driver 376.33

Deleted P3D.CFG and let P3D build a new one.

Dialled back several settings to free up VAS.

I now have 1360Mb free at EGLL in Concorde. Previously it was 805Mb.

I'm reasonably confident this will prevent OOMs. I may tweak these over time and change to newer drivers.

I obviously had set them too high thinking P3D could cope with VAS far better than FSX. But you have to give it a fighting chance.

Thanks to all who offered advice.

I'm glad to hear that the combination of rebuilding the p3d.cfg and running the 376.33 driver has improved your VAS usage.

I can say that I have seen many instances where users who had tweaked their cfg-file to death started experiencing issues sooner or later, and deleting the configuration file and letting P3d rebuild a new one gave them a relief. Personally, I only "tweak" using the P3D internal display settings (except of maybe the cloud shadow size), and it has worked best for me.

I can confirm the new drivers leak like hell using the the fsl out of Gatwick but Ironically dont leak going in... You couldn't make it up.