Search Issue Tracker
Fixed in 2017.2.X
Votes
0
Found in
5.6.0f3
Issue ID
907717
Regression
No
Time.unscaledDeltaTime returns value larger than Maximum Allowed Timestep in a second FixedUpdate call
How to reproduce:
1. Open the attached "FixedUpdate" project and "test" scene
2. Enter playmode and quickly pause it
3. Observe the second Time.unscaledDeltaTime value
Expected result: Value is smaller than Maximum Allowed Timestep (0.3333333)
Actual result: Value is larger (~1) than Maximum Allowed Timestep (0.3333333)
Reproducible with - 2017.1.0b5, 5.6.1f1
Note: In 5.5 and earlier major versions Time.unscaledDeltaTime returns a large value that is bigger than Maximum Allowed Timestep in the FIRST frame instead of the SECOND frame
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Add comment