Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
0
Found in
2020.3.47f1
2021.3.24f1
2022.2.17f1
2023.1.0b14
2023.2.0a12
Issue ID
UUM-33952
Regression
No
AnimationStream.deltaTime and Time.deltaTime are not equal when the Time scale is set to > 0.85
Reproduction steps:
1. Open the attached "repro_IN-38581.zip" project
2. Open the "Assets/Sample" Scene
3. Enter Play mode
4. Observe the two figures in the scene
Expected result: The two figures are moving in the same direction
Actual result: The two figures are moving in different directions
Reproducible with: 2020.3.47f1, 2021.3.24f1, 2022.2.17f1, 2023.1.0b14, 2023.2.0a12
Note:
- Reproduction may be inconsistent, had to unplug the laptop’s charger for consistent reproduction
- If the figures are not visible, observe the Console, specifically the tuple which contains the transform coordinates. They are expected to be equal
- If Time scale is set to <= 0.85 or if executing Play mode Frame by Frame, this issue is not reproducible
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
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.
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.