Model disapears on additive animation group (GLB export)

Hello community,

I’m trying to export a GLB file from a model i animated in babylon using additive animations

the animations works just fine until i export it into glb and open it in sandbox the model is completely hidden.

let me explain a test case i created into a playground

  • 2 animations groups : only one of them is additive
  • 1st one has a translate animation and the 2nd has a jump animation
  • in addition to the translate i have a quaternion and scaling animation (that i’m not really animating, same values in the 2 keyframes)

when i remove the scaling animation or enter 2 differents value keyframes, everything works as expected.

what i’m assuming is with the additive animations magic, something is transforming the scaling to 0,0,0 resulting the model to be hidden,

Can anyone help me figure out what’s happening noting that having the scale animation (whether with different keyframe values or similar) is a must.

here’s a link to the playground :

the model will automatically download on animation end.

cc @Cedric

I’m adding it to my todo list.


I’m debugging it ATM.
BTW, thank you @MeshSlayer for the invaluable playground.

1 Like

Thanks @Cedric for your time !
looking forward to hear from you, i’ll make sure to always provide you with any additional informations to help the debugging progress


PR Additive animation with scaling by CedricGuillemet · Pull Request #12513 · BabylonJS/Babylon.js · GitHub

EDIT: I’m closing the PR. I’m not happy with the result. I think the issue is in the gltf exporter instead.


ping @Guillaume_Pelletier

just readed the thread.
My understanding of the additive animation under Babylon js is that


is “just” baking the animation. Once done, it’ should be played and saved as it into gltf.

So if you have different behavior once exported and loaded into/from the GLTF, it may be the Serializer or the Loader.
We may have a look with another loader to see if it behave similar (i guess you already done this step)
Then we may using the Visual code tools to have a look into the GLTF data, seeing if the data are corrupted in a way or another. Using the animation editor into the SandBox is also very usefull for these case (what did you find there ?)
After that we can finally debug the code with a better idea of where to search :slight_smile:
let me know how i can help to speed up the process.
What i believe is once baked, the scale animation is NOT played anymore (if you are looking into the animation curve editor, playing the scale make the sphere disapear, nothing to do with the export).
The export only highlight this by exporting the 3 animations separately without taking care of the

        animationGroup.isAdditive = true;

property or the fact the animation is one keyframe only.
So i’m agree it’s might be a missing feature into the exporter and a strange behavior into the MakeAnimationAdditive call which is changing the source animation scale to zero
(but i also think the exporter was written before the additive capabilities).

1 Like

Thanks @Guillaume_Pelletier for your response,

i totaly agree.

after doing some investigations, if you take a look at the playground i provided and log the keyframes, you may notice that the scaling animation has Vector3.Zero already

so playing animations with an isAdditive flag maybe compute the keyframes in a way that we coudn’t notice the issue in the playground.

in conclusion i think the exporter doesn’t fully support additive animation.

also correct me if i’m wrong, isn’t multiple animationGroups are supposed to be exported as a single animation ? (based on the docs) it’s not the case here :thinking:

As far i readed the code (that I did not write), your assumption is right.
is the place where the export happen and it add every animation, one by one, to channels, which might be the normal behavior for an exporter. There is no generic reason to bake the animation prior to export.

hi there, I’m having the same issue here.
Is there some workaround to make the export work?
If not, is there any solution in mind to support this feature in the exporter?

please share a sample in order to give us a better view of your issue.