Animation Editor: Animation Import Fails Due to Invalid clamp Arguments

I’m currently unable to import an animation into Roblox Studio’s Animation Editor.

When attempting to import the animation, the import fails and Studio outputs the following error:

“[Roblox][builtin_AnimationClipEditor.rbxm.AnimationClipEditor.Src.Components.EditorController] builtin_AnimationClipEditor.rbxm.AnimationClipEditor.Src.Components.EditorController:236: invalid argument #3 to ‘clamp’ (max must be greater than or equal to min) - Edit”

Expected behavior

The animation should import successfully into the Animation Editor and retain the animation data from the source file, including the expected root motion/movement.

A private message is associated with this bug report

Hi there, thanks for your report!

At first sight, it seems like your error comes from the UI rather than the data.
If this error happens for other clips as well, could you please try to reset your Studio layout (last option of the Window menu, “Reset Layout”) and see if that fixes the issue?
If it’s only for this clip, or resetting the layout doesn’t help, could you please attach the place file in a private message? We couldn’t reproduce the issue with the fbx file you already provided.

Cheers!!

Hey!

Thanks for the response! I tried resetting the Studio layout, but unfortunately that didn’t resolve the issue.

I was able to fix the problem by reimporting the entire rig into Studio and then importing the animation again.

While investigating the original rig further, I found something else interesting. The rig had a single bone that I had inserted directly within Studio as a child of “root”. After deleting that bone, the animations started importing correctly on the original rig as well.

The bone wasn’t being used by the animation, so I’m not sure why simply having an additional child bone under “root” would affect the animation import or root motion.

You should be able to reproduce this using the original FBX I sent. It seems that simply inserting an additional bone as a child of “root” is enough to cause the issue. If you cant, I have attached the original problematic place within the private message.

Thanks!

Glad you found a solution!

We’ll have a closer look at the place you provided. Thank you!