Jump to content

John Pavey

Members
  • Content Count

    20
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

2 Neutral

About John Pavey

  • Birthday 05/04/1948

Profile Information

  • Gender
    Male
  • Location
    Toronto, Ontario

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    Other
  • Virtual Airlines
    No

Recent Profile Visitors

661 profile views
  1. For the past two years, I have had no problems using Honeycomb's BTQ in P3D V4/V5, MSFS2020 and XPlane 11. Yesterday, I attempted a flight in MSFS2020. After it loaded, I noticed that the throttles were fluttering approximately mid-way through their axes in the simulator. I attempted to move the throttles using the BTQ and while they did move in the simulator, it wasn't through their full range nor could I get the throttles to move to their close position and stay there. I attempted closing down the sim and computer, then restarting and reloading a flight. The same problem occurred, I tried loading flights in both P3D and Xplane to see if the problem was isolated to MSFS. The same problem occurred in P3D but in XPlane the throttle were in their closed position when the flight loaded and movement was fine.An I also tried: a) detaching and attaching the BTQ to my system. b) calibrating the axis in using first the windows game controller setup and then calibrating the axis in both P3D and MSFS; c) loading different aircraft in both P3D and MSFS - again, no change. Any suggestions before I try uninstalling and reinstalling MFS2020? I
  2. Well - happy to report that after setting my BIOS settings to Optimized Default, I have just successfully completed a 2 hour flight with no system crash or app crash!! Here's hoping that this signals the end of what has been a very frustrating process. Also frame rates were really no different than when my computer was overclocked (which makes me wonder what the whole point of overclocking was (may the story will be different with FSX?) Anyhow, thanks for all your help, Jim
  3. Good to know!...So if I understand this correctly, all I have to do in the Overclocking section of the Bios is simply press the F5 key which is the option for "Optimized Defaults"?
  4. OK Jim - will give it one more try as I really enjoyed the first 3 months or error free P3D flying. Have done a quick review of the link you provided and at first glance, it looks like I may have to remove the overclocking of my CPU as an initial step. Will have to read up on this to understand how to do - hopefully won't destroy my CPU in the process!!. Will update this thread if I have any success. Thanks again.
  5. Sad to say, I think you’re right that I wasn’t meant to run P3DV4! The only positive was that over the past 2 days, I was able to successfully fly with 3 different default aircraft for flights lasting 30 or so minutes with no problems. And then the final straw occurred. I downloaded and installed PMDG’s 737NGX, launched P3D, created a scenario, loaded it, programmed the FMC; pushed back, taxied and took off, climbed beyond 12,000 feet and BINGO – crash! This time Event Viewer said it wasn’t an app error but a system crash (Kernel-Power). So I’m giving up on P3D for a while. I’m tired of wasting my time trying to problem solve – I just want to practice flying. It’s crazy that with a clean SSD with only Windows 10 and P3D loaded , no add-ons except PMDG, this should occur. So it’s back to FSX and maybe try XPlane. It just boggles my mind the LM can design complex systems to operate real sophisticated aircraft but can’t put the puck in the net for a 64bit flight simulator.
  6. Thanks for your suggestions, Jim - will try the troubleshooting tips outlined in the Guide and update if I find a fix (hopefully this crash is a "one-off" and not symptomatic of the curse that's been laid on me!) BTW - while I had Active Sky installed previouosly, I haven't had the opportunity to install it since I added the new SSD - the only software I was operating at the time of the crash was Windows and P3D only - no add-ons whatsoever.
  7. Here's the EventViewer report Faulting application name: Prepar3D.exe, version: 4.4.16.27077, time stamp: 0x5bfdbb35 Faulting module name: D3DCOMPILER_47.dll, version: 6.3.9600.16384, time stamp: 0x5215f2ea Exception code: 0xc0000005 Fault offset: 0x0000000000321f20 Faulting process id: 0x688 Faulting application start time: 0x01d4b7f15210e127 Faulting application path: D:\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: D:\Lockheed Martin\Prepar3D v4\D3DCOMPILER_47.dll Report Id: 1bcaddfa-4637-46f5-81bc-0a788146a174 Faulting package full name: Faulting package-relative application ID:
  8. After a few weeks of experiencing CTDs (mainly due to TERRAIN.DLL faults) (with the only add-on being (AS for P3D4!), I bit the bullet - bought and installed a new Samsung 1TB SSD, installed Windows 10, Installed Drive Booster to ensure all drivers are up-to-date; downloaded and installed P3DV4; started up the simulator; made 1 change to the config (Sound - changed speaker output to my Sound card instead of the default speakers); selected a scenario using the default fighter jet and default locations, weather etc; the scenario was successfully loaded; took off and flew around for just over a minute and --- you guessed it - my first crash!! The good news is that the fault (this time) wasn't TERRAIN.DLL - the reported module was D3DCompiler_47.dll; (Didn't think I'd need to download appcrashview this early in the game, so the only report I've attached is from EventViewer (see below). I checked out the CTD Guide and the only faults close to what EventViewer reported appear of pp 32/33 (D3D9.dll and D3D11.dll) but I haven't installed SweetFX or ENBSeries modules so not sure if this applies. Any suggestions as to how to fix this? In the meantime, might as well install STEAM FSX - at least my experience with it has been more reliable than P3D (even if the frame rates are not as robust!)
  9. That's reassuring to know I have a bit of a stretch to go - having just made it to 70. Although I feel more like 80. No longer any fun climbing the struts of a 172 to check the gas tanks!
  10. Thanks for the dll clarification - I thought either I had the wrong version of the CTD guide or I was experiencing the initial onset of dementia!
  11. Thanks, Jim. I restored the default settings on the GPU as you suggested and flew another 3 hour flight and with NO CTD!!! (Re page 36 of the Guide, I couldn't find a specific reference to the nvwgf2umx.dll reported in the AppCrash report - is the "nvlddmkm.dll" a similar fault?); As to the TERRAIN.dll crashes (I've had 17 since late August!), I think for now, I will refrain from installing any add-ons and try flying 3 to 5 more 3 hour scenarios over the next wek to see if there are any further issues. If not, I'll start adding airports (1 at a time) and hope things go well.
  12. My most recent P3D uninstall/reinstall was on Nov 16 and the following recaps my experience since then: Nov 16: Installed P3D; made minor config changes to address my cockpit setup (eg., Wideaspect View=True; ignore crashes; disable error reporting and disable controllers (I use FSUIPC5)). Installed PMDG 737NGX; Flew KDEN to KSFO (default scenery) - no CTD; Installed FlightBeam’s KSFO and KDEN sceneries; Nov 17: Flew KDEN to KSFO using add-on sceneries – CTD occurred around 2.5 hours – TERRAIN.DLL fault; Disabled KDEN and KSFO add-ons; Flew KDEN to KSFO again using default scenery – No CTD occurred; Installed Flytampa’s CYYZ scenery Nov 18: Flew CYYZ (Addon) to KFLL (Default) – NO CTD occurred; Installed Active Sky for P3Dv4; P3D config file modified to increase cloud coverage density to maximum (as recommended by Active Sky); Flew CYYZ (addon) to CYHZ (default): No CTD occurred Nov 20: Flew CYHZ (Default) to CYYZ (Addon) – NO CTD occurred; installed LatinVFR’s KMIA; Nov 21: Flew KMIA to CYYZ (both addons); CTD occurred after 2+ hours: - TERRAIN.dll fault; Disabled KMIA addon; Nov 22: Flew KMIA (default) to CYYZ (Addon): CTD occurred after 2+ hours: nvwgf2umx.dll fault reported. I’m at a loss as to next steps; First, I have no idea what the latest fault (nvwgf2umx.dll) means; and second, what’s causing all the TERRAIN.dll faults. I’ve included the latest Eventview and Appcrash reports re the nvwgf2umx fault. I’d be happy to include the reports for the TERRAIN.dll as well. Any help or suggestions would be much appreciated. ********************** Event Viewer Report ********************** Faulting application name: Prepar3D.exe, version: 4.3.29.25520, time stamp: 0x5b2c3263 Faulting module name: nvwgf2umx.dll, version: 25.21.14.1694, time stamp: 0x5bea3171 Exception code: 0xc0000409 Fault offset: 0x000000000120a8b4 Faulting process id: 0x242c Faulting application start time: 0x01d482672a774763 Faulting application path: D:\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_6992f55a2cc4b209\nvwgf2umx.dll Report Id: ad2911a3-60d1-4302-a59e-8ac9c56619fd Faulting package full name: Faulting package-relative application ID: *********************** APPCRASHVIEW REPORT *********************** Version=1 EventType=BEX64 EventTime=131873734907647799 ReportType=2 Consent=1 UploadTime=131873734915834533 ReportStatus=268435456 ReportIdentifier=2187f922-ec89-457c-8fab-c8c358aa79d2 IntegratorReportIdentifier=ad2911a3-60d1-4302-a59e-8ac9c56619fd Wow64Host=34404 NsAppName=Prepar3D.exe OriginalFilename=Prepar3D.exe AppSessionGuid=0000242c-0006-005a-6347-772a6782d401 TargetAppId=W:0000669526e145a32afc23bdda8830b2dfc500000904!0000d5fc0d7ce97f85830080d86c7b00cc081e7b7730!Prepar3D.exe TargetAppVer=2018//06//21:23:18:59!2d5e49!Prepar3D.exe BootId=4294967295 TargetAsId=1629 UserImpactVector=858796848 IsFatal=1 Response.BucketId=9c3820ba42fc84fb657cb14fcd070961 Response.BucketTable=5 Response.LegacyBucketId=1548307328208931169 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=Prepar3D.exe Sig[1].Name=Application Version Sig[1].Value=4.3.29.25520 Sig[2].Name=Application Timestamp Sig[2].Value=5b2c3263 Sig[3].Name=Fault Module Name Sig[3].Value=nvwgf2umx.dll Sig[4].Name=Fault Module Version Sig[4].Value=25.21.14.1694 Sig[5].Name=Fault Module Timestamp Sig[5].Value=5bea3171 Sig[6].Name=Exception Offset Sig[6].Value=000000000120a8b4 Sig[7].Name=Exception Code Sig[7].Value=c0000409 Sig[8].Name=Exception Data Sig[8].Value=0000000000000002 DynamicSig[1].Name=OS Version DynamicSig[1].Value=10.0.17134.2.0.0.768.101 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1033 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=15c4 DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=15c4e3dea49de45ced1c574117f64a29 DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=ab2d DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=ab2d3928f6579956eb84aeed043205ad UI[2]=D:\Lockheed Martin\Prepar3D v4\Prepar3D.exe LoadedModule[0]=D:\Lockheed Martin\Prepar3D v4\Prepar3D.exe LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL LoadedModule[3]=C:\WINDOWS\System32\KERNELBASE.dll LoadedModule[4]=C:\WINDOWS\SYSTEM32\apphelp.dll LoadedModule[5]=C:\WINDOWS\System32\USER32.dll LoadedModule[6]=C:\WINDOWS\System32\win32u.dll LoadedModule[7]=C:\WINDOWS\System32\GDI32.dll LoadedModule[8]=C:\WINDOWS\System32\gdi32full.dll LoadedModule[9]=C:\WINDOWS\System32\msvcp_win.dll LoadedModule[10]=C:\WINDOWS\System32\ucrtbase.dll LoadedModule[11]=C:\WINDOWS\System32\ole32.dll LoadedModule[12]=C:\WINDOWS\System32\combase.dll LoadedModule[13]=C:\WINDOWS\System32\RPCRT4.dll LoadedModule[14]=C:\WINDOWS\System32\bcryptPrimitives.dll LoadedModule[15]=C:\WINDOWS\System32\sechost.dll LoadedModule[16]=C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll LoadedModule[17]=D:\Lockheed Martin\Prepar3D v4\api.dll LoadedModule[18]=C:\WINDOWS\System32\IMM32.dll LoadedModule[19]=C:\WINDOWS\SYSTEM32\Cabinet.dll LoadedModule[20]=C:\WINDOWS\SYSTEM32\MSWSOCK.dll LoadedModule[21]=C:\WINDOWS\System32\WS2_32.dll LoadedModule[22]=C:\WINDOWS\System32\CRYPT32.dll LoadedModule[23]=C:\WINDOWS\System32\MSASN1.dll LoadedModule[24]=C:\WINDOWS\SYSTEM32\WINHTTP.dll LoadedModule[25]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.17134.407_none_f94e16e330999300\COMCTL32.dll LoadedModule[26]=C:\WINDOWS\System32\ADVAPI32.dll LoadedModule[27]=C:\WINDOWS\System32\msvcrt.dll LoadedModule[28]=C:\WINDOWS\System32\SHELL32.dll LoadedModule[29]=C:\WINDOWS\SYSTEM32\WINMM.dll LoadedModule[30]=C:\WINDOWS\SYSTEM32\VERSION.dll LoadedModule[31]=C:\WINDOWS\System32\cfgmgr32.dll LoadedModule[32]=C:\WINDOWS\System32\shcore.dll LoadedModule[33]=C:\WINDOWS\System32\windows.storage.dll LoadedModule[34]=C:\WINDOWS\System32\shlwapi.dll LoadedModule[35]=C:\WINDOWS\System32\kernel.appcore.dll LoadedModule[36]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll LoadedModule[37]=C:\WINDOWS\System32\profapi.dll LoadedModule[38]=C:\WINDOWS\System32\powrprof.dll LoadedModule[39]=C:\WINDOWS\System32\FLTLIB.DLL LoadedModule[40]=D:\Lockheed Martin\Prepar3D v4\acontain.dll LoadedModule[41]=D:\Lockheed Martin\Prepar3D v4\ai_player.dll LoadedModule[42]=D:\Lockheed Martin\Prepar3D v4\atc.dll LoadedModule[43]=D:\Lockheed Martin\Prepar3D v4\controls.dll LoadedModule[44]=D:\Lockheed Martin\Prepar3D v4\demo.dll LoadedModule[45]=D:\Lockheed Martin\Prepar3D v4\DIS.dll LoadedModule[46]=C:\WINDOWS\System32\SETUPAPI.dll LoadedModule[47]=C:\WINDOWS\System32\OLEAUT32.dll LoadedModule[48]=D:\Lockheed Martin\Prepar3D v4\facilities.dll LoadedModule[49]=D:\Lockheed Martin\Prepar3D v4\fe.dll LoadedModule[50]=D:\Lockheed Martin\Prepar3D v4\flight.dll LoadedModule[51]=D:\Lockheed Martin\Prepar3D v4\fs-traffic.dll LoadedModule[52]=D:\Lockheed Martin\Prepar3D v4\g2d.dll LoadedModule[53]=D:\Lockheed Martin\Prepar3D v4\g3d.dll LoadedModule[54]=C:\WINDOWS\System32\WLDAP32.dll LoadedModule[55]=D:\Lockheed Martin\Prepar3D v4\gps.dll LoadedModule[56]=D:\Lockheed Martin\Prepar3D v4\livingwater.dll LoadedModule[57]=D:\Lockheed Martin\Prepar3D v4\main.dll LoadedModule[58]=D:\Lockheed Martin\Prepar3D v4\menus.dll LoadedModule[59]=C:\WINDOWS\System32\COMDLG32.dll LoadedModule[60]=D:\Lockheed Martin\Prepar3D v4\multiplayer.dll LoadedModule[61]=D:\Lockheed Martin\Prepar3D v4\pdk.dll LoadedModule[62]=D:\Lockheed Martin\Prepar3D v4\panels.dll LoadedModule[63]=D:\Lockheed Martin\Prepar3D v4\sim1.dll LoadedModule[64]=D:\Lockheed Martin\Prepar3D v4\simscheduler.dll LoadedModule[65]=D:\Lockheed Martin\Prepar3D v4\simprop.dll LoadedModule[66]=D:\Lockheed Martin\Prepar3D v4\sound.dll LoadedModule[67]=D:\Lockheed Martin\Prepar3D v4\symmap.dll LoadedModule[68]=D:\Lockheed Martin\Prepar3D v4\terrain.dll LoadedModule[69]=D:\Lockheed Martin\Prepar3D v4\util.dll LoadedModule[70]=D:\Lockheed Martin\Prepar3D v4\visualfx.dll LoadedModule[71]=D:\Lockheed Martin\Prepar3D v4\weather.dll LoadedModule[72]=D:\Lockheed Martin\Prepar3D v4\window.dll LoadedModule[73]=C:\WINDOWS\SYSTEM32\MSVCP140.dll LoadedModule[74]=C:\WINDOWS\SYSTEM32\CONCRT140.dll LoadedModule[75]=C:\WINDOWS\SYSTEM32\HID.DLL LoadedModule[76]=D:\Lockheed Martin\Prepar3D v4\librti1516e.dll LoadedModule[77]=C:\WINDOWS\SYSTEM32\DINPUT8.dll LoadedModule[78]=C:\WINDOWS\SYSTEM32\USERENV.dll LoadedModule[79]=C:\WINDOWS\SYSTEM32\MFReadWrite.dll LoadedModule[80]=C:\WINDOWS\SYSTEM32\MFPlat.DLL LoadedModule[81]=D:\Lockheed Martin\Prepar3D v4\mplEasyBlendSDKDX1164.dll LoadedModule[82]=C:\WINDOWS\SYSTEM32\dxgi.dll LoadedModule[83]=C:\WINDOWS\SYSTEM32\d3d11.dll LoadedModule[84]=C:\WINDOWS\SYSTEM32\OPENGL32.dll LoadedModule[85]=C:\WINDOWS\SYSTEM32\GLU32.dll LoadedModule[86]=D:\Lockheed Martin\Prepar3D v4\D3DCOMPILER_47.dll LoadedModule[87]=C:\WINDOWS\SYSTEM32\d3dx9_43.dll LoadedModule[88]=C:\WINDOWS\SYSTEM32\DSOUND.dll LoadedModule[89]=D:\Lockheed Martin\Prepar3D v4\audiere.dll LoadedModule[90]=C:\WINDOWS\SYSTEM32\MSACM32.dll LoadedModule[91]=C:\WINDOWS\SYSTEM32\MSIMG32.dll LoadedModule[92]=D:\Lockheed Martin\Prepar3D v4\libfedtime1516e.dll LoadedModule[93]=D:\Lockheed Martin\Prepar3D v4\OpenRTI.dll LoadedModule[94]=C:\WINDOWS\SYSTEM32\d3dx11_43.dll LoadedModule[95]=C:\WINDOWS\SYSTEM32\D3DCOMPILER_43.dll LoadedModule[96]=C:\WINDOWS\SYSTEM32\RTWorkQ.DLL LoadedModule[97]=D:\Lockheed Martin\Prepar3D v4\language.dll LoadedModule[98]=C:\WINDOWS\system32\uxtheme.dll LoadedModule[99]=C:\Program Files\NVIDIA Corporation\Display\NvSmartMax64.dll LoadedModule[100]=C:\WINDOWS\SYSTEM32\ntmarta.dll LoadedModule[101]=C:\WINDOWS\SYSTEM32\MSXML6.DLL LoadedModule[102]=C:\WINDOWS\SYSTEM32\inputhost.dll LoadedModule[103]=C:\WINDOWS\SYSTEM32\wintypes.dll LoadedModule[104]=C:\WINDOWS\SYSTEM32\CoreMessaging.dll LoadedModule[105]=C:\WINDOWS\SYSTEM32\CoreUIComponents.dll LoadedModule[106]=C:\WINDOWS\SYSTEM32\SspiCli.dll LoadedModule[107]=D:\Lockheed Martin\Prepar3D v4\uiInterface.dll LoadedModule[108]=C:\WINDOWS\SYSTEM32\mscoree.dll LoadedModule[109]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll LoadedModule[110]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll LoadedModule[111]=C:\WINDOWS\SYSTEM32\MSVCR120_CLR0400.dll LoadedModule[112]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\mscorlib\a6021ef6892ab519b334a17992542017\mscorlib.ni.dll LoadedModule[113]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll LoadedModule[114]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System\8ff4bf965a60a85a0598226bf67e993a\System.ni.dll LoadedModule[115]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Core\4db19b6c7622a8939b4a5629cf59c5ff\System.Core.ni.dll LoadedModule[116]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\WindowsBase\393414ebfcd8a64e2f3b267a38832ce0\WindowsBase.ni.dll LoadedModule[117]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll LoadedModule[118]=C:\WINDOWS\system32\rsaenh.dll LoadedModule[119]=C:\WINDOWS\SYSTEM32\bcrypt.dll LoadedModule[120]=C:\WINDOWS\SYSTEM32\CRYPTBASE.dll LoadedModule[121]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\PresentationCore\a5b2d65123f574f273f7a1a2920182dd\PresentationCore.ni.dll LoadedModule[122]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\Presentatio5ae0f00f#\9f0feb655b529709fff4e5130ce69f7a\PresentationFramework.ni.dll LoadedModule[123]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Xaml\cdfeba4bfc8c7fd52fbbeb81ecb25989\System.Xaml.ni.dll LoadedModule[124]=C:\WINDOWS\SYSTEM32\dwrite.dll LoadedModule[125]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\wpfgfx_v0400.dll LoadedModule[126]=C:\WINDOWS\SYSTEM32\MSVCP120_CLR0400.dll LoadedModule[127]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WPF\PresentationNative_v0400.dll LoadedModule[128]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Configuration\ed57871eb5218c20f36290299e011a90\System.Configuration.ni.dll LoadedModule[129]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Xml\96b052a0815a6699986712bec8659f0f\System.Xml.ni.dll LoadedModule[130]=C:\WINDOWS\system32\dwmapi.dll LoadedModule[131]=C:\WINDOWS\SYSTEM32\iphlpapi.dll LoadedModule[132]=C:\WINDOWS\System32\NSI.dll LoadedModule[133]=C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL LoadedModule[134]=C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL LoadedModule[135]=C:\WINDOWS\System32\MSCTF.dll LoadedModule[136]=C:\WINDOWS\SYSTEM32\secur32.dll LoadedModule[137]=C:\WINDOWS\SYSTEM32\DNSAPI.dll LoadedModule[138]=C:\WINDOWS\System32\fwpuclnt.dll LoadedModule[139]=C:\Windows\System32\rasadhlp.dll LoadedModule[140]=C:\WINDOWS\SYSTEM32\PROPSYS.dll LoadedModule[141]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Drawing\d56a87ba57efe8f63335298ab1cb8772\System.Drawing.ni.dll LoadedModule[142]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\Presentatioaec034ca#\7a5e92b3bc39396ed1e5ecc9be3ca0c6\PresentationFramework.Aero2.ni.dll LoadedModule[143]=C:\WINDOWS\SYSTEM32\urlmon.dll LoadedModule[144]=C:\WINDOWS\SYSTEM32\iertutil.dll LoadedModule[145]=C:\WINDOWS\SYSTEM32\WindowsCodecs.dll LoadedModule[146]=C:\WINDOWS\SYSTEM32\d3d9.dll LoadedModule[147]=C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_6992f55a2cc4b209\nvldumdx.dll LoadedModule[148]=C:\WINDOWS\System32\WINTRUST.DLL LoadedModule[149]=C:\WINDOWS\System32\imagehlp.dll LoadedModule[150]=C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_6992f55a2cc4b209\nvd3dumx.dll LoadedModule[151]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Windows.Forms\a8f8eef9e281ad0ac06dc269147ae72c\System.Windows.Forms.ni.dll LoadedModule[152]=C:\WINDOWS\SYSTEM32\wtsapi32.dll LoadedModule[153]=C:\WINDOWS\SYSTEM32\WINSTA.dll LoadedModule[154]=C:\WINDOWS\System32\clbcatq.dll LoadedModule[155]=C:\WINDOWS\system32\dataexchange.dll LoadedModule[156]=C:\WINDOWS\system32\dcomp.dll LoadedModule[157]=C:\WINDOWS\system32\twinapi.appcore.dll LoadedModule[158]=C:\WINDOWS\system32\RMCLIENT.dll LoadedModule[159]=C:\WINDOWS\SYSTEM32\TextInputFramework.dll LoadedModule[160]=C:\WINDOWS\system32\msctfui.dll LoadedModule[161]=C:\WINDOWS\SYSTEM32\UIAutomationCore.dll LoadedModule[162]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Runteb92aa12#\767095c34868d692c94cb37accd5bf8b\System.Runtime.Serialization.ni.dll LoadedModule[163]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.17134.407_none_2c2f90488af60bb7\gdiplus.dll LoadedModule[164]=C:\WINDOWS\SYSTEM32\DEVOBJ.dll LoadedModule[165]=C:\WINDOWS\system32\nvapi64.dll LoadedModule[166]=C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_6992f55a2cc4b209\nvwgf2umx.dll LoadedModule[167]=C:\WINDOWS\system32\nvspcap64.dll LoadedModule[168]=C:\WINDOWS\SYSTEM32\CLDAPI.dll LoadedModule[169]=C:\Windows\System32\Windows.StateRepositoryPS.dll LoadedModule[170]=C:\WINDOWS\system32\ntshrui.dll LoadedModule[171]=C:\WINDOWS\system32\srvcli.dll LoadedModule[172]=C:\WINDOWS\SYSTEM32\cscapi.dll LoadedModule[173]=C:\WINDOWS\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.17134.407_none_fb449d63306391e9\comctl32.dll LoadedModule[174]=C:\WINDOWS\system32\netutils.dll LoadedModule[175]=C:\WINDOWS\System32\coml2.dll LoadedModule[176]=C:\WINDOWS\system32\mssprxy.dll LoadedModule[177]=C:\WINDOWS\SYSTEM32\LINKINFO.dll LoadedModule[178]=C:\WINDOWS\SYSTEM32\MPR.dll LoadedModule[179]=C:\WINDOWS\System32\drprov.dll LoadedModule[180]=C:\WINDOWS\System32\ntlanman.dll LoadedModule[181]=C:\WINDOWS\System32\davclnt.dll LoadedModule[182]=C:\WINDOWS\System32\DAVHLPR.dll LoadedModule[183]=C:\WINDOWS\System32\wkscli.dll LoadedModule[184]=C:\Program Files\AVAST Software\Avast\ashShA64.dll LoadedModule[185]=C:\WINDOWS\System32\PSAPI.DLL LoadedModule[186]=C:\WINDOWS\SYSTEM32\msi.dll LoadedModule[187]=C:\Windows\System32\EhStorShell.dll LoadedModule[188]=C:\WINDOWS\system32\NetworkExplorer.dll LoadedModule[189]=C:\WINDOWS\System32\MMDevApi.dll LoadedModule[190]=C:\WINDOWS\SYSTEM32\AUDIOSES.DLL LoadedModule[191]=C:\WINDOWS\SYSTEM32\AVRT.dll LoadedModule[192]=C:\Windows\System32\Windows.UI.dll LoadedModule[193]=C:\WINDOWS\SYSTEM32\XInput9_1_0.dll LoadedModule[194]=C:\WINDOWS\SYSTEM32\wdmaud.drv LoadedModule[195]=C:\WINDOWS\SYSTEM32\ksuser.dll LoadedModule[196]=C:\WINDOWS\SYSTEM32\msacm32.drv LoadedModule[197]=C:\WINDOWS\SYSTEM32\midimap.dll LoadedModule[198]=D:\Lockheed Martin\Prepar3D v4\SimObjects\Modules\Utilities.dll LoadedModule[199]=D:\Lockheed Martin\Prepar3D v4\CIGI.dll LoadedModule[200]=D:\Lockheed Martin\Prepar3D v4\radar.dll LoadedModule[201]=D:\Lockheed Martin\Prepar3D v4\VirtualReality.dll LoadedModule[202]=D:\Lockheed Martin\Prepar3D v4\openvr_api.dll LoadedModule[203]=D:\Lockheed Martin\Prepar3D v4\ovrvision.dll LoadedModule[204]=C:\WINDOWS\SYSTEM32\OpenCL.dll LoadedModule[205]=D:\Lockheed Martin\Prepar3D v4\ControllableCamera.dll LoadedModule[206]=D:\Lockheed Martin\Prepar3D v4\Gauges\TargetInfo.dll LoadedModule[207]=D:\Lockheed Martin\Prepar3D v4\Gauges\Fury_1500.dll LoadedModule[208]=D:\Lockheed Martin\Prepar3D v4\Gauges\F-16.dll LoadedModule[209]=D:\Lockheed Martin\Prepar3D v4\SimObjects\Modules\Driver.dll LoadedModule[210]=D:\Lockheed Martin\Prepar3D v4\SimObjects\Modules\Orion MPCV.dll LoadedModule[211]=D:\Lockheed Martin\Prepar3D v4\SimObjects\Modules\SLS Block 1.dll LoadedModule[212]=D:\Lockheed Martin\Prepar3D v4\SimDirector.dll LoadedModule[213]=D:\Lockheed Martin\Prepar3D v4\PMDG\DLLs\PMDG_HUD_interface.dll LoadedModule[214]=D:\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.dll LoadedModule[215]=C:\WINDOWS\SYSTEM32\SHFolder.DLL LoadedModule[216]=D:\Lockheed Martin\Prepar3D v4\as_srv\as_connect_64.dll LoadedModule[217]=C:\WINDOWS\SYSTEM32\XInput1_4.dll LoadedModule[218]=C:\WINDOWS\system32\wbem\wbemprox.dll LoadedModule[219]=C:\WINDOWS\SYSTEM32\wbemcomn.dll LoadedModule[220]=C:\WINDOWS\system32\wbem\wbemsvc.dll LoadedModule[221]=C:\WINDOWS\system32\wbem\fastprox.dll LoadedModule[222]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_64\System.Web\7749606a3a1a5acb10698e8ce14a10a1\System.Web.ni.dll LoadedModule[223]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\webengine4.dll LoadedModule[224]=D:\Lockheed Martin\Prepar3D v4\Gauges\PMDG_737NGX.dll LoadedModule[225]=C:\WINDOWS\SYSTEM32\NETAPI32.dll LoadedModule[226]=C:\WINDOWS\system32\XAudio2_7.dll LoadedModule[227]=D:\Lockheed Martin\Prepar3D v4\Gauges\PMDG_737NGX_2.dll LoadedModule[228]=C:\WINDOWS\SYSTEM32\WINSPOOL.DRV LoadedModule[229]=C:\WINDOWS\SYSTEM32\snmpapi.dll LoadedModule[230]=C:\WINDOWS\SYSTEM32\OLEACC.dll LoadedModule[231]=C:\WINDOWS\SYSTEM32\icmp.Dll LoadedModule[232]=C:\WINDOWS\system32\napinsp.dll LoadedModule[233]=C:\WINDOWS\system32\pnrpnsp.dll LoadedModule[234]=C:\WINDOWS\system32\NLAapi.dll LoadedModule[235]=C:\WINDOWS\System32\winrnr.dll LoadedModule[236]=C:\WINDOWS\SYSTEM32\sxs.dll LoadedModule[237]=C:\Windows\System32\ieframe.dll LoadedModule[238]=C:\WINDOWS\SYSTEM32\msIso.dll LoadedModule[239]=C:\Windows\System32\mshtml.dll LoadedModule[240]=C:\Windows\System32\srpapi.dll LoadedModule[241]=C:\WINDOWS\SYSTEM32\WLDP.DLL LoadedModule[242]=C:\Windows\System32\ieapfltr.dll LoadedModule[243]=C:\Windows\System32\vaultcli.dll LoadedModule[244]=C:\WINDOWS\SYSTEM32\MLANG.dll LoadedModule[245]=C:\WINDOWS\SYSTEM32\WININET.dll LoadedModule[246]=C:\WINDOWS\SYSTEM32\msadp32.acm State[0].Key=Transport.DoneStage1 State[0].Value=1 OsInfo[0].Key=vermaj OsInfo[0].Value=10 OsInfo[1].Key=vermin OsInfo[1].Value=0 OsInfo[2].Key=verbld OsInfo[2].Value=17134 OsInfo[3].Key=ubr OsInfo[3].Value=407 OsInfo[4].Key=versp OsInfo[4].Value=0 OsInfo[5].Key=arch OsInfo[5].Value=9 OsInfo[6].Key=lcid OsInfo[6].Value=1033 OsInfo[7].Key=geoid OsInfo[7].Value=244 OsInfo[8].Key=sku OsInfo[8].Value=101 OsInfo[9].Key=domain OsInfo[9].Value=0 OsInfo[10].Key=prodsuite OsInfo[10].Value=768 OsInfo[11].Key=ntprodtype OsInfo[11].Value=1 OsInfo[12].Key=platid OsInfo[12].Value=10 OsInfo[13].Key=sr OsInfo[13].Value=0 OsInfo[14].Key=tmsi OsInfo[14].Value=240557 OsInfo[15].Key=osinsty OsInfo[15].Value=3 OsInfo[16].Key=iever OsInfo[16].Value=11.407.17134.0-11.0.95 OsInfo[17].Key=portos OsInfo[17].Value=0 OsInfo[18].Key=ram OsInfo[18].Value=16334 OsInfo[19].Key=svolsz OsInfo[19].Value=239 OsInfo[20].Key=wimbt OsInfo[20].Value=0 OsInfo[21].Key=blddt OsInfo[21].Value=180410 OsInfo[22].Key=bldtm OsInfo[22].Value=1804 OsInfo[23].Key=bldbrch OsInfo[23].Value=rs4_release OsInfo[24].Key=bldchk OsInfo[24].Value=0 OsInfo[25].Key=wpvermaj OsInfo[25].Value=0 OsInfo[26].Key=wpvermin OsInfo[26].Value=0 OsInfo[27].Key=wpbuildmaj OsInfo[27].Value=0 OsInfo[28].Key=wpbuildmin OsInfo[28].Value=0 OsInfo[29].Key=osver OsInfo[29].Value=10.0.17134.407.amd64fre.rs4_release.180410-1804 OsInfo[30].Key=buildflightid OsInfo[30].Value=7B3F085B-AF94-4576-9A9C-9A5E41CD1FC9.1 OsInfo[31].Key=edition OsInfo[31].Value=Core OsInfo[32].Key=ring OsInfo[32].Value=Retail OsInfo[33].Key=expid OsInfo[33].Value=RS:17A7 OsInfo[34].Key=containerid OsInfo[35].Key=containertype OsInfo[36].Key=edu OsInfo[36].Value=0 FriendlyEventName=Stopped working ConsentKey=BEX64 AppName=Prepar3D exe AppPath=D:\Lockheed Martin\Prepar3D v4\Prepar3D.exe NsPartner=windows NsGroup=windows8 ApplicationIdentity=DED48A47CD06CBA637AF1CD9393BD4FC MetadataHash=-721547041
  13. Hi Folks - well it looks like Rob was on the right track re panel states. I performed a number of test cases flying to TNCM as well as 4 other destinations using both the default and 777 Long panel states. In most cases, the brake overheating issue occurred only at TNCM and only when I loaded the 777 Long panel state. There were no issues when I loaded the default panel state and flew to TNCM. I fed the test results to PMDG and this was their response: "John I suspect this is one of the issues we discovered with the saved panel state files. There was a problem with the release version of the 777 that caused a lot of strange behaviour with saved panel states but it has been corrected for the upcoming SP1 update. Hopefully that will be released shortly. Let me know if you see this issue again after the SP1 update."
  14. Well it looks like something's wrong with the simulation at my end. Just tried landings at three different airports - Toronto (CYYZ), New York (KJFK) and Ft Lauderdale (KFLL). In all cases, the approach config was the same (Autobrakes 2; Flaps 30; Spoilers armed and Autothrottle armed with speed set at 140. In all cases, I had the Gear screen displayed so I could check the brake temps - After landing, disengaged reverse thrust at 50 kts. Nothing out the ordinary guys - the highest brake temp was 0.8! Went back and tried the landing at St Maarten and you guessed it - brake temp reaching around 7.0 before I shut it down. Looks like I'll have to check it out with PDMG.
×
×
  • Create New...