Search Issue Tracker
Fixed in 2021.2.X
Votes
1
Found in
2019.4
2020.2.1f1
2020.3
2021.1
2021.2
Issue ID
1318053
Regression
No
Resolutions returned by Screen.resolutions differ between Editor and Build
How to reproduce:
1. Open the attached project named "Case_1318053"
2. Enter Play Mode and observe the Debug.Log messages (All resolutions have a refresh rate of 60)
3. Build the Project
4. Run the build and observe the Player log which is located in the appdata folder
Expected results: The build returns the same resolutions, with the same refresh rates
Actual results: The build returns resolutions with the refresh rate of 30 and 59
Reproducible with: 2019.4.22f1, 2020.3.2f1, 2021.1.1f1, 2021.2.0a11
Notes:
1. According to https://docs.unity3d.com/ScriptReference/Screen-resolutions.html Screen.resolutions should always contain resolutions at 60 Hz which is the current behavior in the Editor
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
- Rotation tool Gizmo is stuck in the Scene View when unchecking/checking the "Orient" node in the VFX Graph and the Scene view is visible
- The Editor opens when the window is closed right after launch
- Frame Debugger's Hierarchy is not navigable when connecting it to the project built with the Volumetric Fog
- The number of SetPass Calls is increasing when attaching the Frame Debugger to the Player
- Scrollbar briefly appears in the Package Manager during installation process even when the package list is too short to require scrolling
Resolution Note (fix version 2021.2):
Fixed in - 2021.2.0a19