Version: * 1.3.13.0*
Frequency: Consistently
Severity: High
Similar MSFS 2020 issue:
Bug description: Heliports close to an airport terminal might prevent Jetways to work. We suspected this was a problem since 2020, because of the very well known issue of the Volocopter packages that prevents Jetways to work at both Paris airports, with users confirming it to be fixed by disabling the Volocopter package. Now it happened to one of our sceneries, so we could isolate it, and also issue a temporary workaround on our side.
Repro steps: The Helipad KE9YA is very close to KORD Terminal M, and this seems to cause most Jetways at that Terminal to stop working. They are not simply inactive, they are not even seen as available from the standard ATC Menu, no Jetways can be called from the Ground Services menu. The same Jetway model, when called from a Terminal much farther away from the Heliport, works.
We could fix this by closing the airport in our own KORD scenery, by adding the following line to the airport source code:
<Airport country="United States" city="Chicago" name="Chicago-O'Hare Intl" ident="KE9YA" closed="TRUE" lat="41.977308" lon="-87.884452" alt="201.168" magvar="3.0" trafficScalar="1.0" airportTestRadius="100">
This would effectively disable the KE9YA Helipad, so on the next restart it wasn’t selectable anymore from the Map (when flying an Helicopter, of course), but it also fixed the disabled Jetways problem when starting a flight at the same gate with an airplane.
While this workaround work, we believe this should be investigated, otherwise other airport developers scratching their heads why jetway are not working in their airport, might start closing all Helipads around there, so it’s not really a solution for users flying Helicopters.