Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.5.0f3
Issue ID
873528
Regression
Yes
Time class values are not 0 and can be manipulated before entering Play mode
Reproduction Steps:
1. Open attached project "873528 - TimeClassBug".
2. Go to "Test" -> "Time Bug" in the menu.
3. Observe how the Time values are not 0 before entering Play mode.
4. Move around the "Time Bug" tab in Unity Editor.
5. Notice how Time values continue to change. (GIF attached)
Expected result: Time values (besides frameCount) should be 0 before entering Play mode.
Actual result: Time values give out unknown values before entering Play mode.
Reproducible on: 5.6.0b5, 5.5.1f1
Not reproducible on: 5.4.3p3, 5.3.7p2, 5.2.5f1
Regression introduced in: 5.5.0f3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment