only default Jetways at default Airports

[rallyeandrea]

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

You are right - I still have the same problem.
I totally uninstalled GSX as well as the FSDT-installer and started from scratch. Downloaded the FSDT-installer again and then GSX again. I was wondering because files named "...vs. 3.5.9" were downloaded and installed but in the end the installer says that 3.7.1 is installed. Well, I fired up MS2020 and tried Gate 51 at EDDE for myself and there was NO jetway at all in spite of it was activated in the FSDT-installer.
Well, I closed MSFS, ran an update in the FSDT-installer as well as a check. During those procedures many, many files were downloaded-I do not know what exactly but a huge amount. I fired up MSFS again and now I have the NOT connected and NOT working jetway at Gate 51 at EDDE just like heijder1 - so the problem still exists. Probably those jetway-files are not updated.
The whole software and/or server-support is not programmed pretty well, I think. Same like it was with the later FS9 software - terribly complicated to get it running. I hesitated for a long time to buy another product from FSDT but bit the bullet two weeks ago which turns out to be a poor decision.
I am still looking forward getting a solution for this! I only want the software to do what I paid for!

[heidjer1]

The bug hasn't been fixed yet, nor has Virtuali provided an explanation.

Has Umberto gone into hiding, or why isn't he responding anymore?

[kingnorris]

As I said, on his system, all is well, so all he said so far was the usual “ensure third party airports are excluded”.. blah blah.

[BENSON33]

Same problem as previously mentioned, missing the part of the gateway connected to the terminal.
EDDE port 51, GSX 3.7.1 MSFS 2020

[Sevlagoth]

Hi everyone,

I've been using GSX Pro for while now, but never used the forum before.
I always had a great experience and rare issues. After a small break from flight sim for some months and updating to a new PC, I'm also having this issue in MSFS 2020 (I also have 2024, but waiting for Sim update 4, before installing on this PC.

I have version 3.7.1 and jetways are only connected to buildings in standard airports, if I disable GSX Pro jetways all together (then it all works fine), otherwise, jetways only work as intended in addon airports I have. The standard ones, have jetways not connected to the buildings and give the error "You have bad jetway data". This happens in all default airports I tested, like for instance a random one, I assume it's not deluxe edition MMUN (since it looks like crap , not that the Asobo deluxe ones, look much better).

I already tried to uninstall Navigraph, but same result.

As suggested previously by the dev, I'll start the painful process of clearing my community folder completely (leaving only GSX Pro). If it then works as intended, I will add all my add-ons 1 by 1 until I find the culprit, however, if it doesn't work with a clean community folder, it'd be really nice to understand whats going on with so many people and fix this.

I remember back at the start of 2025, all was working fine. I figure some Asobo update messed this up.

By the way on the config of the FSDT installer I have the option "SU 12 Navdata API enabled" = yes. Should this be enabled, since we're already past SU12?

If someone found a solution, please do share. I'll also share my findings (It'll take some weeks...)

In the meantime I have GSX jetways disabled at all airports.

Cheers

[heidjer1]

I've already given it a try.
There are only three GSX-Pro links left in the community folder (fsdreamteam-gsx-xxxxx).

Nothing has changed. The jetways don't have a building connection (tested with EDDE, Gate 51).

It remains a tragedy!

[virtualstuff]

It's pretty simple as for MSFS 2024 SU3 works SU4 don't 

[Sevlagoth]

I've already given it a try.
There are only three GSX-Pro links left in the community folder (fsdreamteam-gsx-xxxxx).

Nothing has changed. The jetways don't have a building connection (tested with EDDE, Gate 51).

It remains a tragedy!

Well, if you already tried with a clean community folder, that spares me the trouble then.

Is there anything at all we can provide from our side to the dev, so we can help him pinpoint the issue? Like logs, or something? This can't just be a coincidence since it's not affecting 1 or 2 people. Navigraph ON/OFF doesn't fix it and now community folder empty with just GSX Pro, has the same result. What else can we try to figure this out?

[virtuali]

Nothing has changed. The jetways don't have a building connection (tested with EDDE, Gate 51).

Of course they have the connection and of course they work, and please stop repeating "I'm not responding anymore", because I not only responded very clearly with a post, but I also posted a VIDEO showing default EDDE Gate 51 with MSFS 2020 working perfectly fine, with the building connections visible and the jetway moving.

