SODE Jetways - Appcrash/disconnect problem

[ESzczesniak]

I'm very excited about KMEM and the concept of the SODE jetways.  However, I'm having some problems using them and was hoping to see if you guys might be able to point me in the right direction to solve this.  In the sim (P3D v3.2), I've been testing at gate C20 with either the Aerosoft A319 or PMDG 737-800.  If I request either deboarding or boarding, I do get the expected dialogues to connect the C20 jetway to door 1L.  The beacon will briefly flash, and in the case of boarding the jetway moves about halfway to the aircraft.  However, both situations quickly end with the in sim message of "All active modules stopped due to main module (exe) disconnection! (N = 0)".  After exiting the program I get a SODE crash dialogue with the following details:

Problem Event Name:   APPCRASH
  Application Name:   SimObjectDisplayEngine.exe
  Application Version:   1.3.3.0
  Application Timestamp:   574c9eb1
  Fault Module Name:   StackHash_0a9e
  Fault Module Version:   0.0.0.0
  Fault Module Timestamp:   00000000
  Exception Code:   c0000005
  Exception Offset:   000007f0
  OS Version:   6.1.7601.2.1.0.256.48
  Locale ID:   1033
  Additional Information 1:   0a9e
  Additional Information 2:   0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:   0a9e
  Additional Information 4:   0a9e372d3b4ad19135b953a78882e789

Any ideas where I should look for a solution?  I have never had SODE installed previously on my system, so there are no old versions.  I did install the updated GSX as well as KMEM installers.

[12bpilot]

Hi,

The first thing to check are the dll.xml and exe.xml files. For P3Dv3, there are two locations for this pair of files, C:\ProgramData\Lockheed Martin\Prepar3D v3 and C:\Users\Jeffrey\AppData\Roaming\Lockheed Martin\Prepar3D v3. Please check for possible duplicate entries or post the contents here in the forum thread.

Also, the SODE.log located at  C:\ProgramData\12bPilot\SODE\log could be helpful.

[ESzczesniak]

Thank you for the help. The dll and exe files outwardly look ok to me.  Unfortunately this stuff doesn't all mean a lot to me, so I've copied the contents below for anyone that it may mean more to.  I've removed a large number of duplicate entries (with different time stamps) for brevity.  It seems that it starts to go down hill when SODE is looking for xml, SDX, and cfg files in the SODE folder...but I don't really know what do do about this or if I'm even correct.

SODE.log
[12:55:48.888] INFO  : Targetting Platform 'P3Dv3'
[12:55:48.888] DEBUG  : Initializing Text Menus...
[12:55:48.888] DEBUG  : Initializing Seasonal Object Handler...
[12:55:48.888] DEBUG  : Initializing SimObject Lists...
[12:55:48.888] DEBUG  : Initializing QuadTree...
[12:55:48.888] DEBUG  : Initializing Sound Engine...
[12:55:48.937] INFO SODE.SOUNDENGINE : SoundEngine initialized.
[12:55:48.938] DEBUG  : Initializing Sim Bubble...
[12:55:48.938] DEBUG  : Initializing AI Monitor...
[12:55:48.938] DEBUG  : Initializing Jetway Handler...
[12:55:48.938] DEBUG  : Initializing VDGS Handler...
[12:55:48.938] WARN  : VDGS Pack is not found/installed!
[12:55:48.938] DEBUG  : Start Main Initialization!
[12:55:48.938] DEBUG  : Trying to read Settings from SimObjectsDisplayEngine.ini file...
[12:55:48.939] DEBUG SODE.SETTINGS : All Settings successfully read.
[12:55:48.939] DEBUG SODE.SETTINGS : CurrentSettings -> SoundEngine=1; WatchDog=1; UserJetwaySound=1; SecMenuHotKey=SHIFT+VK_MINUS; AIDetection=0; AIJetwaySound=0
[12:55:48.939] DEBUG  : Trying to find Custom Configuration files...
[12:55:48.939] DEBUG SODE.XML : Finding SDX CFG Files...
[12:55:48.940] WARN SODE.XML : \cfg\ not found. Code(2) [C:\ProgramData\12bPilot\SODE\cfg\*.sdx]
[12:55:48.940] DEBUG  : Trying to build SimObject List out of Custom Config files...
[12:55:48.940] WARN SODE.XML : No SDX Files found! Lists are empty.
[12:55:48.940] DEBUG  : Trying to find XML Definition files...
[12:55:48.940] DEBUG SODE.XML : Finding XML Files...
[12:55:48.940] WARN SODE.XML : \xml\ not found. Code(2) [C:\ProgramData\12bPilot\SODE\xml\*.xml]
[12:55:48.940] DEBUG  : Trying to build SimObject List out of XML definition files...
[12:55:48.940] WARN SODE.XML : No XML Files found! Lists are still empty.
[12:55:48.940] DEBUG  : List generated! Trying now to insert into QuadTree...
[12:55:48.940] DEBUG  : QuadTree populated with SimObject references.
[12:55:48.940] DEBUG  : Trying to generate Aircraft Parameter Map from the INI file...
[12:55:48.946] DEBUG SODE.ACFTPARAMS : Door Parameters read for 26 ICAO Aircraft Types.
[12:55:48.946] DEBUG  : SDX/XML/INI Handling done! Start FS Processing...
[12:55:48.946] DEBUG  : Initializing Internal Sounds...
[12:55:48.946] DEBUG  : All Initialization Done!
[12:55:48.946] DEBUG SODE.FSPROCESS : Trying to connect to FS...
[12:55:48.947] DEBUG SODE.FSPROCESS : Connected to FS!
[12:55:48.947] FATAL SODE.FSLOOP : No SimObjects inside Lists! SODE runs in 'External Jetway Triggering Mode' only...
[12:55:48.947] DEBUG SODE.FSPROCESS : Setting up Connection Watchdog...
[12:55:48.947] DEBUG SODE.FSPROCESS : Entering FS Dispatch Loop.
[12:56:09.527] INFO SODE.FSLOOP : SODE connected to Simulator...
[12:56:09.529] DEBUG SODE.ACFTEXITS : No Custom Data Found for G:/Prepar3D v3/SimObjects/Airplanes/VRS_FA-18E/. Using original aircraft.cfg exit data!
[12:56:09.530] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in C:\ProgramData\12bPilot\SODE\SimObjects\
[12:56:09.530] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in C:\Program Files (x86)\12bPilot\SODE\data\SimObjects\
[12:56:09.530] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in G:\Prepar3D v3\SimObjects\Airplanes\
[12:56:09.636] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in G:\Prepar3D v3\SimObjects\Avatars\
[12:56:09.636] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in G:\Prepar3D v3\SimObjects\Rotorcraft\
[12:56:09.640] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in G:\Prepar3D v3\SimObjects\GroundVehicles\
[12:56:09.665] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in G:\Prepar3D v3\SimObjects\Boats\
[12:56:09.682] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in G:\Prepar3D v3\SimObjects\Animals\
[12:56:09.683] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in G:\Prepar3D v3\SimObjects\Misc\
[12:56:09.740] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in G:\Prepar3D v3\SimObjects\Submersible\
[12:56:09.740] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in G:\Prepar3D v3\SimObjects\Weapons\
[12:56:09.744] DEBUG SODE.FOLDERMANAGER : Looking for sim.cfg files in G:\Prepar3D v3\SimObjects\Countermeasures\
[12:56:09.745] INFO SODE.FOLDERMANAGER : SODE SimObjects Map Building completed. Size=180
[12:56:09.746] INFO SODE.FSLOOP : Successfull Registration of Reserved Key -> s Tab+S
[12:58:06.960] ERROR SODE.FSLOOP : SimConnect EXCEPTION! ID=3
...
[12:58:10.989] ERROR SODE.FSLOOP : SimConnect EXCEPTION! ID=3
[12:58:25.481] DEBUG SODE.ACFTEXITS : No Custom Data Found for G:/Prepar3D v3/SimObjects/Airplanes/PMDG 737-700NGX WL/. Using original aircraft.cfg exit data!
[12:58:32.040] ERROR SODE.FSLOOP : SimConnect EXCEPTION! ID=3
...
[13:00:29.942] ERROR SODE.FSLOOP : SimConnect EXCEPTION! ID=3
[13:00:34.648] DEBUG SODE.FSLOOP :  [API::TRIGGER] Received Trigger Client Data: ObjID=460, DoorDesignator='1L', OwnFlag=1, DoorDataOverrideFlag=1
[13:00:34.650] DEBUG SODE.FSLOOP :  [API::TRIGGER] Received Trigger Client Data: ObjID=460, DoorDesignator='4L', OwnFlag=1, DoorDataOverrideFlag=1
[13:00:37.985] DEBUG SODE.FSLOOP :  [API::TRIGGER] Received Trigger Client Data: ObjID=460, DoorDesignator='1L', OwnFlag=1, DoorDataOverrideFlag=1
[13:00:37.995] ERROR SODE.FSLOOP : SimConnect EXCEPTION! ID=3

