CTD with 1.6.4 in Taxi2Gate EDDM SimObjectAnimationModule64.dll

Home Forums Support CTD with 1.6.4 in Taxi2Gate EDDM SimObjectAnimationModule64.dll

This topic contains 8 replies, has 4 voices, and was last updated by  Eamonn_Jawhary 1 month ago.

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • #3182

    Urmel81
    Participant

    Hello,

    I get sometimes a CTD in EDDM. (SimObjectAnimationModule64.dll)

    That’s from AppCrashView:

    Version=1
    EventType=APPCRASH
    EventTime=131910918530397730
    ReportType=2
    Consent=1
    UploadTime=131910918539297180
    ReportStatus=268435456
    ReportIdentifier=6cef7eed-a66d-4b4d-88bd-d065a51a24b4
    IntegratorReportIdentifier=b3c8bf32-ebda-409b-bbd2-dc3a5d74cacf
    Wow64Host=34404
    NsAppName=Prepar3D.exe
    OriginalFilename=Prepar3D.exe
    AppSessionGuid=00002748-0004-0010-e739-ee5946a4d401
    TargetAppId=W:00000fd8e1548ddc258b3ce94ed3d6130ca000000904!0000f4a6d227777f5de7b2e85c3afb498a6b55cc49a0!Prepar3D.exe
    TargetAppVer=2018//11//27:21:46:29!2d2651!Prepar3D.exe
    BootId=4294967295
    TargetAsId=2934
    UserImpactVector=269497136
    IsFatal=1
    EtwNonCollectReason=1
    Response.BucketId=90800eef7df37e37f8e4f49c470232b3
    Response.BucketTable=4
    Response.LegacyBucketId=1793827503643701939
    Response.type=4
    Sig[0].Name=Anwendungsname
    Sig[0].Value=Prepar3D.exe
    Sig[1].Name=Anwendungsversion
    Sig[1].Value=4.4.16.27077
    Sig[2].Name=Anwendungszeitstempel
    Sig[2].Value=5bfdbb35
    Sig[3].Name=Fehlermodulname
    Sig[3].Value=SimObjectAnimationModule64.dll
    Sig[4].Name=Fehlermodulversion
    Sig[4].Value=1.6.4.0
    Sig[5].Name=Fehlermodulzeitstempel
    Sig[5].Value=5c100d52
    Sig[6].Name=Ausnahmecode
    Sig[6].Value=c0000005
    Sig[7].Name=Ausnahmeoffset
    Sig[7].Value=000000000000dc78

     

    That’s from SODE.log:

    [17:10:35.530] INFO SODE.FSLOOP :  + SimObject Taxi2Gate_EDDM_Stands:Terminal 1 Gate 143 [Taxi2gate_EDDM_Jetway_T1_BS]. ID: 690
    [17:10:35.530] INFO SODE.FSLOOP :  + SimObject Taxi2Gate_EDDM_Stands:Terminal 1 Gate 142 [Taxi2gate_EDDM_Jetway_T1_BS]. ID: 691
    [17:10:35.740] INFO SODE.FSLOOP : SeasonalObjectHandler: Variables initialized!
    [17:10:39.946] INFO SODE.FSLOOP : SeasonalObjectHandler: Refreshing Season/Time Data…
    [17:10:40.558] DEBUG SODE.FSLOOP : [AI DETECTION] N monitored AIObjects = 0
    [17:10:42.165] WARN SODE.FSLOOP : [AI DETECTION] Jetway Terminal 2 Gate 217 cannot be docked to AI=A320 D-AIUT [IKErrCode=1]
    [17:10:44.195] DEBUG SODE.FSLOOP : [AI DETECTION] N monitored AIObjects = 66
    [17:10:48.141] DEBUG SODE.FSLOOP : [AI DETECTION] N monitored AIObjects = 66
    [17:10:50.125] INFO SODE.FSLOOP : SeasonalObjectHandler: Refreshing Season/Time Data…
    [17:11:02.015] FATAL SODE.WATCHDOG : Sim Process running test failed!
    [17:11:02.017] DEBUG SODE.FSPROCESS : Cleaning up Memory…
    [17:11:02.045] DEBUG SODE.FSPROCESS : Removing Top-Menu structure…
    [17:11:02.045] DEBUG SODE.FSPROCESS : Closing Connection to FS.
    [17:11:02.146] INFO  : Terminate SODE.

    Without SODE 1.6.4 (I delete the EDDM.xml from the XML Folder): No Crash.

    Any Idea?

    This happens with every aircraft (like a small PA38, or a PMDG 737, or default aircraft)

     

    Thanks Urmel

     

     

    #3194

    12bPilot
    Keymaster

    Hi,

    Thanks for the report. There was an other report with the same issue: https://sode.12bpilot.ch/?topic=sode-module-fault.

    Until I can recreate the issue here, I won’t be able to provide a fix. It surely has to do something with the AI jetway docking animation, since the jetway animation part is the only thing that could crash the sim.

    Disabling the AI detection feature should also fix this problem temporarily.

    So cross your fingers that I can crash my sim eventually 😉

    By the way, what AI package are you using? UTL?

    Best regards

    #3214

    Harry320
    Participant

    Hi,

    same issue here,

    when I’m in the outside view and try to turn the view around my plane P3D4.4 crashed immediately.

    I don’t know if this message has anything to do with it.

    Fehler bei der Profilbenachrichtigung des Ereignisses Load für Komponente {B31118B2-1F49-48E5-B6F5-BC21CAEC56FB}. Fehlercode: See Tracelogging for error details.

     

    Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 4.4.16.27077, Zeitstempel: 0x5bfdbb35
    Name des fehlerhaften Moduls: SimObjectAnimationModule64.dll, Version: 1.6.4.0, Zeitstempel: 0x5c100d52
    Ausnahmecode: 0xc0000005
    Fehleroffset: 0x000000000000dc78
    ID des fehlerhaften Prozesses: 0x780
    Startzeit der fehlerhaften Anwendung: 0x01d4a73349204e79
    Pfad der fehlerhaften Anwendung: D:\Prepar3D_V4\Prepar3D.exe
    Pfad des fehlerhaften Moduls: C:\Program Files (x86)\12bPilot\SODE\SimObjectAnimationModule64.dll
    Berichtskennung: 4dbf0783-9b9d-42e3-bad8-77c2e9d4cbae
    Vollständiger Name des fehlerhaften Pakets:
    Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

    Best regards

    Harald

     

     

    • This reply was modified 6 months, 2 weeks ago by  Harry320.
    #3216

    12bPilot
    Keymaster

    Hi guys,

    The dll crashes when calling a SimConnect function. However, I can’t determine which function is affected, so I need your help here (still can’t reproduce the crash).

    Could you run Prepar3D.exe with logging the simconnect server communications? Instructions on how to generate such simconnect.log files can be found in the FAQ, Section D https://sode.12bpilot.ch/?topic=faq

    When you face another CTD with SODE as the faulting module, navigate to your simconnect.log file and upload it here. I may be able to trace then which SimConnect call is causing issues.

    Thanks.

    -Jeffrey

    #3217

    Harry320
    Participant

    hello Jeffrey,

    thanks for your help,

    tried it today again and call it Vorführeffekt.

    No Crash at EDDM !

    Since version 1.64, SimObjectAnimationModule constantly crashed in EDDM if I was in the outside view

    and i’m spinning around my plane.

    I think i need futher tests.

    Please have a look at my Simmconnect.log

    Best regards,

    Harald

     

     

     

     

     

    Attachments:
    You must be logged in to view attached files.
    #3219

    Urmel81
    Participant

    Hi, Thanks for the report. There was an other report with the same issue: https://sode.12bpilot.ch/?topic=sode-module-fault. Until I can recreate the issue here, I won’t be able to provide a fix. It surely has to do something with the AI jetway docking animation, since the jetway animation part is the only thing that could crash the sim. Disabling the AI detection feature should also fix this problem temporarily. So cross your fingers that I can crash my sim eventually  By the way, what AI package are you using? UTL? Best regards

     

    Hello, no, I use custom AI. I made another test. I moved every xml file out of the sode folder and startet only with EDDM. It works. I decided to do it this way, because I get two other CTD with the SimObjectAnimationModule64.dll.

    Both inflight, one in the LOWW area and one on approach to LRIA.

    I was on the way from EDDM to LRIA (Flight over LOWW).

     

    • This reply was modified 6 months, 1 week ago by  Urmel81.
    #3249

    12bPilot
    Keymaster

    I was able to find the cause of the crash. There were timing issues between the SODE EXE and DLL and corrupted data was read in the DLL and processed, which resulted in a crash in the animation loop.

    The timing sensitive nature of this EXE to DLL data transmission was always SODE’s weak point concerning the AI detection loop.

    I have now redesigned this data transmission to be independent of timing, but relying on handshake signals between EXE and DLL, ensuring proper reception of the data on the DLL end. Initial tests are successful and I am confident that this eliminates this crash and makes SODE’s AI engine more robust.

    Best regards

    #3303

    Urmel81
    Participant

    I was able to find the cause of the crash. There were timing issues between the SODE EXE and DLL and corrupted data was read in the DLL and processed, which resulted in a crash in the animation loop. The timing sensitive nature of this EXE to DLL data transmission was always SODE’s weak point concerning the AI detection loop. I have now redesigned this data transmission to be independent of timing, but relying on handshake signals between EXE and DLL, ensuring proper reception of the data on the DLL end. Initial tests are successful and I am confident that this eliminates this crash and makes SODE’s AI engine more robust. Best regards

     

    Hello,

    nice to hear. An Update is coming?

    Today I had another CTD in WSSS.

     

    Thanks Urmel

    #3391

    Eamonn_Jawhary
    Participant

    Every once in a while a get a CTD on pushback. last time was the other day at Taxi2gate KSEA. I don’t have AIDetection enabled.

    [General]
    WatchdogEnable=False
    SecondaryTextMenuHotkey=NONE
    DebugMode=False
    SoundEngineDisable=False
    [JetwaySystem]
    JetwaySoundEnable=True
    ForceHorizontalJetwayForRotation=True
    AircraftStateTriggeredAutoDockingEnable=False
    [AISystem]
    DetectionEnable=False
    JetwaySoundEnable=False

    <span class=”m”><</span><span class=”t”>Event</span><span class=”ns”> xmlns</span><span class=”m”>=”</span><b class=”ns”>http://schemas.microsoft.com/win/2004/08/events/event</b><span class=”m”>”</span><span class=”m”>></span>
    <span class=”m”><</span><span class=”t”>System</span><span class=”m”>></span>
    <span class=”m”><</span><span class=”t”>Provider</span> <span class=”t”>Name</span><span class=”m”>=”</span><b>Application Error</b><span class=”m”>”</span><span class=”m”> /></span>
    <span class=”m”><</span><span class=”t”>EventID</span><span class=”t”> Qualifiers</span><span class=”m”>=”</span><b>0</b><span class=”m”>”</span><span class=”m”>></span><span class=”tx”>1000</span><span class=”m”></</span><span class=”t”>EventID</span><span class=”m”>></span>
    <span class=”m”><</span><span class=”t”>Level</span><span class=”m”>></span><span class=”tx”>2</span><span class=”m”></</span><span class=”t”>Level</span><span class=”m”>></span>
    <span class=”m”><</span><span class=”t”>Task</span><span class=”m”>></span><span class=”tx”>100</span><span class=”m”></</span><span class=”t”>Task</span><span class=”m”>></span>
    <span class=”m”><</span><span class=”t”>Keywords</span><span class=”m”>></span><span class=”tx”>0x80000000000000</span><span class=”m”></</span><span class=”t”>Keywords</span><span class=”m”>></span>
    <span class=”m”><</span><span class=”t”>TimeCreated</span> <span class=”t”>SystemTime</span><span class=”m”>=”</span><b>2019-06-18T14:54:59.225444600Z</b><span class=”m”>”</span><span class=”m”> /></span>
    <span class=”m”><</span><span class=”t”>EventRecordID</span><span class=”m”>></span><span class=”tx”>72423</span><span class=”m”></</span><span class=”t”>EventRecordID</span><span class=”m”>></span>
    <span class=”m”><</span><span class=”t”>Channel</span><span class=”m”>></span><span class=”tx”>Application</span><span class=”m”></</span><span class=”t”>Channel</span><span class=”m”>></span>
    <span class=”m”><</span><span class=”t”>Computer</span><span class=”m”>></span><span class=”tx”>Eamonn-PC-1</span><span class=”m”></</span><span class=”t”>Computer</span><span class=”m”>></span>
    <span class=”m”><</span><span class=”t”>Security</span> <span class=”m”>/></span>
    <span class=”m”></</span><span class=”t”>System</span><span class=”m”>></span>
    <span class=”m”><</span><span class=”t”>EventData</span><span class=”m”>></span>
    <span class=”m”><</span><span class=”t”>Data</span><span class=”m”>></span><span class=”tx”>Prepar3D.exe</span><span class=”m”></</span><span class=”t”>Data</span><span class=”m”>></span>
    <span class=”m”><</span><span class=”t”>Data</span><span class=”m”>></span><span class=”tx”>4.5.12.30293</span><span class=”m”></</span><span class=”t”>Data</span><span class=”m”>></span>
    <span class=”m”><</span><span class=”t”>Data</span><span class=”m”>></span><span class=”tx”>5cd47aad</span><span class=”m”></</span><span class=”t”>Data</span><span class=”m”>></span>
    <span class=”m”><</span><span class=”t”>Data</span><span class=”m”>></span><span class=”tx”>SimObjectAnimationModule64.dll</span><span class=”m”></</span><span class=”t”>Data</span><span class=”m”>></span>
    <span class=”m”><</span><span class=”t”>Data</span><span class=”m”>></span><span class=”tx”>1.6.4.0</span><span class=”m”></</span><span class=”t”>Data</span><span class=”m”>></span>
    <span class=”m”><</span><span class=”t”>Data</span><span class=”m”>></span><span class=”tx”>5c100d52</span><span class=”m”></</span><span class=”t”>Data</span><span class=”m”>></span>
    <span class=”m”><</span><span class=”t”>Data</span><span class=”m”>></span><span class=”tx”>c0000005</span><span class=”m”></</span><span class=”t”>Data</span><span class=”m”>></span>
    <span class=”m”><</span><span class=”t”>Data</span><span class=”m”>></span><span class=”tx”>000000000000dc78</span><span class=”m”></</span><span class=”t”>Data</span><span class=”m”>></span>
    <span class=”m”><</span><span class=”t”>Data</span><span class=”m”>></span><span class=”tx”>314c</span><span class=”m”></</span><span class=”t”>Data</span><span class=”m”>></span>
    <span class=”m”><</span><span class=”t”>Data</span><span class=”m”>></span><span class=”tx”>01d525df79ceb10c</span><span class=”m”></</span><span class=”t”>Data</span><span class=”m”>></span>
    <span class=”m”><</span><span class=”t”>Data</span><span class=”m”>></span><span class=”tx”>E:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe</span><span class=”m”></</span><span class=”t”>Data</span><span class=”m”>></span>
    <span class=”m”><</span><span class=”t”>Data</span><span class=”m”>></span><span class=”tx”>C:\Program Files (x86)\12bPilot\SODE\SimObjectAnimationModule64.dll</span><span class=”m”></</span><span class=”t”>Data</span><span class=”m”>></span>
    <span class=”m”><</span><span class=”t”>Data</span><span class=”m”>></span><span class=”tx”>0d3c425c-5b32-4fe8-a1d9-db7f95fc1e3d</span><span class=”m”></</span><span class=”t”>Data</span><span class=”m”>></span>
    <span class=”m”><</span><span class=”t”>Data</span> <span class=”m”>/></span>
    <span class=”m”><</span><span class=”t”>Data</span> <span class=”m”>/></span>
    <span class=”m”></</span><span class=”t”>EventData</span><span class=”m”>></span>
    <span class=”m”></</span><span class=”t”>Event</span><span class=”m”>></span>
    Faulting application name: Prepar3D.exe, version: 4.5.12.30293, time stamp: 0x5cd47aad
    Faulting module name: SimObjectAnimationModule64.dll, version: 1.6.4.0, time stamp: 0x5c100d52
    Exception code: 0xc0000005
    Fault offset: 0x000000000000dc78
    Faulting process id: 0x314c
    Faulting application start time: 0x01d525df79ceb10c
    Faulting application path: E:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
    Faulting module path: C:\Program Files (x86)\12bPilot\SODE\SimObjectAnimationModule64.dll
    Report Id: 0d3c425c-5b32-4fe8-a1d9-db7f95fc1e3d
    Faulting package full name:
    Faulting package-relative application ID:
Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic.