Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.0f2
2019.1.0a1
Issue ID
1110765
Regression
No
Default Fixed Timestep value is set to 0.02 (50Hz) instead of 0.0167 (60Hz)
How to reproduce:
1. Create a new Unity project
2. Open Edit > Project Settings > Time
Expected result: Fixed Timestep value is set to 0.0167
Actual result: Fixed Timestep value is set to 0.02
Reproducible with: 2017.4.18f1, 2018.3.2f1, 2019.1.0a13
Comments (1)
-
knthzh
Oct 19, 2024 21:17
Now that Fixed Timestep is saved as a Rational in Unity 6 (making floating point inaccuracy no longer an issue), are there any other objections for making 60Hz the default?
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note:
It is set to 50Hz because of the floating point inaccuracy that would be introduced if it was at 60Hz.