Very detailed report. Thanks for this! This bug in my opinion is the worst one in the sim. I first noticed it back when SU 9 was applied I believe.
My question is has anything significant been done by the developers to try and get to the bottom of this? My worry is that if no work has been done on it will it be transferred over to 2024 if the 2020 code is used as a skeleton?
Update: As I stated prior, I was going to try without FSLTL and no traffic.
I did this, and unfortunately the issue remains. Upon arriving at Al Hamad from Lahore (OPLA-OTHH), every single jetway was broken, so that rules out FSLTL or AI traffic causing the issue.
Any update on this? It’s been two years and ten months since this bug was initially reported. Hoping to see a result, as this will be very detrimental for MS2024 and may prompt some users to switch to XP12, as it’s a significantly hampering bug for those that like to fly airliners.
Of course! I’m trying to help them troubleshoot it, sadly no response yet.
I don’t know if anything has been done yet, it’s been two years and ten months and the bug still remains. Hoping it won’t be in FS2024, otherwise I’ll be switching to XP12, as I only fly airliners in flight sim, so it would be a bit pointless for me to buy a sim with broken jetways, since it’s one of the pieces of equipment I use in every single flight. I even use it more than my transponder or radios, as I only fly some of my flights in VATSIM, but just about every flight I do has a jetway at the arriving airport.
Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it?
No
Have you disabled/removed all your mods and addons? 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.
No Mods
Brief description of the issue:
Jetways are misaligned and many not connected to building
Provide Screenshot(s)/video(s) of the issue encountered:
ICAO or coordinates (DevMode > Debug > Display position)
KABQ
Detailed steps to reproduce the issue encountered:
just load into airport and see
PC specs and/or peripheral set up if relevant:
Build Version # when you first started experiencing this issue:
since inception
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:
Here are screenshots of this issue at OTHH. Still occurring, these screenshots were taken today (Sept 24, 2024 1600Z).
Any guidance on how to proceed to troubleshoot this bug yet from someone at Asobo? Willing to troubleshoot on my PC and provide log files and anything else needed.
same issue still seems to be present in the MS2024 alpha as seen in the video of TwoToneMurphy (apparently there is no NDA for the current Alpha build).
This is a reminder that this thread is meant to serve as a bug topic, not a discussion topic. If you are experiencing this issue, please feel free to report your findings using the following template. In addition, if you find workarounds or processes that helped resolve the bug for you, please feel free to post about it, as it may help the team’s investigation. Outside of this, please use an existing or new topic in the appropriate Discussion Hub or User Support Hub to discuss/assist others with this bug.
All other posts will be removed.
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:
Well darn… I already pre-ordered the Collectors Limited Edition or whatever its called… I should’ve got XP12 instead. Fool me twice, I guess I can only blame myself for thinking it would get fixed in 2024
Anyways, to stay on track - I’ve noticed this at more airports: OOMS, OKKK, VVTS,YPPH… so here’s my updated list of affected airports @ adobe dev team if it’s helpful:
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:
Partial Specs & current settings:
Build: AAU3 (v1.38.2.0)
3rd-Party Addons: None, Community Addons: None
i7-12700K, 32 GB 5200 MHz DDR5, Intel Arc 770 (16GB, v32.0.101.6083).
Graphics Tab: Full Screen 3840 x 2160 TAA, Render resolution - 100, AMD Fidelity - 150, VSync - On, FRL - 50% MRR (120 Hz), HDR10 - On, DX12B, TLOD @ 400, OLD @ 200, Other settings - all Ultra or highest setting, except Motion Blur - Off.
Data Tab: Data Connection: All six options - On, Data Limit - Off, Bandwidth - Unlimited, Rolling Cache - Off
Developers Tab: Developer Mode - Off
MSFS Version: MS-Store, Standard, plus All World and City Updates
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:
AMD Ryzen 7 3700X, Nvidia RTX 2080 Super
If relevant, provide additional screenshots/video:
NZCH , Christchurch International (FS version). Startup A320 at the airport, left the gate after half an hour, runway 20, aborted takeoff , returned to suddenly broken jetways.
For Perth YPPH specifically, I had broken Jetways when I arrived after a three-hour flight from YSSY, but when I respawned at the YPPH terminal after a fresh sim restart, the jetways were not broken.
It seems to depend on how long the sim has been running and how far you have flown from your departure airport, at least for some airports affected by the problem…