...
[13:01:45.929] ERROR SODE.FSLOOP : SimConnect EXCEPTION! ID=3
[13:01:49.047] DEBUG SODE.FSLOOP :  [API::TRIGGER] Received Trigger Client Data: ObjID=584, DoorDesignator='1L', OwnFlag=1, DoorDataOverrideFlag=1
[13:01:49.049] DEBUG SODE.FSLOOP :  [API::TRIGGER] Received Trigger Client Data: ObjID=584, DoorDesignator='4L', OwnFlag=1, DoorDataOverrideFlag=1
[13:01:49.060] ERROR SODE.FSLOOP : SimConnect EXCEPTION! ID=3
...
[13:01:51.003] ERROR SODE.FSLOOP : SimConnect EXCEPTION! ID=3
[13:01:53.985] DEBUG SODE.FSLOOP :  [API::TRIGGER] Received Trigger Client Data: ObjID=584, DoorDesignator='1L', OwnFlag=1, DoorDataOverrideFlag=1
...
[13:02:36.063] ERROR SODE.FSLOOP : SimConnect EXCEPTION! ID=3
[13:02:39.265] DEBUG SODE.FSLOOP :  [API::TRIGGER] Received Trigger Client Data: ObjID=707, DoorDesignator='1L', OwnFlag=1, DoorDataOverrideFlag=1
[13:02:39.359] DEBUG SODE.FSLOOP :  [API::TRIGGER] Received Trigger Client Data: ObjID=707, DoorDesignator='4L', OwnFlag=1, DoorDataOverrideFlag=1
[13:02:41.607] DEBUG SODE.FSLOOP :  [API::TRIGGER] Received Trigger Client Data: ObjID=707, DoorDesignator='1L', OwnFlag=1, DoorDataOverrideFlag=1
[13:02:57.698] INFO SODE.FSLOOP : SODE disconnected from Simulator!
[13:02:57.699] DEBUG SODE.FSPROCESS : Cleaning up Memory...

dll.xml in AppData
<?xml version="1.0" encoding="WINDOWS-1252"?>
-<SimBase.Document version="1,0" Type="Launch">
<Descr>Launch</Descr>
<Filename>dll.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
-<Launch.Addon>
<Name>ObjectFlow</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>G:\Prepar3D v3\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow_P3D.dll</Path>
</Launch.Addon>
-<Launch.Addon>
<Name>FSUIPC 4</Name>
<Disabled>False</Disabled>
<Path>Modules\FSUIPC4.dll</Path>
</Launch.Addon>
-<Launch.Addon>
<Name>PMDG HUD interface</Name>
<Disabled>False</Disabled>
<Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path>
<DllStartName>module_init</DllStartName>
<DllStopName>module_deinit</DllStopName>
</Launch.Addon>
-<Launch.Addon>
<Name>PMDG Interface</Name>
<Disabled>False</Disabled>
<Path>PMDG\DLLs\PMDG_Interface.dll</Path>
<DllStartName>module_init</DllStartName>
<DllStopName>module_deinit</DllStopName>
</Launch.Addon>
-<Launch.Addon>
<Name>RAASPRO</Name>
<Disabled>False</Disabled>
<Path>.\RAASPRO\RAASPRO.dll</Path>
<DllStartName>module_init</DllStartName>
<DllStopName>module_deinit</DllStopName>
</Launch.Addon>
-<Launch.Addon>
<Name>as_connect</Name>
<Disabled>False</Disabled>
<Path>as_srv\as_btstrp.dll</Path>
</Launch.Addon>
-<Launch.Addon>
<Name>VRS_TacPack</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>Modules\VRS_TacPack\VRS_TacPack.dll</Path>
</Launch.Addon>
</SimBase.Document>

and the dll.xml in ProgramData
<?xml version="1.0" encoding="WINDOWS-1252"?>
-<SimBase.Document id="dll" version="3,0" Type="AceXML">
<Descr>AceXML Document</Descr>
<Filename>dll.xml</Filename>
-<Launch.Addon>
<Name>SODE Animation Module</Name>
<Path>C:\Program Files (x86)\12bPilot\SODE\SimObjectAnimationModule.dll</Path>
</Launch.Addon>
-<Launch.Addon>
<Name>Addon Manager</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>bglmanx.dll</Path>
</Launch.Addon>
-<Launch.Addon>
<Name>Flight Recorder</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>Aerosoft\Flight Recorder\AS-FlightRecorder.dll</Path>
</Launch.Addon>
</SimBase.Document>

And exe.xml in AppData
<?xml version="1.0" encoding="WINDOWS-1252"?>
-<SimBase.Document version="1,0" Type="Launch">
<Descr>Launch</Descr>
<Filename>exe.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
-<Launch.Addon>
<Name>as_btstrp_config_manager</Name>
<Disabled>False</Disabled>
<Path>as_srv\as_btstrp_config_manager.exe</Path>
</Launch.Addon>
</SimBase.Document>

and the exe.xml in ProgramData
<?xml version="1.0" encoding="WINDOWS-1252"?>
-<SimBase.Document id="exe" version="3,0" Type="AceXML">
<Descr>AceXML Document</Descr>
<Filename>exe.xml</Filename>
-<Launch.Addon>
<Name>SODE</Name>
<Path>C:\Program Files (x86)\12bPilot\SODE\SimObjectDisplayEngine.exe</Path>
<CommandLine>P3Dv3</CommandLine>
</Launch.Addon>
-<Launch.Addon>
<Name>Couatl</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>fsdreamteam\couatl\couatl.exe</Path>
</Launch.Addon>
</SimBase.Document>

