Tagged: Sode Module
- This topic has 6 replies, 2 voices, and was last updated 5 years, 5 months ago by 12bPilot.
-
AuthorPosts
-
30. October 2018 at 08:46 #2939blaunarwalParticipant
Hi
I’m using the freeware LFSB from here http://www.euroairport2011.homepage.t-online.de/
I use 1.6.3, lastest version.
It has SODE Jetways, which I installed in C:\ProgramData\12bPilot\SODE. They work optically. With the SODE Window, I can attach the Jetways, but to detach, I have to reset all jetways. I read, starting the strobe would detach the Jetway, but it doesn’t with the BB A321 I tested it. Also GSX, Level 2, does not recognize the SODE Jetways on this airport. I tried several things, let GSX rebuild the cache etc. If I alter the GSX parkings, the correct ADE file is used. There is no other ADE for LFSB (eliminated all others).
What is the problem? I use GSX on other airports without problem to move SODE Jetways.
Regards
Dan
30. October 2018 at 10:18 #294112bPilotKeymasterSince I didn’t build the scenery I can’t give you detailed support. SODE itself seems to work fine otherwise and that’s my area of support I can give.
My guess is that the AFCAD/ADE used is not properly matched to the airport’s SODE config file (xml).
Can you detach the jetway using the menu (instead of the aircraft beacon)?
I’d recommend to contact the add-on developer directly.
30. October 2018 at 10:32 #2943blaunarwalParticipantNo I can’t detach via menu, there’s no option after attach. There are two options, the one to attach and one “no other objects” or similar. If I click this, the menu dissapears.
The xml just has a few jetways configured. Nothing to not match de ADE I guess. The jetways are were the should be. So that cant be so wrong.
I will ask the developer of the EAP scenery.
Thanks
Dan
30. October 2018 at 14:00 #294412bPilotKeymasterHey Dan,
I have quickly downloaded the scenery and the jetways since it’s freeware…
Checking the jetway placement xml, my guess was correct! The AFCAD/ADE data in the xml do not match the actual AFCAD/ADE parking data in the bgl, leaving the xml ill-defined.
This means that SODE can’t reliably detect the jetway associated to the parking position, and GSX is completely not able to link the parking position to a jetway.
I have uploaded a corrected jetway placement xml here with proper data to the AFCAD/ADE file. I have not tested it, but I’m pretty confident that it will work.
Attachments:
You must be logged in to view attached files.30. October 2018 at 22:16 #2948blaunarwalParticipantHey Dan, I have quickly downloaded the scenery and the jetways since it’s freeware… Checking the jetway placement xml, my guess was correct! The AFCAD/ADE data in the xml do not match the actual AFCAD/ADE parking data in the bgl, leaving the xml ill-defined. This means that SODE can’t reliably detect the jetway associated to the parking position, and GSX is completely not able to link the parking position to a jetway. I have uploaded a corrected jetway placement xml here with proper data to the AFCAD/ADE file. I have not tested it, but I’m pretty confident that it will work.
Hey that’s great news. Will test it tomorrow. But tell me, what is different. The coordinates should be matching, else the jetways were missplaced, or not? I will have a look at the two files tomorrow anyway. It’s very nice you had a look at it. It’s also a good piece of freeware.
Dan
31. October 2018 at 19:30 #2949blaunarwalParticipantOk it’s working. There is only a small problem in the interaction with GSX. If the jetway is already attached and I ask GSX to deboard, the jetway goes back to start and I have to tell GSX how to attach the jetway. But that’s a GSX problem.
I will inform the designer of this LFSB scenery too about the xml problem.
Thanks a lot.
Dan
31. October 2018 at 21:48 #295212bPilotKeymasterThere is only a small problem in the interaction with GSX. If the jetway is already attached and I ask GSX to deboard, the jetway goes back to start and I have to tell GSX how to attach the jetway. But that’s a GSX problem.
Yeah, that’s a known issue by fsdreamteam. The problem is that GSX does not know the state of the jetway (docked/undocked/moving) when it was operated by the SODE menu first, or when someone uses the automatic triggering function of SODE based on the aircraft state.
The next SODE version will transmit this bit of information to GSX upon request. So, it is something that is going to be fixed in the future.
-
AuthorPosts
- You must be logged in to reply to this topic.