Hopefully this will help FSDT GSX SODE  be able to connect to AI eventually.

https://sode.12bpilot.ch/?p=3120

 

It is not SODE's fault that this is not possible, it is simply a choice of FSDT to not allow that. With "pure" SODE jetways that is already possible. It is just a matter of convincing FSDT to allow it as well with their SODE-jetways.

Change Log

8. December 2014 12bPilot

Version 1.6.4

• Installer
  • P3Dv4: SimObjects path in add-on.xml is now dynamically set during install time, fixing missing objects when installed on other drive than 😄
• General
  • Fixed bug in the object injection routine resulting in missing objects
  • Added “LVar” interface to query variables of add-on aircraft, e.g. FSLabs A32X Parking brake and beacon states
  • Added support for P3D v4.4+ MDL files
  • Fixed bug where UTLive aircraft were not added to the SimObjects list
• Jetway Control System
  • Fixed bug where SODE would not recognize the GSX transmitted raw gate name when a custom designator is defined in the xml, resulting in a reset of the jetway
  • Enhanced API to transmit jetway docking status and served door IDs to GSX
  • Fixed bug in crossing jetway calculation and detection
  • Improved automatic multi-jetway assignment logic using the fixed crossing jetway code
  • Added ‘Shallow Angle’ jetway trajectory. If the final jetway bridge heading and the aircraft heading form a “shallow angle” (smaller than 20 degrees), then jetway will now move in a two-step manner: partially rotating and fully extending, and then rotating to the door. This avoids the “scraping” of the jetway along the fuselage during extension.
• AI Detection
  • Fixed bug where AI Traffic data returned an unexpected user aircraft object ID, resulting in loss of AI detection capability

Install instructions are included or it’s just an update over the existing installation?.

Cheers, Ed

1 hour ago, edpatino said:

Install instructions are included (...) ?

If you have a look at the manual, you will see this:

'2.1 Upgrading SODE
As of version 1.4.0, the SODE installer is able to detect if an older or newer SODE version is
installed on your machine.
• If an older version is found, the newer installer will automatically uninstall it
• If a newer version is found, the installer will abort
→ You don't need to manually uninstall SODE anymore if you use one of the newer installers, just
run it and it will handle everything automatically'
 

1 hour ago, Rafal said:

If you have a look at the manual, you will see this:

'2.1 Upgrading SODE
As of version 1.4.0, the SODE installer is able to detect if an older or newer SODE version is
installed on your machine.
• If an older version is found, the newer installer will automatically uninstall it
• If a newer version is found, the installer will abort
→ You don't need to manually uninstall SODE anymore if you use one of the newer installers, just
run it and it will handle everything automatically'
 

Thanks so much.

Cheers, Ed

Wow, after installing 1.6.4 - it still shows up as 1.6.3 (very confusing)

35 minutes ago, Skywolf said:

Wow, after installing 1.6.4 - it still shows up as 1.6.3 (very confusing)

Same here.  Where that does looks to be TEXT not actually reading the version itself, but still noteworthy!

Best wishes.

 

 

Same here.
The first 3 are 1.6.4.0.
The last (SODEPlatformManager.exe) is 1.6.3.0.

I've had this option ticked for a while now, but recently unchecked it. Is it fixed? The thing is that Jetways auto-dock to AI but as well to my plane; so basically when I open up GSX to board PAX the jetways dissapear. It's incredibly annoying and I still wonder why am I (my model) considered as AI.

Thanks for clarification.  They should have updated the app to show 1.6.4 vs 1.6.3.  Oh well, everything is installed perfectly.

On 12/13/2018 at 9:46 AM, officercrockey said:

It is not SODE's fault that this is not possible, it is simply a choice of FSDT to not allow that. With "pure" SODE jetways that is already possible. It is just a matter of convincing FSDT to allow it as well with their SODE-jetways.

That's not the case. We decided to focus on performance first, since jetways for AI will obviously have an impact on fps and, in fact, it took quite a bit of additional effort to:

- model the static versions of 85+ different jetways in *addition* to the dynamic version.

- coding all the switching system, so the switch from static jetway to dynamic is not very noticeable.

And this, only because we take fps very seriously.

But of course, since lots of users asked for it, we confirmed multiple times that Jetways for AI will come in GSX, so there's no need to convince anybody.

In order to make this less painful as possible from a performance point of view, we have been discussing with Jeffey Stahli (SODE's author) what will be the best way to do it, and this will surely require an update to the API GSX and SODE use to communicate, since right now, GSX jetways are not known to SODE until they are activated on a parking and, in order to not spam the simulator with unnecessary data requests, we'll just piggyback on what SODE is already doing, since it wouldn't make much sense if *both* SODE and GSX would ask for the same data (all AI positions) for the same purpose.

Now the new version is out, perhaps there will be a chance to enhance the SODE GSX API, which will allow GSX jetways to work with AI as well.

9 hours ago, virtuali said:

But of course, since lots of users asked for it, we confirmed multiple times that Jetways for AI will come in GSX, so there's no need to convince anybody

 

9 hours ago, virtuali said:

In order to make this less painful as possible from a performance point of view, we have been discussing with Jeffey Stahli (SODE's author) what will be the best way to do it, and this will surely require an update to the API GSX and SODE use to communicate, since right now, GSX jetways are not known to SODE until they are activated on a parking and, in order to not spam the simulator with unnecessary data requests, we'll just piggyback on what SODE is already doing, since it wouldn't make much sense if *both* SODE and GSX would ask for the same data (all AI positions) for the same purpose.

Many thanks for this Umberto, very much appreciated, I am sure you will make many people happy as always.

All the best,

Simbol