Search Issue Tracker
By Design
Votes
0
Found in
2018.3.0b6
2018.3.12f1
2018.4.0f1
2019.1.0a3
2019.2.0a1
2019.3.0a1
Issue ID
1174378
Regression
Yes
Using Exclusive FullScreenMode on second monitor, non-native resolution is stuck when trying to change it to native resolution
Repro steps:
1. Open attached project
2. In the Player settings, in the Resolution and Presentation section, enable the Display Resolution Dialog option
3. In the Build settings press "Build And Run"
4. In the Configuration window, select "Display 2" for the "Select monitor" option and press "Play!"
5. Change to native resolution and "Exclusive Fullscreen" mode if build opens with different settings
6. Change native resolution to 720x480 (59 Hz)
7. Select "Fullscreen Window" and then "Exclusive Fullscreen"
8. Change the resolution back to native resolution
Expected result: Resolution changes to selected native resolution
Actual result: Resolution does not change from 720x480 (59 Hz)
Reproducible with: 2018.3.0b6, 2018.4.6f1, 2019.1.0a3, 2019.1.14f1, 2019.2.1f1, 2019.3.0a11
Not reproducible with: 2018.3.0b5, 2019.1.0a1, 2019.1.0a2
Could not test with: 2017.4.31f1 (Doesn't have FullScreenMode in the API)
Note: Reproducible only on the second monitor
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
- Unable to undo or redo color swatch changes when creating or deleting color swatches
- [Linux][Vulkan] Silent crash when tooltip appears while hovering over a label
- Material Properties are not preserved when overriding Shader using Render Objects
- Scene view flickers when both Scene and Game view are active and DX11 API is used with Gamma Color Space
- ZivaRT Player and ML Agents packages Deprecated label color differs from other Deprecated packages
Resolution Note (2019.3.X):
There is a flaw in the user provided script. Modified the script to make use of correct overloaded version of Screen.SetResolution().