Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
5.3.1p4
Issue ID
764454
Regression
No
When root motion is applied, playing animations automatically and playing animations through script the end position differs
Reproduction steps:
1. Open the attached project
2. Open and play "Test" scene
3. Click on "Play" button
4. After the animations are finished notice that the coordinates on the top left corner are about (14.5, 0.5) (coordinates differ each time)
5. Press the "Reset" button
6. Click the "Advance" button 5 times to cycle through all the animations (make sure each animation finishes)
7. Notice that coordinates are (15.0, 0.0)
Actual result: When root motion is applied, after playing animations one after another through script, balls position is different than after animations are played automatically.
Expected result: Playing animations through the script and playing animations automatically the balls position should not differ.
Reproduced on: 5.1.4f1, 5.2.4f1, 5.3.1p4, 5.4.0b3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Add comment