Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.0.3
Issue ID
1314501
Regression
No
[Animation rigging] Animation sometimes twitches after Transfering Rig motion to skeleton
Reproduction steps:
1. Open the user's attached project and Scenes/Levels/ScarfAnimations scene
2. In the Hierarchy window, select Scarf/SM_Scarf_02/Scarf_02 and Window/Animation/Animation to open its Animation window
3. Press on the Animation time track
4. In the Hierarchy window, select SM_Scarf_02 GameObject
5. In the Inspector window, right-click on the Rig Builder component and select Transfer motion to skeleton
6. Play the animation and observe Scarf_02 GameObject
Expected result: Animation is played smoothly
Actual result: Animation twitches sometimes
Reproducible with: 1.0.3 (2020.2.7f1, 2021.1.0b9, 2021.2.0a7)
Could not test with: 2018.4.32f1, 2010.4.20f1 (could not downgrade), Animation Rigging 1.0.2 (NullReferenceException when playing animation)
Notes:
1. The twitch happens at random times
2. Twitches are not visible when playing animation frame by frame in the preview
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Audio Mixer does not change volume when lowering volume on an Audio Mixer loaded from AssetBundles
- Error “Value cannot be null. Parameter name: key UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)” thrown and Addressables build fails when "Include in Build" is disabled and using Addressables For Android package
- “error CS0433: The type 'CodeBinaryOperatorType' exists in both 'System.CodeDom and 'System" compilation errors are thrown when opening a specific project
- Metal Vertex Shader warning is being thrown when creating a VR Template Project
- Asset database warning is thrown when declaring font variable in the USS text file
Resolution Note:
This is to be expected because of the source animation that has been provided when transferring rig motion to skeleton.
Taking a look at the source animation provided for the damped transform constraint (SM_Scarf_02), you can notice jumps in the rotation. While this may evaluate properly when sampled frame by frame, baking this data in between frames will definitely cause some issues.
To fix this, simply clean up the animation on the SM_Scarf_02 node and unroll your rotation curves. You'll have much better results when baking to clips afterwards.