Search Issue Tracker
Fixed in 2022.2.0b15
Fixed in 2022.2.X, 2023.1.X, 2023.2.X
Votes
2
Found in
2022.2.0a17
2023.1.0a1
2023.2.0a1
Issue ID
UUM-2180
Regression
No
Motion property of FBX import applies Root Motion Node to all Animation clips when any Animation clip changes Motion property
How to reproduce:
1. Open project "FBXMotionSelection"
2. In the Project window, select FBX "Knight" (in Assets folder)
3. In the Inspector, select the Animation tab and select any animation clip from the Clip selection list
4. In the Animation tab, Scroll down to the "Motion" property, expand it, and choose a Root Motion Node that is not <None>
5. Hit Apply in the Animation tab
Expected results: Root Motion Node is only applied to the selected Animation clip
Actual results: Root Motion Node is applied to all Animation clips
Reproducible with: 2019.4.29f1, 2020.3.15f2, 2021.1.16f1, 2021.2.0b7, 2022.1.0a5
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
- Build fails when building a project containing an 18+ dimension array with IL2CPP
- [Android][Sentis] Human poses are not detected when using the BlazePose model
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
Resolution Note (fix version 2023.1):
The documentation was updated : https://docs.unity3d.com/Manual/class-AnimationClip.html
Resolution Note (fix version 2022.2):
The documentation was updated : https://docs.unity3d.com/Manual/class-AnimationClip.html