hilkiah

717 Tester
  • Content count

    63
  • Joined

  • Last visited

Community Reputation

7 Neutral

2 Followers

Recent Profile Visitors

523 profile views
  1. First flight with latest update (1.0.9.27) . Imported flight plan from simbrief, however there seems to be a problem with the flight plan display of the font (see link). Here is the flight plan: EGLL/27R BPK7F BPK Q295 CLN UL620 REDFA REDF1A EHAM/27
  2. hilkiah

    Problems with fmc.

    ANd yes I had AS runnning (can’t recall wind conditions) but it was a fairly smooth landing.
  3. hilkiah

    Problems with fmc.

    Not wanting to hijack your thread, but I had a similar weird fmc behaviour on the following flight flight (generated and uploaded from simbrief): LDPL/09 RJK2C RJK T742 KOTOR DCT VEBAL DCT BABIT DCT ETIDA Q27 GRN N605 TOTKA TOTK3F LBWN/27 I had the same 90 degree looking lines extended to infinity. Also had some weird circular lines and some 'indecision' on the part of the fmc. I am running v1.0.9.24 (downloaded tfdi addon manager update before flight). I have uploaded a few stills of the mcdu as well as the expected flight path according to Pilot2ATC.
  4. hilkiah

    Still Getting CTD with P3D 4.2 Update

    Out of curiosity, were you using time acceleration ? (R+)
  5. hilkiah

    Still Getting CTD with P3D 4.2 Update

    Yeah same thing that happened to me....switching back from cinematic mode to VC.
  6. Collin, I doubt I can make it crash at the same point, but somewhere during the flight there is a high chance it'll crash. From a programmer point of view, what useful information should we provide about the crash and where can we get those from? The CTD with view switching is pretty old (pre-4.1 probably). Was really hoping that 4.2 wold have solved this, but my last few flights with the 717 all ended in a CTD. Note I was running CP and AS at the time.
  7. I just had a CTD (changing back from chaseplane cinematic mode). My event logs has a 6 entries that pertain to the crash. I am enclosing them here @turbofandude 1) Log Name: Application Source: ESENT Date: 3/14/2018 4:27:34 PM Event ID: 916 Task Category: General Level: Information Keywords: Classic User: N/A Computer: hilkiahpc Description: DllHost (9920,G,0) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="ESENT" /> <EventID Qualifiers="0">916</EventID> <Level>4</Level> <Task>1</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2018-03-14T20:27:34.561041100Z" /> <EventRecordID>28691</EventRecordID> <Channel>Application</Channel> <Computer>hilkiahpc</Computer> <Security /> </System> <EventData> <Data>DllHost</Data> <Data>9920,G,0</Data> <Data> </Data> <Data>EseDiskFlushConsistency</Data> <Data>ESENT</Data> <Data>0x800000</Data> </EventData> </Event> 2) Log Name: Application Source: Windows Error Reporting Date: 3/14/2018 4:26:46 PM Event ID: 1001 Task Category: None Level: Information Keywords: Classic User: N/A Computer: hilkiahpc Description: Fault bucket 1224744385034509663, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Prepar3D.exe P2: 4.2.21.24048 P3: 5a7c832c P4: KERNELBASE.dll P5: 10.0.16299.309 P6: 90a96867 P7: c000041d P8: 0000000000014008 P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDE6F.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE93F.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE94F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE95F.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_d988d51e8b75f9c3cfd1a3157798ffe356794b_00292455_62e0ed92 Analysis symbol: Rechecking for solution: 0 Report Id: 4b2eb842-6663-4c9e-a5de-01851f0514b4 Report Status: 268435456 Hashed bucket: 81eeb371a78b06a460ff2a877aa2dd5f Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Windows Error Reporting" /> <EventID Qualifiers="0">1001</EventID> <Level>4</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2018-03-14T20:26:46.879565900Z" /> <EventRecordID>28690</EventRecordID> <Channel>Application</Channel> <Computer>hilkiahpc</Computer> <Security /> </System> <EventData> <Data>1224744385034509663</Data> <Data>4</Data> <Data>APPCRASH</Data> <Data>Not available</Data> <Data>0</Data> <Data>Prepar3D.exe</Data> <Data>4.2.21.24048</Data> <Data>5a7c832c</Data> <Data>KERNELBASE.dll</Data> <Data>10.0.16299.309</Data> <Data>90a96867</Data> <Data>c000041d</Data> <Data>0000000000014008</Data> <Data> </Data> <Data> </Data> <Data> \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERDE6F.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE93F.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE94F.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERE95F.tmp.txt</Data> <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_d988d51e8b75f9c3cfd1a3157798ffe356794b_00292455_62e0ed92</Data> <Data> </Data> <Data>0</Data> <Data>4b2eb842-6663-4c9e-a5de-01851f0514b4</Data> <Data>268435456</Data> <Data>81eeb371a78b06a460ff2a877aa2dd5f</Data> </EventData> </Event> 3) Log Name: Application Source: Application Error Date: 3/14/2018 4:26:42 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: hilkiahpc Description: Faulting application name: Prepar3D.exe, version: 4.2.21.24048, time stamp: 0x5a7c832c Faulting module name: KERNELBASE.dll, version: 10.0.16299.309, time stamp: 0x90a96867 Exception code: 0xc000041d Fault offset: 0x0000000000014008 Faulting process id: 0x4c10 Faulting application start time: 0x01d3bbcbb63a3bff Faulting application path: P:\Prepar3D v4\Prepar3D.exe Faulting module path: C:\Windows\System32\KERNELBASE.dll Report Id: 4b2eb842-6663-4c9e-a5de-01851f0514b4 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2018-03-14T20:26:42.851935300Z" /> <EventRecordID>28689</EventRecordID> <Channel>Application</Channel> <Computer>hilkiahpc</Computer> <Security /> </System> <EventData> <Data>Prepar3D.exe</Data> <Data>4.2.21.24048</Data> <Data>5a7c832c</Data> <Data>KERNELBASE.dll</Data> <Data>10.0.16299.309</Data> <Data>90a96867</Data> <Data>c000041d</Data> <Data>0000000000014008</Data> <Data>4c10</Data> <Data>01d3bbcbb63a3bff</Data> <Data>P:\Prepar3D v4\Prepar3D.exe</Data> <Data>C:\Windows\System32\KERNELBASE.dll</Data> <Data>4b2eb842-6663-4c9e-a5de-01851f0514b4</Data> <Data> </Data> <Data> </Data> </EventData> </Event> 4) Log Name: Application Source: Windows Error Reporting Date: 3/14/2018 4:26:35 PM Event ID: 1001 Task Category: None Level: Information Keywords: Classic User: N/A Computer: hilkiahpc Description: Fault bucket 1392826489021623753, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Prepar3D.exe P2: 4.2.21.24048 P3: 5a7c832c P4: KERNELBASE.dll P5: 10.0.16299.309 P6: 90a96867 P7: c0020001 P8: 0000000000014008 P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA52F.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB29F.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB29D.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB2AD.tmp.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_eb1b543f9025e96761247d1dad37a965d9e74582_00292455_6a24c058 Analysis symbol: Rechecking for solution: 0 Report Id: 7623b501-a00b-4e6f-9771-454215d8d12d Report Status: 268435456 Hashed bucket: b9e6f19d4a3767945354504fefe36dc9 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Windows Error Reporting" /> <EventID Qualifiers="0">1001</EventID> <Level>4</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2018-03-14T20:26:35.303281700Z" /> <EventRecordID>28688</EventRecordID> <Channel>Application</Channel> <Computer>hilkiahpc</Computer> <Security /> </System> <EventData> <Data>1392826489021623753</Data> <Data>4</Data> <Data>APPCRASH</Data> <Data>Not available</Data> <Data>0</Data> <Data>Prepar3D.exe</Data> <Data>4.2.21.24048</Data> <Data>5a7c832c</Data> <Data>KERNELBASE.dll</Data> <Data>10.0.16299.309</Data> <Data>90a96867</Data> <Data>c0020001</Data> <Data>0000000000014008</Data> <Data> </Data> <Data> </Data> <Data> \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA52F.tmp.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB29F.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB29D.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERB2AD.tmp.txt</Data> <Data>C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_eb1b543f9025e96761247d1dad37a965d9e74582_00292455_6a24c058</Data> <Data> </Data> <Data>0</Data> <Data>7623b501-a00b-4e6f-9771-454215d8d12d</Data> <Data>268435456</Data> <Data>b9e6f19d4a3767945354504fefe36dc9</Data> </EventData> </Event> 5) Log Name: Application Source: Application Error Date: 3/14/2018 4:26:28 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: hilkiahpc Description: Faulting application name: Prepar3D.exe, version: 4.2.21.24048, time stamp: 0x5a7c832c Faulting module name: KERNELBASE.dll, version: 10.0.16299.309, time stamp: 0x90a96867 Exception code: 0xc0020001 Fault offset: 0x0000000000014008 Faulting process id: 0x4c10 Faulting application start time: 0x01d3bbcbb63a3bff Faulting application path: P:\Prepar3D v4\Prepar3D.exe Faulting module path: C:\Windows\System32\KERNELBASE.dll Report Id: 7623b501-a00b-4e6f-9771-454215d8d12d Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2018-03-14T20:26:28.165660500Z" /> <EventRecordID>28687</EventRecordID> <Channel>Application</Channel> <Computer>hilkiahpc</Computer> <Security /> </System> <EventData> <Data>Prepar3D.exe</Data> <Data>4.2.21.24048</Data> <Data>5a7c832c</Data> <Data>KERNELBASE.dll</Data> <Data>10.0.16299.309</Data> <Data>90a96867</Data> <Data>c0020001</Data> <Data>0000000000014008</Data> <Data>4c10</Data> <Data>01d3bbcbb63a3bff</Data> <Data>P:\Prepar3D v4\Prepar3D.exe</Data> <Data>C:\Windows\System32\KERNELBASE.dll</Data> <Data>7623b501-a00b-4e6f-9771-454215d8d12d</Data> <Data> </Data> <Data> </Data> </EventData> </Event> 6) Log Name: Application Source: .NET Runtime Date: 3/14/2018 4:26:27 PM Event ID: 1026 Task Category: None Level: Error Keywords: Classic User: N/A Computer: hilkiahpc Description: Application: Prepar3D.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0020001, exception address 00007FFEB8744008 Stack: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name=".NET Runtime" /> <EventID Qualifiers="0">1026</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2018-03-14T20:26:27.393523000Z" /> <EventRecordID>28686</EventRecordID> <Channel>Application</Channel> <Computer>hilkiahpc</Computer> <Security /> </System> <EventData> <Data>Application: Prepar3D.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0020001, exception address 00007FFEB8744008 Stack: </Data> </EventData> </Event> WER31DD.tmp.WERInternalMetadata.xml
  8. hilkiah

    Still Getting CTD with P3D 4.2 Update

    I got a CTD last evening during cruise and after switching. Can anyone advise whether the CTDs happen with EzDok? I’m willing to give it a try but wouldn’t if the same CTDs occurs.
  9. NO!!!! I have 4.2 and I just completed 3 flights with the 717 and plenty of chaseplane view switching (external + internal + cinematic). Also using 2x time compression in cruise. Prior to 4.2 (i.e. with 4.1) it was almost guaranteed that P3D would CTD when switching views. Right now I'm actually abusing the view switching trying to get the sim to CTD...but nothing. For me the 717 with v4.2 is solid as a rock!!
  10. hilkiah

    Is the 717 P3D4.2 compatible?

    And I just experienced True glass rain effects on final to LEBB...damn that was cool!!
  11. hilkiah

    Is the 717 P3D4.2 compatible?

    I just did another fantastic flight...no CTD with loadsssssss of switching (chaseplane external view, + cinematic mode + internal views). I had 2x time compression enabled (during cruise), used PROF to descend and then v/s mode. Honestly I am getting excited again about the 717 now that p3d 4.2 seemed to have cured the CTD when switching views.
  12. hilkiah

    PFPX

    Navigator, are you looking for a PFPX profile for the 717? If so see:
  13. hilkiah

    Will P3Dv4.2 fix some of the 717 issues?

    Very excited to post this!! I'm now on v4.2 like most others. When I read Joshua's post that he switched 500 times without a crash, I was honestly skeptical. Anyway I decided to bring my KLM citihopper out of the hanger to take her for a quick spin from EGLL to LFPG. Went through the checklist to get the rust out of my head and flew her successfully without a CTD!!!! More importantly I was switching like crazy trying to see if Joshua was correct. This is something I could NOT have done with v4.1 (CTD would have been guaranteed). I am going to now fly from here to LEBB or LEVC and then return to EGKK to see, but so far so good, NO MORE CTD FROM VIEW SWITCHING. Now all I need are more liveries for my 717.
  14. hilkiah

    CTD when going back to cockpit

    Yeah I'm really looking forward to this fix..cause just like you guys I can't help but peek (actually enable chaseplane cinematic mode).
  15. hilkiah

    unable to download add-on manager

    Hi Patco, I was able to download the addon and then install/update to latest version. I can't say that I did anything different, it just started working again. Not sure if tfdi did anything on their end tbh.