And, I posted in another thread a way to check if you maybe have remnants of the old GSX jetway files in the old location we used before adding the MSFS 2020 separate package, here:

https://www.fsdreamteam.com/forum/index.php/topic,33820.msg211555.html#msg211555

The FSDT Installer normally removes them but, if for some reason it couldn't ( permission problems, antivirus blocking the installer, etc. ), if you have an outdated version of the files in the old location, I can imagine they won't work, since they are not the latest version that matches MSFS 2020 SU16 database.

[heidjer1]

Of course they have the connection and of course they work, and please stop repeating "I'm not responding anymore", because I not only responded very clearly with a post, but I also posted a VIDEO showing default EDDE Gate 51 with MSFS 2020 working perfectly fine, with the building connections visible and the jetway moving.

Of course, the jetways still don't work!
Umberto, you're obviously the only one whose jetways work.

As I've reported several times (including by me), GSX-Pro was completely uninstalled. There were no remaining folders or files.
After a complete reinstallation (3.7.0) using the offline installer, the error still occurs. The update to 3.7.1 didn't change anything either. See here:

https://www.fsdreamteam.com/forum/index.php/topic,33752.msg211388.html#msg211388

I haven't been able to find any solution from you yet.

Apparently, all users are stupid, except you.

[virtuali]

Of course, the jetways still don't work!

Of course jetways work.

Umberto, you're obviously the only one whose jetways work.

No, of course they work for all thousands of users that have have not reported any problem! Clearly, a support forum won't show anything from somebody NOT having problems so no, your assumption "I'm the only one with working jetways", is as wrong as it could be.

After a complete reinstallation (3.7.0) using the offline installer, the error still occurs.

You can't do a complete reinstallation with the Offline installer. If you cared to read the other post I've linked, I added the chance a problem on your local Cloudlfare node MIGHT be ONE of the possible MANY possible causes I spent my time to explain.

The replacement jetway files are ALWAYS downloaded. They are NOT included in the Full installer and they are NOT included in the Offline installer. The only way to get the latest version is online with the normal online updater.

Which means, if your local Cloudflare node (and this doesn't mean it's "your fault", unless you work for Cloudflare...) is not updated, you might have an outdated version of the jetway replacement package that was made BEFORE SU16.

So, ANOTHER suggestion I can add to may already long list of things I spent my time trying to help you, is trying to update USING A VPN. That MIGHT fix the problem, if it's really a problem of your local node.

I haven't been able to find any solution from you yet.

I posted MULTIPLE possible reasons and things to check.

Apparently, all users are stupid, except you.

Apart for the obvious repeated mistake of confusing "all users" with the FEW that posted in this thread with all the rest that obviously won't post here to say "it's all fine", but after all the previous insinuations like "putting my head in the sand" or "not responding", when it clearly isn't the case, you are trying to put words in my mouth I never said ?

So, just stop and try to listen, for once.

[Sevlagoth]

Guys comme on.

I have a feeling we're close to figuring this out, let's keep it constructive.

Check the latest developments here: https://www.fsdreamteam.com/forum/index.php/topic,33820.0.html

Lets work together to find the solution. I figure it might have something to do with that missing "FSDT_WorldOfJetways_Lib.BGL" file in the old folder "\Addon Manager\MSFS\fsdreamteam-gsx-world-of-jetways\scenery\FSDT_WorldOfJetways\" (maybe?)

I'll try the VPN suggestion. I'll choose a different country than my own, like lets say USA and press the "Check" button(?) in the FSDT installer? Maybe that forces a full check and update?

Update: Didn't work with VPN pointed to the USA (Or I did something wrong and it didn't trigger any update). I'll try other countries, but what do you suggest Umberto?

Keep it up!

[BENSON33]

I just reinstalled GSX using a VPN (Nord VPN) and always the same. We're still missing that famous FSDT_WorldOfJetways_Lib.BGL file in C:\Program Files (x86)\Addon Manager\MSFS\fsdreamteam-gsx-world-of-jetways\scenery\FSDT_WorldOfJetways.
I'm sure the solution lies in this problem.

[pete_auau]

Just came across this thread checked  that too see if i got  the missing bgl file, went into my folder and  i have the bgl file.  which probably  why i have no issues  with jet ways.  So to those  that have this issue must all have some thing in common with each other

[kingnorris]

“Update using a VPN…”

“Your Cloudfare nodes may be out of date”.

Again, I’m not an IT tech. This reads like a nuclear power code to me.