Author Topic: Jetway MSFS 2024  (Read 3077 times)

vekant

  • Jr. Member
  • **
  • Posts: 65
Jetway MSFS 2024
« 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,

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51917
    • VIRTUALI Sagl
Re: Jetway MSFS 2024
« Reply #1 on: January 07, 2025, 05:38:03 pm »
Please provide an example of a gate that doesn't work, and clarify if you are using GSX to guide you to the position.

vekant

  • Jr. Member
  • **
  • Posts: 65
Re: Jetway MSFS 2024
« Reply #2 on: January 08, 2025, 06:55:31 pm »
Yes I use GSX, or even directly in the efb inibuilds. I tested the M, M10, M11 gates... none of them work

vekant

  • Jr. Member
  • **
  • Posts: 65
Re: Jetway MSFS 2024
« Reply #3 on: January 13, 2025, 06:22:07 pm »
some help please?

airbadger

  • Sr. Member
  • ****
  • Posts: 345
Re: Jetway MSFS 2024
« Reply #4 on: February 23, 2025, 03:59:29 am »
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?

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51917
    • VIRTUALI Sagl
Re: Jetway MSFS 2024
« Reply #5 on: February 24, 2025, 09:01:14 pm »
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)