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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note (fix version 2021.2):
Fixed in - 2021.2.0a19