Jetway Samples from SDK Completely Broken

I just wanted to double check something with an untouched jetway hood animation from the SDK samples and found out that the hood animation from the sample is completely broken.

Neither the Blender file itself nor importing the GLTF works.

Please fix this. Jetways are by far the most complex, confusing, and difficult thing to master in scenery creation and for new devs who don’t have any working Jetway yet this is completely useless.

Blender file

blender_2HGaNdVkaA

Imported GLTF

blender_5CNb8AYzjp

1 Like

Hello,

This has been logged in our backlog.

I will let you know when I have some updates to share.

Regards,
Boris

2 Likes

Hello,

Sorry for the delay.
This has been fixed in the SU4 sdk samples (1.5.7).

Let me know if it’s now working as expected please.

Regards,
Boris

Hello @Boris , still getting the same issue in Blender 4.2LTS with the Samples V1.5.7.

I can confirm nothing has changed really. The animation is still broken. This is not fixed. If anything it is even more broken now because everything is duplicated as this now includes LODs which are named incorrectly.

This is with the samples from the SDK update 1.6.4
Blender Version 3.6.12

Animation from opened Blender file:

And imported GLTF:

Exactly the same result as before.

Hello,

Can you check using the sdk su5 flighting 1.6.6.0 and tell me if it’s now working as expected ?

Regards,
Boris

Hi @Boris

It is still broken

What do you mean by “it is still broken”?

Which Blender version are you using?

Also, did you open the .blend sample directly, or did you import the .gltf file? I’m asking because the model looks strange in your screenshot.

Here, I just opened the .blend with blender 4.2 LTS and this is what I see :

Regards,
Boris

I am using 3.6 and 4.2. I opened the .blend file.

If you extend the the hood all the way you can see how it does not have the accordion effect, as it can be seen in the picture I attached above.

Indeed the hood animation is broken when exporting using blender.
I logged the issue in our backlog.

Thank you,

Regards,
Boris