Search Issue Tracker
Fixed
Fixed in 2023.1.14f1, 2023.2.0b10, 2023.3.0a5
Votes
0
Found in
2023.1.0b18
2023.2.0a23
Issue ID
UUM-43331
Regression
Yes
Fixed Timestep is set to 0.01999999 by default in Project Settings
How to reproduce:
1. Create a new 3D project
2. Navigate to Edit > Project Settings > Time
3. Observe the field "Fixed Timestep"
Expected result: By default, the field is set to 0.02
Actual result: The field is set to 0.01999999
Reproducible with: 2023.1.0a23, 2023.1.0b18, 2023.2.0a23
Not reproducible with: 2020.3.48f1, 2021.3.28f1, 2022.3.5f1, 2023.1.0a22
Note: The version before regression had a Time Project Settings window with more options, but this was reverted to previous options. The reversion of this decision might've been the cause of this regression.
Notes:
The code change: [https://github.cds.internal.unity3d.com/unity/unity/commit/094d2827b30be92934a4c31782cd66703366498a]
- overall the DrawFixedTimeAsFloat method just needs a rounding call to clean this up. It's not necessary, but it seems like it might be nice to have and this is such a simple thing to add (Assigning task to myself: I haven't worked in trunk in ages and I'm using this to re-learn the new process)
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
- Crash on mecanim::SetValueWeight when switching the AnimationMixerPlayable connection with Animator's UpdateMode set to "Animate Physics"
- The "StringComparer.InvariantCultureIgnoreCase.GetHashCode()" returns different Hash Codes for the same word with the only difference being case sensitivity in WebGL
- 2D Light Textures show the lights of any 'blend style' index higher than theirs (if present) when they aren't visible by the Camera using Render Graph
- [SpeedTree] Wireframe mode not rendering correctly ST assets
- Light2D affecting only the Default Sorting Layer will also affect any Custom Lit Sprite not on that Layer when using Render Graph
Resolution Note (fix version 2023.1.14f1):
A fix for this case Landed in 2023.1.14f1