February 7, 20179 yr Hello I was checking my Route on the LEGS Page in the FMC via Step Button, EFIS was on PLN and Range 10, and while i chlicking throu the Waypoints a n reproducible CTD happens. First CTD Error Message EventData fsx.exe 10.0.61637.0 46fadb14 PMDG_747QOTSII.DLL 1.0.0.0 5890e257 c0000409 002fe9da 36dc 01d2818f2b5aa2f0 D:\FSX\fsx.exe D:\FSX\GAUGES\PMDG_747QOTSII.DLL 8fb1afe1-87e4-45f4-a626-2fa0297b94e5 2nd (detail) CTD Error Message Protokollname: Application Quelle: Application Error Datum: 08.02.2017 00:05:54 Ereignis-ID: 1000 Aufgabenkategorie:(100) Ebene: Fehler Schlüsselwörter:Klassisch Benutzer: Nicht zutreffend Computer: Simon-PC Beschreibung: Name der fehlerhaften Anwendung: fsx.exe, Version: 10.0.61637.0, Zeitstempel: 0x46fadb14 Name des fehlerhaften Moduls: PMDG_747QOTSII.DLL, Version: 1.0.0.0, Zeitstempel: 0x5890e257 Ausnahmecode: 0xc0000409 Fehleroffset: 0x002fe9da ID des fehlerhaften Prozesses: 0x3454 Startzeit der fehlerhaften Anwendung: 0x01d2819572aebd54 Pfad der fehlerhaften Anwendung: D:\FSX\fsx.exe Pfad des fehlerhaften Moduls: D:\FSX\GAUGES\PMDG_747QOTSII.DLL Berichtskennung: 5664ade2-d0e7-458d-9372-68abde9bacee Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist: Ereignis-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="2017-02-07T23:05:54.641522200Z" /> <EventRecordID>1399845</EventRecordID> <Channel>Application</Channel> <Computer>Simon-PC</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61637.0</Data> <Data>46fadb14</Data> <Data>PMDG_747QOTSII.DLL</Data> <Data>1.0.0.0</Data> <Data>5890e257</Data> <Data>c0000409</Data> <Data>002fe9da</Data> <Data>3454</Data> <Data>01d2819572aebd54</Data> <Data>D:\FSX\fsx.exe</Data> <Data>D:\FSX\GAUGES\PMDG_747QOTSII.DLL</Data> <Data>5664ade2-d0e7-458d-9372-68abde9bacee</Data> <Data> </Data> <Data> </Data> </EventData> </Event> Do you need more information? Greez Simon Keller reproducible Greez Simon Keller
February 7, 20179 yr Was there a fix made of coordinates? If so, did you import a fpl from simbrief? Have a look here: http://www.avsim.com/topic/503733-747-v3-crash-when-using-pbd/ Fabrizio Barbierato
February 7, 20179 yr FYI Done this several times with no problems at all. Win7 64 Prof FSX:SE Per W Sweden Programmer since 30+ years (now retired) and a avid flightsimmer since SubLogic on Vic64. Now I enjoy XP 12.1.3r2 and Scenery fixing. Also did some real pilot training back in 1979-80. Win10 Pro, i5-11600K, Water Cooling, ASUS MB 32GB, nVidia 4060Ti 16 GB, 27" ASUS TUF Gaming VG27AQZ 2560x1440 monitor, 2 NVMe drives + 4 SSDs and 1 HDD for downloads/storage. Honeycomb Yoke + throttle and MFG Crosswind rudders. I always build my PCs myself so I know what is inside them.
February 7, 20179 yr Commercial Member I was checking my Route on the LEGS Page in the FMC via Step Button, EFIS was on PLN and Range 10, and while i chlicking throu the Waypoints a nreproducible CTD happens. I'm guessing you loaded a route from an external route planner? Kyle Rodgers
February 8, 20179 yr Author The Route, VHHH-WSSS, was created by simbrief: ATEN2A BEKOL A461 IDUMA W501 KEVAR W509 NLG W18 TAMOT B330 CH L642 ENREP N891 OBDAB But i made no change on the Route himself. No Fix entered, simply the Runway and SID on the FMC. Then flowing throu the Steps until the CTD happens. Greez Simon Keller
February 8, 20179 yr nav data issues? whats your nav data and from where I7-8700k,Corsair h1101 cooler ,Asus Strix Gaming Intel Z370 S11 motherboard, Corsair 32gb ramDD4,, gtx 1080ti Card, RM850 power supply Peter kelberg
February 8, 20179 yr Commercial Member So SimBrief is adding something into the file that is causing an issue. Try it without loading the file (manually enter the route on the RTE pages). I have a feeling it won't crash. Kyle Rodgers
February 8, 20179 yr Commercial Member SImbrief is adding too long waypoint names, beyond PMDG flightplan specs. As I responded in the other thread the problem is now solved (by adding protection) and there is just a little wait for the next update. ==================================== E M V Precision Manuals Development Group ====================================
Archived
This topic is now archived and is closed to further replies.