Maddog X V5 CTD GSX

[micstatic 4,319]

So Flight 2 and Flight 3 for me with the maddog in V5 have both CTD.  First CTD was when calling for pushback with GSX.  This one was when using the mechanics panel to disconnect ground power.  Has anybody else had problems like this?

 

 

Log Name:      Application
Source:        Application Error
Date:          5/24/2020 7:15:38 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DG-9700k
Description:
Faulting application name: Prepar3D.exe, version: 5.0.24.34874, time stamp: 0x5eab3677
Faulting module name: maddog.dll, version: 1.6.0.571, time stamp: 0x5ebe8cc5
Exception code: 0xc0000005
Fault offset: 0x00000000002ac283
Faulting process id: 0x30fc
Faulting application start time: 0x01d63218d557c653
Faulting application path: D:\Lockheed Martin\Prepar3D v5\Prepar3D.exe
Faulting module path: C:\Users\David Gray\Documents\Prepar3D v5 Add-ons\MaddogX\SimObjects\Airplanes\MaddogX83\panel\maddog.dll
Report Id: 56357beb-6f1d-4d6e-93ec-50885b9d6316
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="2020-05-24T23:15:38.526458700Z" />
    <EventRecordID>44670</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DG-9700k</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>5.0.24.34874</Data>
    <Data>5eab3677</Data>
    <Data>maddog.dll</Data>
    <Data>1.6.0.571</Data>
    <Data>5ebe8cc5</Data>
    <Data>c0000005</Data>
    <Data>00000000002ac283</Data>
    <Data>30fc</Data>
    <Data>01d63218d557c653</Data>
    <Data>D:\Lockheed Martin\Prepar3D v5\Prepar3D.exe</Data>
    <Data>C:\Users\David Gray\Documents\Prepar3D v5 Add-ons\MaddogX\SimObjects\Airplanes\MaddogX83\panel\maddog.dll</Data>
    <Data>56357beb-6f1d-4d6e-93ec-50885b9d6316</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

[micstatic 4,319]

just got another CTD.  This time a kernalbase one.  I was at cruise.  VRAM not pushing the limit at all.  Clicked acars and attempted to get an arrival ATIS for LAX.  Right when I clicked send it CTD'd

[snapshot21 254]

I had a GSX CTD like that once while calling for pushback but with the PMDG 747. Run FSDT and I no longer encountered it.

With the acars one, I advise posting it directly to their support forum, you will get better visibility from the devs there regarding issues with the plane.

[Daniel M 8]

I've had multiple CTD's with the QW 787 when calling GSX. Seems like GSX is the common theme for all of us.

[cwburnett 1,809]

1 hour ago, micstatic said:

just got another CTD.  This time a kernalbase one.  I was at cruise.  VRAM not pushing the limit at all.  Clicked acars and attempted to get an arrival ATIS for LAX.  Right when I clicked send it CTD'd

I just got this one an hour ago. Click ACARS and kernelbase CTD. Sent me back to the FSW F50.

Surprisingly the only v5 native airliner that isn't causing me trouble is the AS A330. The v4 version of the Q400 is safe also for me.

I have sadly parked my beloved Maddog until hf2 is out.

[micstatic 4,319]

i reported this via ticket to Maddog.  Will see what they say.  Right now the maddog is almost unflyable for me.  In V5.  The PMDG 747 has been very stable.  Not a single CTD.  787 has also been good for me.  

[fltent1184 4]

2 hours ago, micstatic said:

just got another CTD.  This time a kernalbase one.  I was at cruise.  VRAM not pushing the limit at all.  Clicked acars and attempted to get an arrival ATIS for LAX.  Right when I clicked send it CTD'd

Are using latest beta of ASP3D (7448)? If yes, there is an issue with retrieving the ATIS (it's not clear if it is related to another bug in ASP3D where the active runway cannot be determined. This was related to reading P3Dv5 scenery & in build 7448 they moved to using Navigraph data. Unfortunately it is still broken & they are looking into it. Check HiFi forums for issues).

Also, if you are using ASP3D 7448, try disabling EA when using Maddog X. It helped to a certain extent to solve the CTD problem with latest beta of ASP3D.

[micstatic 4,319]

thanks.  Yes using 7448