Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2018.2.0a1
2018.4
2019.2
2019.3
2020.1
2020.1.0a17
Issue ID
1216135
Regression
Yes
Unity freezes when Time.timeScale is set to NaN
How to reproduce:
1. Open attached project "Case_1216135" and load "Scene"
2. Press Play
3. Click Tab on your keyboard
Expected result: Error is thrown in the console
Actual result: Unity freezes
Reproducible with: 2018.2.0a1, 2018.4.17f1, 2019.2.20f1, 2019.3.0f6, 2020.1.0a22
Not reproducible with: 2017.4.36f1 (throws error in console)
Notes: In order to get NaN, division 0/0 is used, but as this throws an error, a variable is used as a denominator.
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
- FP32 is used for a temporary when compiling a shader for GLES or Vulkan
- The highlight that was created with Highlighter.Highlight does not disappear when the window is closed with the element
- [URP] CommandBuffer warnings thrown while debugging Depth Overlays with Post-processing enabled in Rendering Debugger
- hlslcc: float image atomics don’t work
- [Apple silicon][M1] Game view FPS is very low when the view is moved to an external display
Resolution Note (fix version 2020.1):
Fixed in: 2020.2.0a12
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.1f1