Sign in to follow this  
concordeba

PMDG 77W - Consistent VAS issue

Recommended Posts

Problem-

I am sure this is a problem with either the B77W or something route specific. But I haven't ever had any issues with the PMDG 772, mostly and only the B77W - I tried to fly the B77W from Heathrow to Tokyo a few months back, and 2 hours or so into the flight it crashes to desktop. I have completed many 772 flights and had zero issues, however with the 77W it's giving me a VAS leak.  This isn't the first time, but no issues with the PMDG 772 since I've got it, so this must be something to do with the 77W?

 

Detail -

 

BAW297 - Heathrow - Chicago (15th May 2015) - GSTBH (Stand 553) -

See below...

BAW297 - Heathrow - Chicago (16th May 2015) - GSTBJ (stand 545) - 

  • Connect FS up at 1341z
  • Connect to VATSIM
  • Load up Active Sky Evolution
  • Prepare for flight using real world data/loads and adding this into PFPX
  • Load flight plan from CORTE
  • I set the DEP/ARR page to what is likely to be the correct ARR into Chicago - WOBUN3G, 27L and PAINT4 ISL28C, ASP TRANS, VOGLR TRANS respectively.
  • Download wind's from Datalink
  • Pushback at 1510z
  • Take-off at 1531z
  • FSX crashes at 1747z just south of Iceland.  

 

The same thing happened yesterday, with a fairly similar route to NAT TRACK C and the same sort of detail as provided for DOF 160515

 

I use the following scenery -  Heathrow UK2000 (Latest Version) and the latest version of PMDG today, with the previous version yesterday.

 

ROUTE - N0485F340 WOBUN3F WOBUN DCT WELIN UT420 TNT UN57 POL UN601 ABEVI UN590 GOW DCT ERAKA/M084F350 NATC DORYY/M084F360 DCT ROUND/N0481F360 DCT ASP PAITN4

 

VAS started off at 2.4GB (From a Stand on Terminal 5) - a few change of views to just have a look. (I mean it is a game, we do take screenshots)  So in just over 4 hours there's VAS increase of 1.6GB overflying the UK (With no add-on scenery and the North Atlantic ocean). I was watching this continuously increase as we kept flying.

 

2mngp06.jpg

 

dddd0m.jpg

 

b4hi00.jpg

 

212ffrq.jpg

 

 

FSX.cfg

