Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2020.3.47f1
2021.3.22f1
2022.2.13f1
2023.1.0b11
2023.2.0a9
Issue ID
UUM-33177
Regression
No
The effect of changing the time on RootMotion isn't eliminated when calling SetTime method twice on an AnimationClipPlayable
How to reproduce:
1. Open the attached project “Repro.zip“
2. Open the "AnimSetTimeTest" Scene
3. Enter the Play Mode
4. Click the "SetTime (0.1f) twice" button in the Game view
Expected result: The character’s position doesn’t jump forward or back
Actual result: The character's position jumps forward or back
Reproducible with: 2020.3.47f1, 2021.3.22f1, 2022.2.13f1, 2023.1.0b11, 2023.2.0a9
Reproduced on: macOS 13.0.1 (Intel), Windows 10 (by reporter)
Note: Issue is reproducible in Builds
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
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
After evaluating the impact, workaround and risk associated with fixing this issue, in addition to the current team's bandwidth and priorities, we have concluded that this issue will not be addressed in the foreseeable future.
We are closing this issue as Won’t Fix.
If you feel this issue does not have an acceptable workaround or that you are still blocked by this issue and strongly feel like this should be addressed, reply to this notification to re-open the issue and explain why this is the case. Or, simply log a new bug if the context (version, repro steps) has changed since the original bug report.
Resolution Note (2023.2.X):
After evaluating the impact, workaround and risk associated with fixing this issue, in addition to the current team's bandwidth and priorities, we have concluded that this issue will not be addressed in the foreseeable future.
We are closing this issue as Won’t Fix.
If you feel this issue does not have an acceptable workaround or that you are still blocked by this issue and strongly feel like this should be addressed, reply to this notification to re-open the issue and explain why this is the case. Or, simply log a new bug if the context (version, repro steps) has changed since the original bug report.