FSDreamTeam forum
Products Support => Chicago O'Hare V2 for MSFS => Topic started by: vekant on January 06, 2025, 09:03:29 pm
-
Hello, I saw in FAQ GSX that jetways were updated in FSDT airports, but impossible to move the jetway on Chicago, Can you help me please?!
I was with the airbus A330-200 inibuilds, or the 380 FBW.
Thanks,
Kevin,
-
Please provide an example of a gate that doesn't work, and clarify if you are using GSX to guide you to the position.
-
Yes I use GSX, or even directly in the efb inibuilds. I tested the M, M10, M11 gates... none of them work
-
some help please?
-
Please provide an example of a gate that doesn't work, and clarify if you are using GSX to guide you to the position.
All M gates are broken in 2024. Can you please fix?
-
All M gates are broken in 2024. Can you please fix?
Just tested this and, it's neither a problem of GSX ( it never is, when jetway don't work ), or the scenery.
It's a case similar to Asobo Volocopter conflicting with both Paris Airports making jetway to stop. In this case, the culprit it's the Helipad close to Terminal M with the fake ICAO code KE9YA, which due to its proximity with Terminal M is making jetway stop working.
Yes, we CAN temporarily fix this by closing the Helipad from KORD, but it's not really a good solution for what is clearly an MSFS bug, because that would disable the Helipad and to fix this everywhere, every airport developer should close all Helipads close to the terminals, so it's something that must be reported by Asobo.
We'll release an update to KORD anyway, and so most people would assume it was a "KORD bug" ( "they fixed it with a KORD update, it must be a KORD bug!" ), but now we have hard evidence of the bug, we can report it to MS/Asobo for a real fix, because it's not like the Volocopter package that can just be disabled, it's part of the default Navdata, so you can't even disable it (it's Streamed and the file contains other airports too)
-
Has this update been submitted for the Marketplace? See that it is 1.4.8 on FSDT Installer but still 1.4.4 on the Marketplace.
-
Has this update been submitted for the Marketplace? See that it is 1.4.8 on FSDT Installer but still 1.4.4 on the Marketplace.
Not only it has been submitted, but it has been *released* by Microsoft, weeks ago (end of January). However, the 1.4.8 version is only visible from MSFS 2020, for some reason, the MS2024 Marketplace is showing older versions of everything.
Of course we reported this to Microsoft, amd they are looking into it.