[12bpilot]

Thanks for the data.
xml files look fine to me. The SODE.log is also good, the warning about cfg/sdx/xml folders are safe, because you have no other SODE airports on your hard drive.
The only thing is that SODE obviously uses wrong Object IDs when trying to trigger a jetway. If SODE crashes for some reason and is not shutdown properly, it will remain running in the background. When you re-start the sim, that faulty SODE instance blocks any new SODE instances. Normally, SODE shuts down when the sim shuts down normally. SODE is also able to detect when the sim crashes and shuts down as well. But in some remote cases, it may still continue to run. So if something odd happens when you quit the sim, check the windows task manager for a "zombie" SODE process and kill it.

[ESzczesniak]

Unfortunately I still seem to be struggling with this.  I do not see any zombie SODE processes active, and encounter this problem after a fresh boot and then straight in to the simulator. 

[ESzczesniak]

Is there anyway to debug the wrong Object ID's?  I've tried looking for zombie processes, reinstalling programs, installing SODE from the website, new simconnects, etc.  None of this has seemed to fix things.  Thanks for any help.

[ESzczesniak]

I have partially figured this out.  While trying to think about what else might mess with SimObject ID's, I realized that VRS TacPack uses SimObjects for some of it's ships, AI, etc.  I disabled this and the SODE jetways work as expected now.  I can certainly enable/disable VRS TacPack as needed (won't be loading munitions at the gate...), but was wondering if this helps figure things out at all and if there'd be an enduring fix as a result?

[virtuali]

There seems to be a longstanding issue with the VRS TacPack that neither we or them were able to understand. But what happens, is that Simconnect seems to go bonkers for a reason, and start reporting strange exceptions:

http://www.fsdreamteam.com/forum/index.php/topic,12542.msg100210.html#msg100210

It seems that Simconnect is "leaking" exceptions into all its connected clients and it has been reported to LM too:

http://www.prepar3d.com/forum/viewtopic.php?f=6310&t=7055

[ESzczesniak]

Interesting to know.  Well, I'm happy as long as I can pick or choose.  Odd with TacPack though...but not an issue for you guys to deal with at all.  Thanks.

[12bpilot]

It seems that Simconnect is "leaking" exceptions into all its connected clients and it has been reported to LM too:

I just ran some tests and confirm this: I have created a tiny SimConnect application with the sole purpose of generating an UNRECOGNIZED_ID exception. The simconnect call is RequestDataOnSimObject with a invalid ObjectID and a rate of PERIOD_SECOND.
This exception is somehow "broadcasted" to all the SimConnect clients like the AddOnManager, SODE etc. I checked that all the other clients do not generate exceptions in the debug console window. Once I fire up my exception generator app, the exceptions pop up at a regular interval, i.e. 1 second (request data rate). Funny thing is that the module id in the log (the id in brackets [XX]) refers to completely different clients! Sometimes, the log indicates that the error originates from SODE (which is wrong) and the SODE exception handler of course gets into action, stopping the movement of the jetway when triggered, because it thinks the jetway is not created. Unfortunately, I can not filter the true origin of the exception leaking into SODE to fix this issue (retrieving the objectID via the SentPacketID is cumbersome!).
Fair enough, in FSX, the expection is not forwared to the other clients in any way. It only occurs with P3D.
I also observed, that when using PERIOD_ONCE, the exception will not leak. Only with recurring requests (_SECOND, _SIMFRAME, etc).

In a nutshell: Once a SimConnect client (in your case TacPack) generates a UNRECOGNIZED_ID exception from a periodic RequestDataOnSimObject() call, this exception leaks into other clients and can fool the exception handling of those clients.

-Jeffrey

[virtuali]

In a nutshell: Once a SimConnect client (in your case TacPack) generates a UNRECOGNIZED_ID exception from a periodic RequestDataOnSimObject() call, this exception leaks into other clients and can fool the exception handling of those clients.

Very interesting to know Jeffrey, have you posted this on LM forum, maybe sending the the test app ?

[12bpilot]

Posted: http://www.prepar3d.com/forum/viewtopic.php?f=6310&t=120711
I hope they can fix this.
However, I was able to rule out those bogus exceptions from being handled by SODE.

[BuddyDog]

Hi Jeffrey,

I have some of the same problems with KIAH and SODE.  Never knew AivlaSoft EFB could be a problem.

Please take a look at my thread (link below) and let me know if you have any ideas.

Thanks.

http://www.fsdreamteam.com/forum/index.php/topic,14249.0.html