Jetways not working flightbeam NZAA msfs 2024

[e4logics]

Has anyone got a fix for the flightbeam NZAA jetways not moving? Jetways work in 2020 but not in 2024 for NZAA. I got the scenery from fligtbeam. All other flightbeam scenery I have are working.

[George8295]

Can also confirm this.

The gates on the eastern side of the airport (domestic) seem to work. But the international gates over on the western side do not work.

I have tried with different aircraft, and then removed GSX and it was the cause.

Can we please get this looked into?

[virtuali]

I have tried with different aircraft, and then removed GSX and it was the cause.

If you have only MSFS 2024, the FSDT Installer will automatically disable all GSX replacement jetway files, because they are not compatible with MSFS 2024 so, if you have only MSFS 2024 installed, check again if they have been in fact Disabled and if they haven't, put all jetway replacement files and all airport service files on the Disabled side and select Apply.

If you have both MSFS 2020 and MSFS 2024, you will be ASKED if you want to disable jetways and airport services, because doing this will affect both simulators. But it's not if you have any choice: if you use MSFS 2024, you must disable them all.

Those files are the only possible reason why GSX might affect jetways.

Another reason why jetways don't work, which doesn't have anything to do with GSX, is the presence of an Helipad nearby. There's a known bug (which dates MSFS 2020 and hasn't been fixed in 2024) that helipads close to a terminal will prevent jetways to work. The only solution is to edit the airport and explicitly disable the helipad.

[Drumcode]

If you have both MSFS 2020 and MSFS 2024, you will be ASKED if you want to disable jetways and airport services, because doing this will affect both simulators. But it's not if you have any choice: if you use MSFS 2024, you must disable them all.

I asked this on the Avsim forums the other day, but nobody responded. So where are we at this point with the gates compatibility? SU1 released and there were updates to the SDK. Are we still in a hole? Any promises from Microsobo or a timeframe to expect when this will work as it did in 2020?

[virtuali]

So where are we at this point with the gates compatibility

Let's clarify what we are missing, which is not generic "gates compatibility", if with "gates" you mean Jetways. Jetways work 100% fine in MSFS 2024, mostly because they are NOT handled by GSX so, once you are sure you have the GSX replacement Jetways disabled, you removed the only GSX-related issue with jetways, which will then work (or not) entirely depending how they are made, the airplane, the airport.

Not forgetting the discussed issue caused by nearby Helipads, which of course is completely unrelated to GSX and it must be fixed by MS/Asobo.

Having said that, what we are missing in relationship with jetways in MSFS 2024 are GSX replacement jetways for BARE DEFAULT airports, which always were the only place where you could possibly use GSX replacement jetways in MSFS 2020. With "bare default", meaning not 3rd party, not custom, not handcrafted.

In order to have these updated for MSFS 2024, we need the ability to optionally download the streamed base files, which has been promised, but it's still not there.

[Drumcode]

In order to have these updated for MSFS 2024, we need the ability to optionally download the streamed base files, which has been promised, but it's still not there.

This answers my question Umberto, thanks. Is this something that we as community need to put pressure on them about, or is this something that is handled between you and their dev team and we should leave it alone for now?

[virtuali]

Is this something that we as community need to put pressure on them about, or is this something that is handled between you and their dev team and we should leave it alone for now?

Do you think the only benefit of being able to download streamed packages would be useful "just" to allow us to create jetway replacement files for bare default airports ?

It's a main feature that has clearly been planned for a long time (otherwise, there wouldn't be both "Official2020" and "Official2024" folders, which are the places where downloaded packages will be found), so there's no doubt it will come, with MS/Asobo will feel it's time.

[George8295]

I think the presence of the helipad might possibly be the culprit.

On the eastern side of the airport where the gates work there is no helipad.

But the western side of the airport does have a helipad nearby. Might have to have a google on how to disable that helipad

[virtuali]

Might have to have a google on how to disable that helipad

It's not very easy to do, but it's very easy for the airport developer instead, just an extra line in the airport source xml, which can close the Helipad. We had to do this at KORD, since several jetways on terminal M didn't work because of the helipad very close to it.

[finnisher]

Might have to have a google on how to disable that helipad

It's not very easy to do, but it's very easy for the airport developer instead, just an extra line in the airport source xml, which can close the Helipad. We had to do this at KORD, since several jetways on terminal M didn't work because of the helipad very close to it.

Fightbeam NZAA jeyways DO work when using the default MSFS2024 ATC comms menu. It seems that everything that relies on SimConnect to command the jetways don't work e.g. GSX, Fenix A320, iniA350, Axis and Ohs (1 (>K:TOGGLE_JETWAY)). Does this seem like a helipad problem? This is an honest question.

The jetways animation also break if GSX services are activated before commanding the jeyways via the default ATC comms menu. They work fine if GSX services are not activated prior to trying to move them.

[virtuali]

Fightbeam NZAA jeyways DO work when using the default MSFS2024 ATC comms menu. It seems that everything that relies on SimConnect to command the jetways don't work e.g. GSX, Fenix A320, iniA350, Axis and Ohs (1 (>K:TOGGLE_JETWAY)). Does this seem like a helipad problem? This is an honest question.

There are two ways the bug manifest itself:

- In SOME cases, the problem only affects add-ons that trigger the jetway, even if they work in the default ground services menu. I think this was the case of the very well known conflict at Paris caused by the Voloport package.

- In OTHER cases, the jetway doesn't even SHOW on the default ATC menu

The difference seems to be be how many *other* installed sceneries have disabled jetways for the same airport, if the add-on airport is the first one disabling jetways (because there were none in the bare default scenery on the same gate) it might be affected in a different way, compared to an airport that already had their jetways disabled by another airport which is in turn also overridden by a 3rd one, like FSDT KORD, which disables jetways and overrides MS handcrafted KORD, which also overrides the bare default KORD jetways. This "cascading" disabling seems to be the most problematic one.

The jetways animation also break if GSX services are activated before commanding the jetways via the default ATC comms menu. They work fine if GSX services are not activated prior to trying to move them.

Nobody ever reported this, but it's clearly not possibly caused by GSX, which simply sends "1 (>K:TOGGLE_JETWAY)" to the sim, exactly as if you did it from Axis and Ohs. Strictly speaking, is not even using Simconnect, but rather the Gauges API through its WASM module, since it's not possible to use the "execute_calculator_code" directly from Simconnect, it's a call from the Gauges API, so you need a WASM module to do that, and it's the ONE and ONLY purpose of the GSX WASM module and many other similar modules that needs WASM to do precisely that call.

Clearly, just sending TOGGLE_JETWAY to the sim, cannot possibly have any effect on the actual animation, other than this being yet another MSFS bug.

In any case, default jetways at default airports with NO GSX INSTALLED, still automatically breaks up their moving part from the fixed part (the straight bridge), this is probably the oldest MSFS bug, which we reported to Asobo on June 2022, even BEFORE GSX came out, they confirmed to be able to reproduce it with default airports using default jetways and clearly no GSX installed (it wasn't even out back then), but this bug has survived unfixed for the whole MSFS 2020 life, and has crept into MSFS 2024 unscathed.