FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: asegm08 on May 17, 2025, 12:33:00 am
-
Have now had several people in various groups I circle report what I encountered. Activating jetways in SU3 2024, causes the sim to the jetways to disappear.
-
Hello,
i'm having a problem with the jetways in Aerosoft's new 2024 EDDL scenery.
When I click on "Operate Jetways" in the GSX menu, the jetway disappears.
The profile is the one provided by Aerosoft.
The same problem occurs with other profiles from Flithsim.to.
Even restarting the cuatl does not help.
Best regards
Peter
-
Hi,
Today I tried MSFS2024 SU3 Beta, and spawned to LOWW Gate F1 in the IniBuilds A350. Everything looked absolutly fine on the walkaround, and the Jetway was still there..... upon entering the Cockpit I activated the Jetway through GSX via the Toolbar. It said Jetway operating but in fact it vanished and did not come back - some WASM error. Hope this can be fixed soon as it worked flawless in SU2.
This is reproduceable for me, If you need any other details please don't hesitate to contact me....
kind regards
liketofly
-
Looks like a SU3 beta bug. You can work around by activating the jetway through the default ATC comms menu
-
Several threads about this already here, looks like a SU3 beta bug. You can work around by activating the jetway through the default ATC comms menu
-
Several threads about this already here, looks like a SU3 beta bug. You can work around by activating the jetway through the default ATC comms menu
-
Many Thanks
-
My opinion but the mod-soldiers dont consider it as a bug and moved the topic into 3rd party forum.
-
Intersting, as I have a comparable issue in SU2 but only on specific sceneries (RKSI from PacSim e.g.). Was reported weeks ago, nothing happened, because it is OF COURSE not a GSX issue.
-
Intersting, as I have a comparable issue in SU2 but only on specific sceneries (RKSI from PacSim e.g.). Was reported weeks ago, nothing happened, because it is OF COURSE not a GSX issue.
never, how dare you ^^
but thats might result in... nothing: Msfs claims not my fault, gsx as usual no its fault. no one's fault, no one cares.
but seriously: in this case i bet on MSFS who needs to fix it, they did the update
-
Yes, this is an SU3 beta issue. There are a few posts on the MSFS forums about it. I noticed this at both Flightbeam NZAA and FlyTampa YSSY.
-
Yes, this is an SU3 beta issue.
It is not, or we have two similar bugs now. I and others reported it already pre-SU2, I was not even in the beta. But of course, it was ignored or the cause was not GSX, as always. Well, as long as default ATC command works, I can live with this bug.
-
More than an SU3 Beta bug, it's a Simconnect bugfix which came in SU3 Beta almost 3 years later after we reported it, but in this case broke the GSX code, which was done under the assumption that bug would stay.
It's fixed in the GSX Beta channel.
-
More than an SU3 Beta bug, it's a Simconnect bugfix which came in SU3 Beta almost 3 years later after we reported it, but in this case broke the GSX code, which was done under the assumption that bug would stay.
It's fixed in the GSX Beta channel.
Is this the same bug that makes the jetway connectors disappear upon arrival at basically any airport that has a connector attached to the jetway object? If so wow, we also reported an issue in their dev forums it feels like a decade ago, we just gave up.
-
Is this the same bug that makes the jetway connectors disappear upon arrival at basically any airport that has a connector attached to the jetway object?
That's another bug, and it's not even required to make a flight to replicate it, you can simply enter the Drone/Showcase camera, go around the airport, and it's likely you'll see some jetway links not extending. It seems as if the sim extends only those close to the gate you are selecting, but forgets to update the ones farther away, and also on arrival.
Yes, we reported it to Asobo in early 2022, happening on default airports using default jetways, months before GSX even came out.
-
Is this the same bug that makes the jetway connectors disappear upon arrival at basically any airport that has a connector attached to the jetway object?
That's another bug, and it's not even required to make a flight to replicate it, you can simply enter the Drone/Showcase camera, go around the airport, and it's likely you'll see some jetway links not extending. It seems as if the sim extends only those close to the gate you are selecting, but forgets to update the ones farther away, and also on arrival.
Yes, we reported it to Asobo in early 2022, happening on default airports using default jetways, months before GSX even came out.
yeah, we use default jetways on our freeware sceneries, but like I said, we just gave up on them fixing it.
-
Weeks later, sadly the situation is unchanged. But I stumbled over a content.xml modifier tool over at flightsim.to allowing to disable all heliports worldwide at once. As soon as I have time, I will try this once to see if this renders those affected jetways operative again.
Really annoying bug, and if FSDT is sure that it is Asobos or Scenery Devs fault and vice versa, no solution in sight...
-
Ok, sadly simply deactivating heliports worldwide is not sufficient. The heliport needs to be fully excluded from loading. Over at avsim, someone did it for NZAA and bam! GSX jetway commands work again. So it really seems that for every airport having issues,.one need a fully excluded nearby heliport. E.g. around RKSI, three are situated. So either the dev or someone else would need to deactivate those...
-
I'm experiencing multiple issues with latest release ranging from jetways not operating to GSX menu failing to launch in continuous loop.
-
What me still puzzles, is the fact that the default way of calling for jetway movement via ground services ATC menue always works. Even if the nearby heliport is active. The only thing that does not work is "operate jetway" via GSX menue. So maybe Umberto can still take another look on it? There must be a difference how jetway movement is triggered when using the default ATC command vs. the way GSX moves the jetway (in MSFS2024).
-
Really annoying bug, and if FSDT is sure that it is Asobos or Scenery Devs fault and vice versa, no solution in sight...
I don't know what you are trying to say here. If we are "sure" it's an Asobo bug, it's because it is, and we reported it in April, and you can see several other developers confirmed it:
https://devsupport.flightsimulator.com/t/heliports-close-to-an-airport-terminal-might-prevent-jetways-to-work/13326
-
Sure, but if devs would take care about customer support instead of blaming Asobo, it would take them 10mins to provide small fixes that disable nearby heliports for time being. Instead the community has to jump in again providing such little fixes. Annoying, as I wrote...
To make it clear, this is not an attack on FSDT, as you DID include those fixes for affected sceneries. It is more a general statement.