Use of non-SODE jetways since last update

[Flying Dutchman]

Today I updated Couatl/GSX because I read in the update log that non-SODE jetways can now be handled via the GSX menu. That appeared right. But it stays a non-SODE jetway. So I still cannot edit the jetway to adjust it neatly to the doors of the aircraft. So what's the benefit of this update? CTRL+J is more easy than pop-up the GSX menu, choose a ground service, choose a jetway and confirm that I want that jetway to move to the airplane.

[virtuali]

I'm not sure I understand your "it stays a non-SODE jetway." question. The ONLY thing the update does, is to restore the trigger to operate a jetway, even if it's not SODE, but it's not supposed to magically transform a non-SODE jetway into a SODE one.

To do that, assuming you are referring to replacing 3rd party *standard* Jetways with GSX L2 ones, you'll always have to to through the steps of first excluding the original jetways, by creating a Exclude XML file that can be compiled into a BGL with the GSX Control Panel, and THEN, on the next start, you can start adding GSX SODE Jetways.

[Flying Dutchman]

Umberto, I'm sorry that, apparently, I didn't express myself clearly enough. I know that GSX replaces all default jetways by SODE jetways. I also know how to edit those jetways (see my other post about Hamburg, for which you still owe my an answer).

My question is: what is the benefit of this update, that enables moving the jetway to and from the airplane via the GSX menu? CTRL + J is far more easier.

Hans Hartvelt
The Netherlands

[virtuali]

My question is: what is the benefit of this update, that enables moving the jetway to and from the airplane via the GSX menu? CTRL + J is far more easier.

Of course CTRL+J is much easier but, since a user reported the "operate jetways" ( which on non-SODE jetways JUST sends a "Ctrl+J" ) that USED to work before, at some time stopped to work:

https://www.fsdreamteam.com/forum/index.php/topic,27622.msg186981.html#msg186981

and in fact, there was a problem with a previous update, we just fixed it, because that's what we try to do when users report a problem. I understand that feature might not be very exiting, and the whole point of GSX L2 is to get rid of default jetways but, since it wasn't working as designed, we fixed it.

[Flying Dutchman]

Hello Umberto, thank you very much for this clarifying answer.