// This file was tweaked on Nov 26, 2012 at 16:49 GMT using Bojote's automated FSX Tweaking & Tuning Service
// Your 'original' fsx.CFG file was backed up at http://www.venetubo.com/fsx/146925c543757f3b42f2cf5451cf8d3b/backup/fsx_backup.cfg
// This file is optimized as follows: 8 core(s), CPU speed 3, HT 1, GPU 2, PREF 2
// You can visit Bojote's FSX Tweaking & Tuning service at http://www.venetubo.com/fsx.html
[BufferPools]
RejectThreshold=131072
UsePools=1
PoolSize=5000000
[VirtualCopilot]
VirtualCopilotActive=0
[SOUND]
AmbientUI=0
AmbientUIMusic=FSX01
AmbientUIMusicVolume=-6.000000
PrimaryDevice={DEF00000-9C6D-47ED-AAF1-4DDA8F2B5C03}
SOUND=1
SOUND_FADER1=0.500000
SOUND_FADER2=0.500000
SOUND_FADER3=0.500000
SOUND_FADER4=0.500000
SOUND_LOD=1
SOUND_QUALITY=2
UISound=1
VoiceDevice={DEF00002-9C6D-47ED-AAF1-4DDA8F2B5C03}
[SlewTextInfo.1]
AirSpeed=1,5
Altitude=1,3
Heading=1,4
Latitude=1,1
Longitude=1,2
[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
ShowLabelTailNumber=0
ShowLabels=0
ShowUserLabel=0
[ATC]
AutoOpenAirTrafficWindow=1
COMM_MSG_AI_ATC_COLOR=FFFF7840
COMM_MSG_ATC_AI_COLOR=FF00FF00
COMM_MSG_ATC_USER_COLOR=FFB6FFB6
COMM_MSG_NONE_COLOR=FFFFFFFF
COMM_MSG_USER_ATC_COLOR=FFFFD21B
PilotVoice=0
ShowATCText=1
UsePilotVoice=1
[TextInfo.1]
AirSpeed=1,5
Altitude=1,3
Heading=1,4
Latitude=1,1
Longitude=1,2
WindDirectionAndSpeed=1,6
[INTERNATIONAL]
ASLAT=2
ASLON=1
MEASURE=0
[CONTROLS]
Controls_Current=Standard
Controls_Default=Standard
KBDAIL=64
KBDELEV=64
KBDRUD=65
[FACILITIES]
CITY=
COUNTRY=
GTL_BUTTON=1543
STATE=
[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
[PointOfInterestSystem]
CycleSetting=0
[GRAPHICS]
AC_SELF_SHADOW=1
AIRCRAFT_REFLECTIONS=1
AIRCRAFT_SHADOWS=0
ALLOW_SHADER_30=1
COCKPIT_HIGH_LOD=1
D3D10=0
EFFECTS_QUALITY=2
GROUND_SHADOWS=0
HIGHMEMFIX=1
IMAGE_QUALITY=0
LANDING_LIGHTS=1
NUM_LIGHTS=8
See_Self=1
TEXTURE_MAX_LOAD=2048
TEXTURE_QUALITY=3
Text_Scroll=1
SHADER_CACHE_PRIMED_10=1693458432
SHADER_CACHE_PRIMED=1693458432
ForceFullScreenVSync=1
[TrafficManager]
AIRPORT_SCENERY_DENSITY=3
AirlineDensity=0
FreewayDensity=0
GADensity=0
IFROnly=0
LeisureBoatsDensity=0
ShipsAndFerriesDensity=0
[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
[REALISM]
AutoCoord=True
AutoTrim=False
CrashDetection=False
CrashTolerance=1.000000
CrashWithDyn=False
GEffect=True
General=1.000000
GyroDrift=False
GyroEffect=1.000000
ManualLights=False
PFactor=1.000000
RealMixture=True
StressDamage=False
Torque=1.000000
TrueAirspeed=False
UnlimitedFuel=False
[Weather]
AdjustForMagVarInDialog=1
CLOUD_COVERAGE_DENSITY=8
CLOUD_DRAW_DISTANCE=3
DETAILED_CLOUDS=1
DisableTurbulence=0
DownloadWindsAloft=1
DynamicWeather=2
MaxGustRampSpeed=200
MaxGustTime=500
MaxVarRampSpeed=75
MaxVarTime=50
MinGustRampSpeed=1
MinGustTime=10
MinVarRampSpeed=10
MinVarTime=5
THERMAL_VISUALS=0
TurbulenceScale=1.000000
WeatherGraphDataInDialog=0
WeatherServerAddress=fs2k.zone.com
WeatherServerPort=80
WindshieldPrecipitationEffects=1
[Misc]
Com_Rate=7
[Main]
HideMenuFullscreen=1
HideMenuNormal=0
HideInfoText=1 
DisablePreload=1 
Location=0,0,1680,1050,\\.\DISPLAY1
Maximized=2
SimObjectPaths.0=SimObjects\Airplanes
SimObjectPaths.1=SimObjects\Rotorcraft
SimObjectPaths.2=SimObjects\GroundVehicles
SimObjectPaths.3=SimObjects\Boats
SimObjectPaths.4=SimObjects\Animals
SimObjectPaths.5=SimObjects\Misc
User Objects=Airplane, Helicopter
ProcSpeed=8885
PerfBucket=7
FIBER_FRAME_TIME_FRACTION=0.33
[Trusted]
E:\Microsoft Flight Simulator X\GAUGES\Bendix_King_Radio.DLL.naananbqkqhauwzaznniqcbznzlkhqbqctzrhwhe=2
E:\Microsoft Flight Simulator X\GAUGES\Magnetic_Compass.DLL.ekbawahtqlawbwohhzzbnintkqwrirrlhiizhhrt=2
E:\Microsoft Flight Simulator X\GAUGES\737-400.DLL.wwokqeqiiarcaazaihltnurwktauanotunbctbwz=2
E:\Microsoft Flight Simulator X\Modules\FSUIPC4.dll.bwlqtbutebeqbwirqibhrcbnlucbzlhnnbaihiuz=1
E:\Microsoft Flight Simulator X\GAUGES\Mooney_Bravo.DLL.qohqcatzahlqtnwaeqtkoacqczwutlbbrqzuhhrw=2
E:\Microsoft Flight Simulator X\FSLabs\DLLs\FSLOptions.dll.iuqkkaacoiruoelzuzucwultlcteaztbkkooewta=1
E:\Microsoft Flight Simulator X\FSLabs\DLLs\FSLEvents.dll.aiobkobortuzetclbnlbalneuhaclwrltiilcekc=1
E:\Microsoft Flight Simulator X\FSLabs\DLLs\FSLSounds.dll.zzhckchcqqrbcqnrzqkbkltlinzzhctczucauolt=1
E:\Microsoft Flight Simulator X\GAUGES\FSL_ConcX.DLL.uzlqqozqataqnioelqwkiqhaakcloinhblwzkklo=2
E:\Microsoft Flight Simulator X\GAUGES\../civa/CIVAC.GAU.owcuehcbiobhcorthbtuqnrnuclkablhacecakie=2
C:\Program Files (x86)\SquawkBox\sbtrans10.dll.wochwkiczwkrllzuhhtotlqkhqotwnekutwwrnaw=1
C:\Program Files (x86)\SquawkBox\sbaicontrol10.dll.trrnzcbzteteekwcnzctibwckctilennlrzkzwba=1
C:\Program Files (x86)\SquawkBox\sbmod10.dll.twwzbktcbceitooobeukzecureeukqbequakciib=1
E:\Microsoft Flight Simulator X\GAUGES\KingAir.DLL.nhklrztqahortclzziibkeoqctbqqiocrrqwbcbc=2
E:\Microsoft Flight Simulator X\GAUGES\Cessna172.DLL.zwzwkwothtoeekbhqurzuikitzqclhuwoqaqiaoe=2
E:\Microsoft Flight Simulator X\GAUGES\KingAir_Radio.DLL.zilhqlrwcihcaaieohoabaauwlccleziiqaiichu=2
E:\Microsoft Flight Simulator X\GAUGES\Cessna.DLL.cwzaczntuwkrrkaeulorertnewkckrelikhaocqq=2
E:\Microsoft Flight Simulator X\GAUGES\Cessna182s.DLL.lkoltebbhwrkhknziwntowbhoilwaiiktiutlell=2
E:\Microsoft Flight Simulator X\GAUGES\CessnaWAlpha.DLL.btukculcozhzklenbuokzuzowrnlehtawktowwuc=2
E:\Microsoft Flight Simulator X\GAUGES\Bell_206B.DLL.chwaioihrnnrkhztetcbtrikqecrwbularcurbqw=2
E:\Microsoft Flight Simulator X\PMDG\DLLs\PMDG_Interface.dll.lwzhzowwabnbaztokltzekiknkzakiwhtenbbhhc=1
E:\Microsoft Flight Simulator X\RAASPRO\RAASPRO.dll.iraeewhotuniertqoaekiqittzietiqlbkoziree=1
E:\Microsoft Flight Simulator X\GAUGES\PMDG_777X.DLL.hwelcokownclorntuqbbkuuihlrnroehieonznlq=2
E:\Microsoft Flight Simulator X\GAUGES\PMDG_777X_3.DLL.iliaeaccnzbhrhuotuwlkukourhzocwecuzrckci=2
E:\Microsoft Flight Simulator X\fsdreamteam\couatl\couatl.exe.waqictanokkctlnuohlaaaonwkeintlwnkurctob=1
E:\Microsoft Flight Simulator X\bglmanx.dll.qubucucnlblonabtucetbnrrhkrrbtloeaokbune=1
E:\Microsoft Flight Simulator X\CPSModulesStart.dll.lawzectzathwhllcieaaneoqirbbiktliutkrqwe=0
E:\Microsoft Flight Simulator X\VistaMare\ViMaCoreX.dll.kaoublitiqqltoqrzqokurtaaqeukcthekrrhhzo=1
E:\Microsoft Flight Simulator X\fsdreamteam\couatl\couatl.exe.tnwqlueiowwbnozcbqbwahchwlbuekoqwliertbn=1
E:\Microsoft Flight Simulator X\bglmanx.dll.ewhoctkbheniolclkcwwnlznwazhllkqibbnnwwe=1
E:\Microsoft Flight Simulator X\Aerosoft\Flight Recorder\AS-FlightRecorder.dll.heetlnutelicqewwezhiwiuqqehertoubuqhzine=1
E:\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus X Extended Base/Panel_Fallback/DLLs/FMGS.DLL.krhqowkarhwcnqukcunuoczheaboktlcbhbblqkl=2
E:\Microsoft Flight Simulator X\SimObjects\Airplanes\Aerosoft Airbus X A320 Extended CFM\panel\ASC.DLL.erzwqaczcozhcihllkukirqunqaozuhttuhthaaw=2
E:\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus X Extended Base/Panel_Fallback/ND/AB_ND_GDI.DLL.aukzibkokkkuqanqkackoutikuhuorwkuzqciene=2
E:\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus X Extended Base/Panel_Fallback/DLLs/AsInput.DLL.ztrnuhbnobrllzkqtqerhroawzchtqotbwuhiwub=2
E:\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus X Extended Base/Panel_Fallback/DLLs/FBW.DLL.rkikqqriqbubotowlwoattnoqnkiaiwwluqqiutn=2
E:\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus X Extended Base/Panel_Fallback/AirbusXE.DLL.tbnlouaqrutihawwucalwrlcrzielaawrtthcctw=2
E:\Microsoft Flight Simulator X\SimObjects\Airplanes\Aerosoft Airbus X A320 Extended CFM NEO\panel\ASC.DLL.erzwqaczcozhcihllkukirqunqaozuhttuhthaaw=2
E:\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus X Extended Base/Panel_Fallback/AirbusXE.DLL.qweqtcrtikzheauzenezbnzkehoocczqkokbawta=2
E:\Microsoft Flight Simulator X\SimObjects\Airplanes\Aerosoft Airbus X A321 Extended IAE\panel\ASC.DLL.erzwqaczcozhcihllkukirqunqaozuhttuhthaaw=2
E:\Microsoft Flight Simulator X\SimObjects\Airplanes\Aerosoft Airbus X A321 Extended CFM\panel\ASC.DLL.erzwqaczcozhcihllkukirqunqaozuhttuhthaaw=2
E:\Microsoft Flight Simulator X\SimObjects\Airplanes\Aerosoft Airbus X A321 Extended IAE NEO\panel\ASC.DLL.erzwqaczcozhcihllkukirqunqaozuhttuhthaaw=2
E:\Microsoft Flight Simulator X\Modules\FSUIPC4.dll.uiwtnrrozqwrcqloarzliwiwwqctuhweiabolnkw=1
E:\Microsoft Flight Simulator X\SimObjects\Airplanes\Aerosoft Airbus X A320 Extended IAE\panel\ASC.DLL.erzwqaczcozhcihllkukirqunqaozuhttuhthaaw=2
E:\Microsoft Flight Simulator X\Aerosoft\ASE_DATA\AseData.dll.eciezcrqweuowbrzethccirteeizinaktnwhlqal=1
E:\Microsoft Flight Simulator X\PMDG\DLLs\PMDG_Interface.dll.kqarbbecnzhlqtluuuutkoitltwukeiziazwnrnw=1
E:\Microsoft Flight Simulator X\RAASPRO\RAASPRO.dll.uzltbriczctczrubronhlqtqnrouikhrhwnttrik=1
E:\Microsoft Flight Simulator X\GAUGES\PMDG_777X.DLL.kiwkhebhcqitqkrwzokbciqwkerwtlcaicerbcnr=2
E:\Microsoft Flight Simulator X\PMDG\DLLs\PMDG_Interface.dll.hkwruribuaktwnwanctqqoiceazhztlonbzbhnha=1
E:\Microsoft Flight Simulator X\GAUGES\PMDG_777X.DLL.qrhbkulqqinnlaiuirkbukenrbacwueqcqhzrzoq=2
E:\Microsoft Flight Simulator X\PMDG\DLLs\PMDG_Interface.dll.rwrbltzqnuhkirokbzcwercacniuzaueiozubnzu=1
E:\Microsoft Flight Simulator X\RAASPRO\RAASPRO.dll.zrtqqtuqqquwikquiubaiotelqktouztaahkhwtq=1
E:\Microsoft Flight Simulator X\GAUGES\PMDG_777X.DLL.zqzocbtckwqqeulhtnlzwcqchtcrrliuhlhqetnn=2
E:\Microsoft Flight Simulator X\Aerosoft\Flight Recorder\AS-FlightRecorder.dll.qriuibioazebnuiohquaqeabubqcqwknhkzhqhck=1
E:\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A318_A319 Base/Panel_Fallback/DLLs/FMGS.DLL.lnabqteaqilttzewwzhqhnohlnrwtlkbrzcizizl=2
E:\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A318_A319 Base/Panel_Fallback/Airbus_ECAMD2D.DLL.ohocwlteeatlokotwubulcrikaebiauttberrbcb=2
E:\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A318_A319 Base/Panel_Fallback/ASC.DLL.lctiqqiohawkkzhhbohwbkennbouhrwbeuwblznk=2
E:\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A318_A319 Base/Panel_Fallback/ND/AB_ND_GDI.DLL.ubiboewluzeezhtwznaeaetzeeqqkzlbarqtlnze=2
E:\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A318_A319 Base/Panel_Fallback/DLLs/AsInput.DLL.brtzqterwlrrhrcnthkcbzberqrzczzuzebclcoc=2
E:\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A318_A319 Base/Panel_Fallback/DLLs/FBW.DLL.biwweboiuirwbruatqeowqhazhtnznnzttclaeke=2
E:\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A318_A319 Base/Panel_Fallback/AirbusXE2.DLL.aucznuzzlreztkqkwebwhqwnnbinibbaqchhcccc=2
E:\Microsoft Flight Simulator X\GAUGES\../SimObjects/Airplanes/Aerosoft Airbus A318_A319 Base/Panel_Fallback/AirbusXE.DLL.ibhhneblkarwueaoncwbclnqzeeziwtiqnetiqcq=2
E:\Microsoft Flight Simulator X\fsdreamteam\couatl\couatl.exe.wrhqqtkwwzwznurzqzzewbawhahrtbaoqoqtitlu=1
E:\Microsoft Flight Simulator X\bglmanx.dll.qonkblniqhiwlzciqiirlbnuhaeuiiurunrrrrtk=1
[TextInfo.2]
FrameRate=1,1
FuelPercentage=1,4
GForce=1,3
LockedFrameRate=1,2
[USERINTERFACE]
Map_Orientation=1
OpenATCOnCreate=0
PAUSE_ON_LOST_FOCUS=0
PROMPT_ON_EXIT=1
PageID=1
SHOW_MISSION_CAPTIONS=0
SITUATION=FLIGHTS\OTHER\FLTSIM
SelectAircraftManufacturer=All
SelectAircraftPublisher=All
SelectAircraftType=777-300ERX
ShowAllACPaintSchemes=1
DisplayFuelAsWeight=1
[SIM]
SYSCLOCK=1
[DISPLAY.Device.NVIDIA GeForce GTX 680.0]
Mode=1680x1050x32
TriLinear=1
[Display]
ActiveWindowTitleBackGroundColor=0,28,140,64
ActiveWindowTitleTextColor=255,255,255
BLOOM_EFFECTS=0
ChangeTime=4.000000
InfoBrakesEnable=True
InfoLowerLeftBackGroundColor=255,0,0,128
InfoLowerLeftTextColor=255,255,255
InfoLowerRightBackGroundColor=255,0,0,128
InfoLowerRightTextColor=255,255,255
InfoOverspeedEnable=False
InfoParkingBrakesEnable=True
InfoPauseEnable=True
InfoSlewEnable=True
InfoStallEnable=True
InfoUpperRightBackGroundColor=0,0,0,0
InfoUpperRightTextColor=255,0,0
NonActiveWindowTitleBackGroundColor=24,33,87,64
NonActiveWindowTitleTextColor=255,255,255
SKINNED_ANIMATIONS=1
TEXTURE_BANDWIDTH_MULT=40
TextureMaxLoad=24
TransitionTime=4.000000
UPPER_FRAMERATE_LIMIT=0
WideViewAspect=True
[JOBSCHEDULER]
AffinityMask=84
[SlewTextInfo.3]
AirSpeed=1,5
Altitude=1,3
FrameRate=2,1
Heading=1,4
Latitude=1,1
LockedFrameRate=2,2
Longitude=1,2
[PANELS]
DEFAULT_VIEW=0
IMAGE_QUALITY=1
PANEL_MASKING=1
PANEL_OPACITY=100
PANEL_STRETCHING=1
QUICKTIPS=0
UNITS_OF_MEASURE=0
[STARTUP]
DEMO=0
LoadWindow=1
SHOW_OPENING_SCREEN=1
STARTUP_DEMO=0
[SlewTextInfo.2]
FrameRate=1,1
LockedFrameRate=1,2
[TERRAIN]
AUTOGEN_DENSITY=2
DETAIL_TEXTURE=1
LOD_RADIUS=4.500000
MESH_COMPLEXITY=100
MESH_RESOLUTION=22
SWAP_WAIT_TIMEOUT=2
TEXTURE_RESOLUTION=29
WATER_EFFECTS=6
TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=4500
TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=3000
[SCENERY]
DAWN_DUSK_SMOOTHING=1
IMAGE_COMPLEXITY=5
LENSFLARE=1
MAX_ASYNC_BATCHING_JOBS=3
SmallPartRejectRadius=4
[MAPVIEW_MAP]
SHOW_AIRPORTS=1
SHOW_VORS=1
SHOW_NDBS=1
SHOW_APPROACHES=1
SHOW_INTERSECTIONS=0
SHOW_VICTOR=0
SHOW_JET=0
SHOW_AIRSPACE=1
SHOW_FLIGHTPLAN=1
SHOW_WEATHERSTATIONS=1
SHOW_WEATHERSYSTEMS=1
SHOW_DATATAGS=1
SHOW_TERRAIN=1
show_flight_history=1
[FSDREAMTEAM]
AntiPopUp=1
AltitudeCull=1
[MULTIPLAYER]
AccountLogin=1
condAccoutPassword=0
LanUsername=Player

 

 

 

 

 

 

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

and the latest version of PMDG today, with the previous version yes

Do you mean PFPX? Have your entered a KORD runway into the FMC?

Share this post


Link to post
Share on other sites

Same as Kyle:  Start eliminating things.  Active Sky Evolution was for FS9, have you added textures to it? I'd be looking at the weather engine first since you are eating up VAS over water.  Also, it is puzzling that the B77L is okay but you have problems with B77W - they are pretty much the same thing code-wise.  The screenie you attached with the skin missing is indicative of low memory so I assume that was taken after you hit the wall on VAS.  Also, make sure you don't have any photoreal scenery loaded other than your departure EGLL.

Share this post


Link to post
Share on other sites

Have you tried without any weather, scenery, or AI?

I have just tried the following. Heathrow, London City and Luton Extreme Deactivated. Default LHR. Active Sky Evo. No VATSIM connection.

(Changing of views, VC> Spot View > VC, but not excessively etc)

 

VAS LOG at Default Heathrow - Does this look normal?

2.170GB @ 1849z
2.359GB @ 1917z after setup for KORD (FPL and perf data loaded/FD setup for departure)
2.468GB @ 1942z
2.509GB @ 1949z
2.712GB @ 2108z
2.725GB @ 2117z - 1hr after setup for KORD
I very much doubt that it will be Active Sky Evolution, that's never caused me issues in the many years I've had it. 
 

Do you mean PFPX? Have your entered a KORD runway into the FMC?

 

That is correct, I entered everything as per flight plan into FMC.  Loaded CORTE and then added DEP/ARR for both EGLL/KORD into the FMC.  Once that was done, I then loaded wind-data from uplink. I am just going to park up the 77W overnight at Heathrow with V3.06 installed (Latest Version) and see what the VAS log says. Gives me the best test.  Currently parked up at Stand 545, with Active Sky on.

2.310GB @ 2122z (Start-up)  FSX, Heathrow UK2000 V3.06 and latest version of PMDG 77W
2.599GB @ 2154z (Cold mode, but with GPU on) 
2.614GB @ 2204z (In 10 minutes a 0.015gb (15.88mb rise))
 
Is that sort of VAS usage correct? On both logs.
 

Same as Kyle:  Start eliminating things.  Active Sky Evolution was for FS9, have you added textures to it? I'd be looking at the weather engine first since you are eating up VAS over water.  Also, it is puzzling that the B77L is okay but you have problems with B77W - they are pretty much the same thing code-wise.  The screenie you attached with the skin missing is indicative of low memory so I assume that was taken after you hit the wall on VAS.  Also, make sure you don't have any photoreal scenery loaded other than your departure EGLL.

 

 

Active Sky Evolution was released in 2010/2012 no? So surely it was for both, or are you adding it's FS9 coded and works with FSX, whereas ASN is better for FSX? If so I'll look into purchasing it soon. I have no photoreal scenery, as I only really see the benefit of having the airports when considering most of my flights are long-haul/short haul airline ops.  I got the screenie just before OOM, that was at 3.7GB VAS. I have done quite a few flights in the PMDG 77L.  I have just had a look, I've done zero completed flights with the B77W since I got it.  

BAW5 to Tokyo OOM'd in July 2014
Yesterday and today I got an OOM for the BAW297 to KORD.   

I have completed the following flights since July 2014 in the B77L. None in the 77W.

EGKK-KJFK and KJFK-EGKK (UK2000 & FSDT) EGKK-KMCO (UK2000 & Taxi 2 Gate) - October 2014
KMCO-EGKK -November 2014
EGLL-KJFK (UK2000 & FSDT),   
EGLL-OMDB (UK2000 and FlyTampa Rebooted) - February 2015
KJFK-EGLL, 
EGKK-TBPB-EGKK (No reset of Flight Sim), 
EGLL-OMDB, 
EGKK-MMUN and MMUN-EGKK (Payware Scenery for Cancun, Barbados Freeware) - April and May 2015.

I do find it all a bit strange.

Edited by concordeba

Share this post


Link to post
Share on other sites

Not specifically related to your problem, but I stumbled upon your thread and noticed that you used Bojotes tool for tweaking FSX..

Im not sure what system you have, but I would in general not advice anyone to use bojotes tweaks anymore as they are simply, what I would argue, outdated with the knowledge we have now and hardware..

 

 

Eg. What does ProcSpeed=8885 do?

 

TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=4500  ??
TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=3000 ??

I for sure dont have them, and I have never been happier with my config.. My system seems to be worse then yours

 

 

I would strongly suggest you generated a new FSX.cfg, and used Tabs' guide for setting it up.. Or some PMDG guide, as its very good

 

Of the top of my head i Think the only four mods I have added to my CFG is Highmemfix=1 wideviewaspect=1 texture_max_load=2048 and the AM tweak..

 

You are welcome to send my an PM or quote me here if you need any assistance..

Share this post


Link to post
Share on other sites

During the last round of VAS testing that we did for latest B77X, all tests were run with no weather and no traffic, same airports and routes, changing only one variable at a time.  That eliminates unknown variables.  Tests were run with both B77L and B77W and we saw no difference but that is not to say you're hallucinating.  You may be onto something and the big payoff comes if you can narrow down the problem to just the B77W in a specific scenario where the problem is repeatable.  Then others can run the same scenario and expect to get the same problem, which leads to the solution.

 

Active Sky Evolution is probably just fine... I was just looking for anything.  I don't think the problem is in your fsx.cfg either but making a backup and running it once with minimum tweaks is something you could put on the to do list as you are troubleshooting.  But, first priority should be getting a well defined scenario that we can repeat.

Share this post


Link to post
Share on other sites

I would perform a full reinstall of ActiveSky (and perform testing without it).  On my system, I had higher-than-normal VAS usage and stutters after one of the ASN patches last year.  Reinstalling seemed to resolve the issue.  Correlation isn't causation, naturally, but it is indeed time to isolate variables.

Share this post


Link to post
Share on other sites

Robbie,

 

I agree with all that's been posted so far.  However, from the data you supplied, I don't believe you are using the correct method to determine how much Virtual Address Space (VAS) you are using or that you have left.  This takes you to en excellent write-up on what VAS is as well as a link to a free tool (Process Explorer) you can download from Microsoft's Mark Russinovich.  This tool shows you how much VAS you are currently using. 

 

You can also use FSUIPC to measure VAS, and this method shows how much VAS is remaining. Here's a link to an excellent explanation and easy instructions on how to configure FSUIPC.

 

Hope this helps a bit,

Share this post


Link to post
Share on other sites

Okay, so we know you OOM on a EGLL-KORD flight. Try KORD-EGLL with the same settings you are using on your westbound flight. See if that one completes okay. And don't use time compression or acceleration or whatever it's called. Don't change the cfg file for now. After we see the results of this eastbound flight, we can probably move on to the no weather/no traffic that Dan Downs mentioned. This needs to be done in a methodical way. You can't just start trying everything at once. Do the eastbound flight and see what happens.

Share this post


Link to post
Share on other sites

Not specifically related to your problem, but I stumbled upon your thread and noticed that you used Bojotes tool for tweaking FSX..

 

 

I definately need to re-do my CFG, if you fancy helping that would be appreciated. Many years ago I was stuck on Flight Sim and had nothing better to do, now I have been working since I built this PC (The above flight list show's I hardly get the time anymore) - It does need a clean up and to get far better performance.

During the last round of VAS testing that we did for latest B77X, all tests were run with no weather and no traffic, same airports and routes, changing only one variable at a time.  That eliminates unknown variables.  Tests were run with both B77L and B77W and we saw no difference but that is not to say you're hallucinating.  You may be onto something and the big payoff comes if you can narrow down the problem to just the B77W in a specific scenario where the problem is repeatable.  Then others can run the same scenario and expect to get the same problem, which leads to the solution.

 

Active Sky Evolution is probably just fine... I was just looking for anything.  I don't think the problem is in your fsx.cfg either but making a backup and running it once with minimum tweaks is something you could put on the to do list as you are troubleshooting.  But, first priority should be getting a well defined scenario that we can repeat.

 

I am definitely onto something,  I removed London City Extreme V1.00, Luton Extreme, Gatwick V3 and Heathrow V3.03

 

Re-Installed Gatwick V3 and Heahtrow V3.06 - so far more stable.

 

I would perform a full reinstall of ActiveSky (and perform testing without it).  On my system, I had higher-than-normal VAS usage and stutters after one of the ASN patches last year.  Reinstalling seemed to resolve the issue.  Correlation isn't causation, naturally, but it is indeed time to isolate variables.

 

Here is the results from last nights test, the sim is still running.  This is post running a complete re-install to the latest versions of UK2000. Maybe they was giving a memory leak?  However could it be the addition of the SID/STAR setup?

2.310GB @ 2122z (Start-up) FSX, Heathrow UK2000 V3.06 and latest version of PMDG 77W
2.599GB @ 2154z (Cold mode, but with GPU on) 
2.614GB @ 2204z (In 10 minutes a 0.015gb (15.88mb rise))
2.634GB @ 0653z
2.650GB @ 0729z (after sitting at stand 545 all night)

Robbie,

 

I agree with all that's been posted so far.  However, from the data you supplied, I don't believe you are using the correct method to determine how much Virtual Address Space (VAS) you are using or that you have left.  This link takes you to en excellent write-up on what VAS is as well as a link to a free tool (Process Explorer) you can download from Microsoft's Mark Russinovich.  This tool shows you how much VAS you are currently using. 

 

You can also use FSUIPC to measure VAS, and this method shows how much VAS is remaining. Here's a link to an excellent explanation and easy instructions on how to configure FSUIPC.

 

Hope this helps a bit,

Hello, I am using Process Explorer and Virtual Size - menu -> View -> Select Columns -> [Tab] Process Memory -> [check] Virtual Size -> OK. - It's been stable all night.

Share this post


Link to post
Share on other sites

I am sure this is a problem with either the B77W or something route specific. But I haven't ever had any issues with the PMDG 772, mostly and only the B77W - I tried to fly the B77W from Heathrow to Tokyo a few months back, and 2 hours or so into the flight it crashes to desktop. I have completed many 772 flights and had zero issues, however with the 77W it's giving me a VAS leak.  This isn't the first time, but no issues with the PMDG 772 since I've got it, so this must be something to do with the 77W?

 

Do you have the latest update installed? If you installed it simply clicking repair it, then most likely you did not successfully install the latest update.

 

To check if you do have it or not. Do this in both the -200LR and -300ER.

 

Enter and activate a route, fill out the PERF INIT pages, and then go to the VNAV CLB page and change the CLB speed by manually inputting 325 as the CLB speed. If it gives you a invalid entry message in the scratchpad, then you do not have the latest release!!!!!!! (limited to 320kts in the previous release). If it accepts your entry of 325 then you have the latest release.

 

Now assuming you dont.... continue below.

 

KORDs missed approaches have the code that was causing the VAS leak in the previous PMDG 777 version. That leak was fixed with the latest update on May 7th. I also had a VAS leak leading to a OOM crash while flying to KORD with the previous version. KLAX, VHHH and plenty of other airports had the same code causing the VAS leak and crash. Otherwise no OOMs for me outside of these airports.

 

Here is what I suggest,

 

1. Open operations center, it will take a snapshot of your installed liveries. Close operations center when it is done loading up.

 

2. Uninstall the -300ER, uninstall the -200LR base package (in this very order).

 

3. Install the latest -200LR base package release, and then install the latest -300ER base package release (in this very order)

 

3. Then fly to KORD from EGLL again. You will not encounter the leak anymore. UNLESS....it is caused by your settings.

 

I have flown to KORD twice since updating to the latest release, both 13 hour plus flights, and no VAS OOMs. My rare OOMs were purely due to the now fixed memory leak caused by the missed approach code.

 

Report back!

 

Leo Cal

Share this post


Link to post
Share on other sites

Hello,

 

I think you might be right, when I entered the DEP/ARR into the FMC, I've had a VAS leak. I use Navigraph, so what I will do is completely re-install PMDG 777, as even though I tried what you said. Simply clicking repair hasn't done the job?  Was RJAA (Tokyo Narita?) also one of these airports that caused the Memory leak.   Either way it's definitely something happening once I've setup the FMC.

 

vymurs.jpg

2.310GB @ 2122z (Start-up) FSX, Heathrow UK2000 V3.06 and latest version of PMDG 77W
2.599GB @ 2154z (Cold mode, but with GPU on) 
2.614GB @ 2204z (In 10 minutes a 0.015gb (15.88mb rise))
2.634GB @ 0653z
2.650GB @ 0729z (after sitting at stand 545 all night)
3.103GB @ 0827z (After setting up FMC)

Thanks all for your help.

Share this post


Link to post
Share on other sites

 

 


Simply clicking repair hasn't done the job?

 

REPAIR is not the same as update.... REMOVE then install.  Check version in Ops Center to verify you are current.

Share this post


Link to post
Share on other sites

Like Dan said, COMPLETELY remove the aircraft and reinstall it.  This does indeed sound similar to the bug we discovered, which has since been fixed on the latest, full installer.

Share this post


Link to post
Share on other sites

Hello,

 

I think you might be right, when I entered the DEP/ARR into the FMC, I've had a VAS leak. I use Navigraph, so what I will do is completely re-install PMDG 777, as even though I tried what you said. Simply clicking repair hasn't done the job?  Was RJAA (Tokyo Narita?) also one of these airports that caused the Memory leak.   Either way it's definitely something happening once I've setup the FMC.

 

 

Robbie, did you take that screenshot BEFORE or AFTER doing the full uninstall and reinstall? 

 

If you took it before, then you already had the latest version installed. How do I know that? Because it would not have let you enter 325kts on the VNAV CLB page in any previous version except for the latest. In this case, something completely unrelated to the PMDG 777 is causing your leak!!!!

 

If you took it after re-installing, then you need to attempt the same flight again and report back. Having the latest version installed successfully patches the missed approach related VAS leak.

 

 

 

 

REPAIR is not the same as update.... REMOVE then install.  Check version in Ops Center to verify you are current.

 

When you merely click repair (which as we know doesnt successfully update the PMDG 777), and then launch operations center it now tells you that you are up to date and that there are no pending updates!!!

 

 I suspect this is resulting in many "updating" their PMDG 737NG/777 by clicking repair in the new installer and not realizing the update did not actually happen. 

 

Leo Cal

Share this post


Link to post
Share on other sites

REPAIR is not the same as update.... REMOVE then install.  Check version in Ops Center to verify you are current.

 

 

Like Dan said, COMPLETELY remove the aircraft and reinstall it.  This does indeed sound similar to the bug we discovered, which has since been fixed on the latest, full installer.

 

 

Robbie, did you take that screenshot BEFORE or AFTER doing the full uninstall and reinstall? 

 

If you took it before, then you already had the latest version installed. How do I know that? Because it would not have let you enter 325kts on the VNAV CLB page in any previous version except for the latest. In this case, something completely unrelated to the PMDG 777 is causing your leak!!!!

 

If you took it after re-installing, then you need to attempt the same flight again and report back. Having the latest version installed successfully patches the missed approach related VAS leak.

 

That makes perfect sense but I have version 1.10.6492 installed on both aircraft. I think it must be something to do with the fact I just hit repair and didn't do a complete full install.  There only seems to be a VAS leak once I have entered all the Information into the FMC.  Can someone do the same for me? I can send the details I put into the FMC if needed be, and see if they get the same issue.  I sat at EGLL all night and left my PC running - not OOM. I enter data, and the VAS keeps going up.

2.310GB @ 2122z (Start-up) FSX, Heathrow UK2000 V3.06 and latest version of PMDG 77W
2.599GB @ 2154z (Cold mode, but with GPU on) 
2.614GB @ 2204z (In 10 minutes a 0.015gb (15.88mb rise))
2.634GB @ 0653z
2.650GB @ 0729z (after sitting at stand 545 all night)
3.103GB @ 0827z (After setting up FMC)

Share this post


Link to post
Share on other sites

 

 


I think it must be something to do with the fact I just hit repair and didn't do a complete full install.

 

I would see if the full reinstall fixes the problem first.

 

I've been running your described scenario, sitting at the gate for an hour so far.  My VAS usage was 2.3 GB cold and dark, and holding steady around 2.45 GB after powering up and entering FMC data.

Share this post


Link to post
Share on other sites

Hello,

 

I've just done the following. Thanks for all your help so far.

 

  • Removed PMDG 777's packages,
  • Removed everything in the PMDG folder.
  • Did a CCleaner of the Registry
  • Re-Installed PMDG 777-200
  • Re-Installed PMDG 777-300
  • Repaired Liveries in folder
  • Re-Installed latest Navigraph AIRAC

Active Sky Evo loaded, FSX loaded, PMDG 777-300 loaded on stand 553 at Heathrow. Engine's shut down (I would prefer it was a cold and dark start all the time IMHO - but haven't quite read how to do this?) - It's raining but VAS is stabled at 2.5GB.  Will leave FSX for 1 hour, then enter all the data, then leave it for a few hours and see what happens.  Since typing this VAS has dropped.

 

VAS - 0940z @ 2.5GB

VAS - 0944z @ 2.480GB

VAS - 1119z @ 2.721GB

Share this post


Link to post
Share on other sites

Again, you have weather and scenery loaded. You need to remove these variables. You're not helping yourself find a cause/solution.

Share this post


Link to post
Share on other sites

 

 


but haven't quite read how to do this?

 

Intro manual. You'll probably find a bunch of other cool things in there, too. For your convenience, though:

 

MENU KEY > PMDG SETUP > [Prompts over on the right for panel loading, saving and default states]

 

 

 


Since typing this VAS has dropped.

 

VAS is dynamic. As Kyle mentioned, the fact that you're running weather means that VAS will be even more noticeably dynamic.

Share this post


Link to post
Share on other sites

Sure shoot me an PM with system details etc and I can give you some pointers and tips

I definately need to re-do my CFG, if you fancy helping that would be appreciated. Many years ago I was stuck on Flight Sim and had nothing better to do, now I have been working since I built this PC (The above flight list show's I hardly get the time anymore) - It does need a clean up and to get far better performance.

 

(...)

Share this post


Link to post
Share on other sites

 

 


a see, this is completely contradictory to what Robert has posted at the top off the General Forum regarding the 777 updates.

 

I believe you but I can't find what you are referencing and as there are many pages of posts in that thread please point me to the right place.  The behavior of the installer is such that if there is an update then it will act like an update with a message like "updating version xxxx to version yyyy.  I've never seen repair provide that message, but it could be because I have a concurrent FSX/FSXSE installation and the installer will do as Robert mentioned in his first post:  It will say sorry, unable to repair.

 

Please correct me and point me to the right post. Thanks.

Share this post


Link to post
Share on other sites

Please correct me and point me to the right post. Thanks.

 

http://forum.avsim.net/topic/468253-07may15-updates-released-for-all-777-packages-fsxfsx-sep3d/?p=3234554

 

I quoted the what-appears-to-be-somewhat-confusing bit below.

 

PMDG eCommerce Customers:

 

If you purchased from PMDG, log-in to your PMDG eCommerce account and access your account history.

Download from the account history.

While you are waiting for the download, run the PMDG Operations Center, then close it. (This causes it to take a most-current snapshot of your installed liveries!)

Run the installers, (base package first, then the 300ER expansion!) and follow their instructions. In some cases, depending upon your specific installation options, the installer may tell you it cannot "update/repair" your setup- in which case you simply need to uninstall the 777, then run the new installer.

Run the PMDG Operations Center and go to the settings wheel at the top right. Instruct the OC to update your liveries and reinstall them all, etc.

Go Fly. Have fun!

 

In my installation (a standard, FSX-SP2 installation - no FSX-Steam - no nutin; :) ), The repair option was present. I suspect is also was for the OP if this thread.

 

Now, Robert above doesn't mention anything about uninstalling the 777 preceding the upgraded install. The fact that he wants you to run the ops center to 'capture' currently installed liveries kind of implies (to me anyways) that he kind of wants you to keep the 777 installed. I'm pretty sure specific user's liveries and options would be lost from the Ops Center if the 777 was uninstalled.

 

The language around the "update/repair" is a little vague. Granted, when you run the new installer, you are (typically) presented with two options. Uninstall, or repair. There is no "update" prompt or action. But Robert only states the installer may prompt you that cannot repair, then you have to uninstall - as it's an action only required in that case. Users seeing the cannot repair I suspect are running an even older version of the 777, or as in your case - have two FSX installs and the respective PMDG registry entries.

 

So my understanding/process was:

 

- Download new installer from PMDG eCommerce

- During download, ran Ops Center (Noted message that this update to 777 was available - but didn't action anything through Ops Center).

-Closed Ops Center (and didn't have FSX or anything like that running of course)

- Ran new installer (200LRF only - don't have -300)

- Wasprompted with Uninstall or Repair

- Selected Repair

- InstallWizard appeared to do a pretty thorough install of 777 update (For me, it took just as long as I recall the initial install did - appeared to reinstall all the gauge and dll magic...and those pesky large-chunky .DEM files).

- Install complete (or should I say 'Repair') - Installer and stuff closed.

- Ran Ops Center - Was prompted to repair liveries and such - completed that. Version info checked serviceable as current.

- Went on me merry way.

- Re-installed current NavData as installer appeared to install default NavData.

 

I agree with you regarding an installer providing an "update" kind of message typically - but I'm pretty sure the InstallShield installer PMDG currently uses doesn't support that.

 

I hope one can understand what I'm trying to get at here. I know my explanation is perhaps as head-scratching as Robert's post ;). The wonders of the written word - so powerful - but so limiting!

 

I just don't want PMDG to be fighting all this tickets/support regarding existing memory issues when they could nip-it-in-the-bud with a true, full re-install.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this