Search Issue Tracker
Fixed in 2018.3
Fixed in 2019.1
Votes
0
Found in
2017.2.0f3
Issue ID
975924
Regression
No
Screen.setResolution() ignores prefferedRefreshRate variable and sets it to what is set as refresh rate through Windows
Steps to reproduce:
1. Download and open the attached project on a setup with a monitor capable of high refresh rates(120, 144hz...)
2. Build for standalone
3. Select any of the resolutions from the drop-down list with a lower than native refresh rate
Expected result: refresh rate gets set accordingly
Actual result: refresh rate gets set to native set in Windows settings
Reproduced on 2017.2.0f3, 2017.4.12f1, 2018.3.0b5, 2019.1.0a3
Verified FIXED 2019.1.0a14, 2019.2.0a1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [macOS] Empty error appears in the Console window when certain files are present in the project with macOS Catalina
- Builds that contain terrain using the Nature/Terrain/Standard shader produce errors when run in headless mode
- When the registry value for "TimeZoneKeyName" is invalid, "TimeZoneNotFoundException" exceptions are thrown
- [2018.4] UnityWebRequest.java has a sHostnameVerifier which doesn't have server identity check implemented
- Secondary hidden Hierarchy windows pop up when a new gameObject is created in another Hierarchy window
Add comment