Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.3.0f3
Issue ID
1002461
Regression
No
FixedUnscaledDeltaTime and unscaledDeltaTime return huge values on the first frame
To reproduce:
1. Open the project, attached by the tester (UnscaledTimeBug.zip)
2. Open the "scene" scene
3. Enter Play mode
4. Observer the console
Expected: unscaled times are not as large and preferably the same as regular deltaTime and fixedDeltaTime
Reproduced in 5.6.5p2, 2017.1.3p1, 2017.3.0f3, 2018.1.0b8, 2018.2.0a1
Comments (1)
-
dgoyette
Jul 17, 2018 00:09
This may be somewhat obvious, but it appears the value of unscaledDeltaTime is equivalent to the time between pressing Play, and the time the first frame is rendered. So, all that startup time is added to the first frame's unscaledDeltaTime.
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
We are deprecating the current input system and replacing it with a new one. We have logged these bugs in the new input system Github page.
You can download the new input system here: https://github.com/Unity-Technologies/InputSystem