Are you rotating the part that’s directly connected to the Root? If so, then this is expected. If you want to code in movement, rather than setting the weight of a right, left, forward, and back animation, you should set the C0 instead.
nope, im moving the torso bones. i noticed that i cant even turn a default r6 character more than 180 degrees when i have the animation editor set to CurveAnimation clip. everything works normally when using animation editor without it, but i want the CurveAnimation mode for smoothness
This is a curve animation issue, it’s probably because when the orientation resets, the engine decides to interpolate the values in a way to get to the end position weirdly. Super annoying.
Can you please send us a copy of your rig and the animation that causes the issue so we can have a closer look?
Can you also describe how you created that animation? Was it imported from an external tool, or was it created from scratch? Did you promote a KeyframeSequence Animation to a Curve Animation, or did you create it directly with curves? Did you convert from Quaternions to Euler angles at any point?
This bug is not unique to this rig and I have experienced it with basically every rig I use.
Replicate:
Create an animation for any rig, I used a bone rig for this.
Convert to CurveAnimationClip
I’m not sure of the exact cause, but when I try and rotate a limb/bone over 180 degrees on any axis it just starts spinning out.
This doesn’t happen with regular animations, just when I use the CurveAnimationFeature. It has also happened to others, so it’s not a problem for me alone.
If you’d still like the rig, let me know and I can provide it, but like I said, it happens with every rig
Can you please check in the settings menu (the cog wheel on the top right side of the ACE) if you are using Quaternions or Euler Angles?
If you are using Quaternions, this is expected. Quaternion rotations always take the shortest path between two orientations, so you cannot rotate by more than 180 degrees. What you need to do in that case is add one intermediate key. Euler Angles don’t have that limitation.
This is a very interesting problem. The issue is that the draggers don’t have any idea you are animating from an angle of about 135 degs to an angle of 200 degs, they just see an angle of -160 degs, because that is the orientation of the local coordinate system in the global system. If you switch to the curve view, the graph for the Z angle of the rotation should make it pretty clear: it goes from 0, to 135, then to -160.
We will see how we can improve the draggers logic to take the previous keyframe into account.
In the meantime, as a workaround for now, you can manually edit the angle by either adding 360 degrees, or subtracting 360 degrees, depending on the way you rotate.
Using quaternions, instead of Euler Angles, would also solve this issue.
