Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2019.1.X
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
- Size of ShadowCaster2D with Casting Source set to a Collider increases when RigidBody2D is attached to the GameObject
- GameObjects with a material derived from a Custom Lighting Surface Shader are displayed as skewed on quads when the Camera's Width and Height properties of the Viewport Rect are lower than 1
- Warning 'Unable to find player assmebly' is thrown when building some Project Templates
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
Add comment