Idea for injecting multiple jetway

[Sadawa_senseio]

When we see that jumbo jets are becoming more and more popular (777, A380), we think that what gsx lacks is the control of several jetways.

We know that the sdk limits the number of jetways to one per gate. However, GSX and the Python engine can inject SimObjects (staircases, loading belts, etc.), which can read the coordinates where the airplane doors are precisely located, so couldn't it be for jetways?
For example, when customizing airport gates, we can place jetways and assign a number to them. Then, in the gsx menu, as on P3D, choose which jetways to assign to the doors.
Of course it's just an idea and I don't know if it's possible for FSDT because i've never devloped gsx and I think they must have already thought of it?

And please understand that my distress call is from someone who wants these jetways to sumblimate these long-haul planes.   

[Captain Kevin]

Just to be clear, the only way you could have multiple jetways in P3D was via SODE. You couldn't have multiple jetways using the standard jetway method. That being said, the developer of SODE has no motivation to develop for MSFS since the SDK keeps changing and it may render SODE obsolete.

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

[Sadawa_senseio]

yes i know it was SODE on P3D and like i said, they can't make like the others simboject if they can indicate the doors position like for the stair, loading belt ect ?

[Fabo]

SODE is not the only method, though it did become a very standard method and also one used by FSDT.

Frankly I'm suprised nobody cared to remake this, even virtuali, and everybody is hiding behind "sim only supports one jetway". Of course it's more than fair that Jeffrey decided not to bother, but, like. Surely it's a thing that GSX could decide to support?

[Captain Kevin]

SODE is not the only method, though it did become a very standard method and also one used by FSDT.

What was the other method.

[virtuali]

SODE is not the only method, though it did become a very standard method and also one used by FSDT.

Yes, it was basically the only method and even if there might have been others, SODE because a de-facto standard long before GSX supported it.

Of course it's more than fair that Jeffrey decided not to bother, but, like. Surely it's a thing that GSX could decide to support?

The problem is, GSX supported SODE when it was already used by many other developers, and it was freeware. While we could do something similar in MSFS, the main problem will be convincing airport developers to use it, and it's very likely they'll object to it, since it would be part of GSX, which is not free.

And, Microsoft position about multiple jetways is not very clear. They said "not at launch", which might mean anything, 6 months, a year, 3 years, nobody knows.

[Sadawa_senseio]

So we agree on all that, now the question is, can the fsdt developers implement a multiple jetway function in gsx that is not based on sode but on the same principle as for their simobjects (give coordinates for doors and follow them) as for conveyers, catering trucks etc.? I mean, sure, scenery developers will have to modify their scenery to exclude static jetways, however, I think it will be much more advantageous to offer this option, it would give gsx an extra selling point, I also think there are a lot of developers (myself included) waiting for this feature if fsdt does it.

[Fabo]

Yep, SODE became de facto standard, I agree there. It is a bit sad that Jeffrey didn't move forward with it though I understand the reasoning.

So I suppose in practice if we want to have something like this done, it would mean to basically implement SODE-like in MSFS and hope enough scenery devs use it to make sense to integrate with GSX...