- This topic has 15 replies, 3 voices, and was last updated 7 years, 7 months ago by .
-
Posts
-
Hi, I have SODE 1.34 and EFB by Aivlasoft, with the main EFB window on a laptop networked with the main P3D computer. When the EFB is active and I want to dock or undock a SODE jetway, I get a message that no SODE jetways can operate because SODE has disconnected (N=0). If I close the EFB SODE works. Has this issue already been reported? Thanks.
Hi,
I don’t have the EFB so I can’t test it for incompatibility. The SODE.log looks ok till the last line. I think it is a SimConnect server issue and a simconnect log file would be interesting. This post tells you how to generate those logs http://forum.simflight.com/topic/45074-fsx-help-logging-simconnect/
I do have the same problems in P3D v3.3.5 and get the message “SODE jetways can’t operate because SODE has disconnected (N=0)” when trying to use a jetway on SODE airports. However, I don’t have EFB.
I uninstalled all SODE airpots, GSX and SODE as well. Then reinstalled and checked, that I have the latest versions of the aiports and of SODE (1.3.4). Still the same problem.
I can select a jetway (e.g. on Aerosoft’s Malaga X) but aftertriggering the flashing lights on the jetway turn on and it may move for a split second, but then the docking error occurs. Interestingly, GSX tells me, that there are no jetways to be operated.
On other airports (e.g. Aerosoft Rome) I can’t select any jetway and get the message, that there are no triggerable objects nearby. The jetways itself are visible on all airports.
I removed all addons from my exe.xml and dll.xml files (both in my app data and program data folders) without solving the issue.
When looking into the SODE logfile I can see the message “ERROR SODE.FSLOOP : SimConnect EXCEPTION! ID=3” multiple times after trying to trigger the jetway.
Regards,
UliIf you are familiar with teamviewer and are able to reproduce the problem, I can have a look at your setup directly and hopefully be able to find the root cause of this.
I am around until thursday evening for a teamviewer session if desired, just write to the contact address provided in the top menu of this site.
-Jeffrey
So, finally I got the jetways working. It seems to be a conflict with VRS Tacpack. If I disable Tacpack in my dll.exe the jetways work perfect. After enabling Tacpack again the jetways are broken again.
Gentlemen,
Seems that both issues are due to a bug in the P3D SimConnect server. It does not happen with FSX.
The Aivlasoft EFB or TacPack are generating a SimConnect exception (which can happen when trying to request some data on a object that has been removed in the meantime). The problem is that this exception is “broadcasted” to all client applications (SODE being one example) of the SimConnect server.
So, this exception is leaking into SODE and activates the exception handler code, which stops any triggered jetway because it thinks the jetway was removed and SODE should not set/read data to/from a removed object. But in reality, the jetway object still exists, but SODE gets fooled by the exception from the other software.
The bad thing is that it’s not easily possible to determine if a received exception is from an other module than your own. In FSX, you only receive exceptions that were created from your module.I try to rethink the exception handling code, but the real fixing should be done in the SimConnect server behaviour by Lockheed Martin.
Thanks for the information. Hopefully, Lockheed Martin will fix the SimConnect server issue. To do this, are they aware of the issue? In the meantime I can live with the it as I am not using my F14 (with TacPack) and moving jetways at the same time. But I guess users of EFB might have a bigger problem.
Yes, I have just reported this in their forums.
I have however found a workaround for this issue for the SODE exception handler. Fixed in V1.4.0.Great you found a solution. Looking forward to 1.4.0.
Just tested the new version 1.4.0. Sode Jetways now works properly through the Sode menu in Malaga, even with TacPack installed. However, if I want to activate the jetway through GSX, SODE disconnects and GSX tells me, that the jetway can’t be operated. Just a minor issue for me, but I wanted to give feedback on the update.
That’s due to a problem with the xml file provided by Simwings.
Find a fixed xml file here: http://forum.aerosoft.com/index.php?/topic/115560-sode-problem-at-malaga-with-fsxsp2/&do=findComment&comment=776153Thanks for your feedback, glad to hear SODE works with TacPack now.
- You must be logged in to reply to this topic.