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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment