Search Issue Tracker
By Design
Votes
1
Found in
2022.3.65f1
6000.0.55f1
6000.2.0f1
6000.3.0a4
Issue ID
UUM-113892
Regression
No
Object motion is affected by incorrectly added rotation motion when importing animations
Reproduction steps:
1. Open the attached “IN-111019.zip” project
2. Open the “Start” scene
3. Enter Play mode
4. Observe the Game view
Expected result: Both characters have animations and go backwards
Actual result: The “anm_strafe_backward” GameObject on the left, goes up instead of backwards
Reproducible with: 2022.3.65f1, 6000.0.55f1, 6000.2.0f1, 6000.3.0a4
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes:
- Additionally, tested by reimporting the FBX each time testing, but no difference was observed
- The problematic GameObject is the “anm_strafe_backward”. The edited version "anm_strafe_backward_noMotionQ" removes rotation motion and the character goes correctly backwards, as designed in 3DS Max. The animation can be opened in Blender, and seen that there is no rotation motion at all on the root bone "priest_m_base_Root"
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
The source asset has a pre-rotation of 90 degrees on the bone used as the source of root motion, and Unity is interpreting the root motion in accordance with that configuration.
Removing that pre-rotation fixes the issue.