only default Jetways at default Airports

[Seralia]

Hey, and again, another Update that messed up something,

all GSX-Jetways are gone since the last 2 Updates.... I have tryed several solutions, Use Updater in FSDT-Installer, Use Live-Updater, Use Offline Installer, click check in FSDT-Installer. Unlink FSDT, Re-Link FSDT, Tryed severel Aircrafts, different Airports. GSX-Jetways are gone. I attach my Log. maybe you can see the Problem.

[Seralia]

Okay, good News, i have found the Solution.

in the manifest.json is an comma not correct. its too much. After deleting it, GSX-Jetways work again.

the manifest.json is located in "Drive:\MSFS\Community\fsdreamteam-gsx-world-of-jetways-2020"

in the manifest.json you will found the lines:
{
  "dependencies": [
    {
      "name": "fsdreamteam-gsx-world-of-jetways",
      "package_version": "3.7.0",
    }
  ],

you have to delete the Red Comma in Line 5, save the file and reload the Sim,

i would take an Airport as an payment 

[kingnorris]

This didn't work for me. I deleted both commas and I still have default jetways. I miss them not connecting to the AI aircraft, and I also miss that warning horn sound, but I'll live with it for now.

[Seralia]

thats sad. i tested it on 2 systems, my buddy had the same issue. and for him - the solution works :S

i have attached my manifest.json. you can maybe download it an compare it with your once,

[kingnorris]

Nope. I copied your manifest and still nada. Like I said, I'll live with it.

[heidjer1]

Seralia's workaround actually works.
After restarting MSFS2020, the GSX jetways are now displayed at standard airports.
However, after various tests at several airports (EDDV, EDDL, EDDN, EDDC), these are not operable or, as in the EDDV example, do not have a building connection.

[kingnorris]

Seralia's workaround actually works.
After restarting MSFS2020, the GSX jetways are now displayed at standard airports.
However, after various tests at several airports (EDDV, EDDL, EDDN, EDDC), these are not operable or, as in the EDDV example, do not have a building connection.

Same issue as before then. Guess I'll stick with the defaults.

[heidjer1]

With GSX version 3.7.1 at EDDE Airport.
Jetways don't have a building connection, and GSX says "Bad Jetway data."
It's a crying shame.

[rallyeandrea]

I have the same problem like heijder1 - at EVERY default airport and that from the very beginning for me. I just bought GSX about a week ago and started with vs. 3.6.8 and this behaviour did not change upto vs. 3.7.1. I disabled all jetways and tried several(!) airports one by one with no success. The services are doing OK but the jetways do NOT. Very disappointing.
MSFS2020 latest versions. All updates installed.
Any help in this matter is very appreciated.

[virtuali]

The comma shouldn't be there, because it's not legal .json format. But I tried it with and without it, and I couldn't find any difference, jetways were visible in both cases, but we fixed the file online anyway.

Now, VISIBLE GSX jetways only means the package has been activated in the sim correctly, but whether they work or not, is a completely different matter. If you see the "bad jetway data" error, it means GSX GOT a "bad jetway data" error from Simconnect, the reasons might be multiple:

This is different depending if you use MSFS 2024 or MSFS 2020:

If you are using MSFS 2020

- The only thing to check is to be sure if you are using a 3rd party or handcrafted default airport, GSX replacement jetways have been DISABLED for that airport, since they are only meant to be used for bare default airports.

- If GSX replacement jetways have been DISABLED for that airport, your problem IS NOT GSX, if the jetway doesn't work, it's completely unrelated to GSX.

If you are using MSFS 2024

- GSX replacement jetways are not even INSTALLED in MSFS 2024 so, again, your problem IS NOT GSX, if the jetway doesn't work, it's completely unrelated to GSX.

If you are using MSFS 2024 or you are using MSFS 2020 and you still got the "bad jetway data" error, the problem might be a conflict caused by another scenery. If you have Navigraph Navdata installed, try without it.

[kingnorris]

The comma shouldn't be there, because it's not legal .json format. But I tried it with and without it, and I couldn't find any difference, jetways were visible in both cases, but we fixed the file online anyway.

Now, VISIBLE GSX jetways only means the package has been activated in the sim correctly, but whether they work or not, is a completely different matter. If you see the "bad jetway data" error, it means GSX GOT a "bad jetway data" error from Simconnect, the reasons might be multiple:

This is different depending if you use MSFS 2024 or MSFS 2020:

If you are using MSFS 2020

- The only thing to check is to be sure if you are using a 3rd party or handcrafted default airport, GSX replacement jetways have been DISABLED for that airport, since they are only meant to be used for bare default airports.

- If GSX replacement jetways have been DISABLED for that airport, your problem IS NOT GSX, if the jetway doesn't work, it's completely unrelated to GSX.

If you are using MSFS 2024

- GSX replacement jetways are not even INSTALLED in MSFS 2024 so, again, your problem IS NOT GSX, if the jetway doesn't work, it's completely unrelated to GSX.

If you are using MSFS 2024 or you are using MSFS 2020 and you still got the "bad jetway data" error, the problem might be a conflict caused by another scenery. If you have Navigraph Navdata installed, try without it.

That's not my issue. I only have one add on airport; KLAS by Fly Tampa. EVERY OTHER AIRPORT is MSFS 2020 DEFAULT, and the jetways DO NOT WORK. They're not connected to the buildings, and I get the Bad Jetway Data message. What I had to do was move EVERY JETWAY over to the disabled list. Now they work but only on my aircraft. The AI's don't get the jetway connections. Nor do I get the alarm, etc. Your response, while appreciated after the lengthy silence, doesn't apply to me.

[heidjer1]

I think Umberto still doesn't seem to have fully understood the whole problem.

MSFS 2020

- If the second comma is set, the "fsdreamteam-gsx-world-of-jetways-2020" directory in the Community folder is displayed as "not installed" in the MSFS Content Manager. This is a fact.
- If the comma is removed, the "fsdreamteam-gsx-world-of-jetways-2020" directory is also displayed as "installed" in the Content Manager. This is a fact.
- The example at Erfurt Airport (EDDE) – which is not a 3rd-party airport in the GSX sense – shows that the GSX jetways cannot be moved and have no connection to the building. This is also a fact.

Umberto, what now?

[virtuali]

I think Umberto still doesn't seem to have fully understood the whole problem.

OF course I fully understood the problem, which should have been obvious from what I just wrote:

The comma shouldn't be there, because it's not legal .json format.

If this is not admitting the problem, I don't know what else is. But that's not the issue, the issue is that I tried WITH or WITHOUT the comma, and it doesn't make any difference for me. But that's not even the point. The point is, this has been FIXED in version 3.7.1, which came out more than a week ago, and what you reported here:

With GSX version 3.7.1 at EDDE Airport. Jetways don't have a building connection, and GSX says "Bad Jetway data." It's a crying shame.

Doesn't have anything to do with the comma, which in 3.7.1 is NO LONGER THERE!

- The example at Erfurt Airport (EDDE) – which is not a 3rd-party airport in the GSX sense – shows that the GSX jetways cannot be moved and have no connection to the building. This is also a fact.

Not only they have the bridge connection, they work just fine: EDDE Gate 51 as in your example:

Fact you are missing the bridge, might indicate you have an outdated version of the jetway package, the one that came before SU16 Navdata update, which we updated with version 3.6.8, so they now 100% match SU16 airport data, that's why they work.

[heidjer1]

Hi Umberto,

Doesn't have anything to do with the comma, which in 3.7.1 is NO LONGER THERE!

I didn't claim that either.
The comma simply prevented "fsdreamteam-gsx-world-of-jetways-2020" from being installed in the sim.

Not only they have the bridge connection, they work just fine: EDDE Gate 51 as in your example:
Fact you are missing the bridge, might indicate you have an outdated version of the jetway package, the one that came before SU16 Navdata update, which we updated with version 3.6.8, so they now 100% match SU16 airport data, that's why they work.

The problem still exists.
I've been using SU16 (1.39.9.0) since July 22, 2025.
I completely uninstalled GSX Pro and then reinstalled it using the offline installer version 3.7.0.
Later, I updated to 3.7.1.
The GSX jetways still don't have a building connection and can't be operated.

What else do you think I should do?

Note: I'm not the only one experiencing this problem!

[kingnorris]

I guess since it works on his PC, the problem doesn’t exist..