Version: 1.6.5.0
Frequency: Consistently
Severity: High
Similar MSFS 2020 issue: Some longstanding Jetways issues
Bug description: Jetway links not connected when starting a flight. The screenshot below is at default LIMC (Milan Malpensa), which is a bare default autogen airport, using default Jetways.
Hi,
Thanks for reporting, we are currently working on a fix, it is a SU4 regression
Regards,
Xavier / Asobo studio
Hello
You could try using a workaround to fill the gap. In the FS20/24 Scenery Objects there is an object named “Boarding_Ramp_White_02” that you can position between the disconnected jetway and the jetway link. I have increased its scale to 1.45 with the Gismo. You can then duplicate the object if required to position them in a single file. I did this for the airports I’ve worked on and simply forget about this problem.
Regards.
Xavier
I reported this mainly to point out a problem that has happened since MSFS 2020 that affects all default airports and any scenery that uses the “proper” jetway link method.
We never those objects in our airports, because they are mainly designed for airports generated automatically (few library objects that can fit almost everywhere), but in a custom scenery, it’s probably best to model custom static bridges anyway.
I anderstand and respect your point of view as a scenery designer. I don’t have the talent to design my own objects and so I do my best to circumvate the obstacle..
