Jetway Control Not Working via Tablet at KMIA (Default and Custom Airports)


ISSUE DESCRIPTION

Description of the issue:

MSFS2024 KMIA, Miami International Airport
Jetways cannot be operated via the aircraft tablet at Miami International Airport (KMIA); it only works through the ATC Communication menu. Initially, suspected this might be related to Glideslope Pro custom scenery of KMIA. However, after further investigation, confirmed that the same issue occurs at the default KMIA airport as well.

FREQUENCY OF ISSUE

every time on sim load

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

1.Load on KMIA (Glideslope Pro or Default) on Gate Parking with MSFS 2024
2.Try to communicate jetway via Tablet
3. works through the ATC Communication menu

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant:

[PC Only] Are you using Developer Mode or have you made any changes to it?

[PC, MSFS 2020 Only] Are you using DX11 or DX12?

[PC Only] What GPU (Graphics Card) do you use?

[PC Only] What other relevant PC specs can you share?

MEDIA

Please add a screenshot or video of the issue occurring.

[END OF FIRST USER REPORT]


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

Which aircraft using a tablet to trigger a jetway are you having an issue with ?. Please detail reproduction steps as much as possible. Without that it is harder for devs/users to try reproducing your issue.

I have tried almost all aircraft with tablets available in the simulator, including the PMDG 777. To reproduce the issue, simply load into Miami at any jetway-equipped parking spot and try to connect the jetway using the aircraft’s tablet. This problem occurs both at the default Miami airport and in the Glideslope Pro scenery

I am having the same issue. Doesn’t work at all.

Do you have the same issue if you follow the OP’s steps to reproduce it?
• yes

Provide extra information to complete the original description of the issue:
• tested with the A320 v2 at KMIA gate 155

If relevant, provide additional screenshots/video:


Do you have the same issue if you follow the OP’s steps to reproduce it?
• Yes

Provide extra information to complete the original description of the issue:
• Tested with the following parameters:

  1. Results are identical after testing on at least one gate on each apron.
  2. Jetways failed to connect using the EBF or GSX for the ini A330, FBW A380, and Asobo 738M. (Jetways did connect using EFB and GSX at default KATL, KCLT, and ini KLAX - Have also been flying the ini A350 for the past few days with no jetway issues at multiple airports).
  3. Jetways failed to connect on LVFR, Glideslope Pro, and default KMIA sceneries (with sim restart after disabling each one.
  4. Jetways failed to connect after unlinking GSX Pro.

I spent several hours trying to resolve this. As best as I can tell, the jetways will not animate unless the ATC menu option for passenger boarding/deboarding is selected with the default scenery. I tried to use payware scenery and this caused a CTD twice. Selection of the jetways in the EFB’s indicates the jetway has been toggled but the jetway will not animate and the EFB will not indicate a successful attachment. Selection of the jetways in GSX indicates the jetway is operating, but as with the EFB, it will not animate (a jetway operation complete message will appear in spite of the fact that the jetway never moves). At first I thought this was a scenery issue and then a GSX issue (although I find most GSX issues can be solved with an update which I did try here); however, upon discovering that the default scenery had the same issue and it was seemingly isolated to KMIA, I now assume it is just a small bug with the airport.

If relevant, provide additional screenshots/video:
• No relevant screenshots. All I could show is an unattached jetway.

Same here!