Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.1.X, 2020.2.X
Votes
0
Found in
2018.4
2019.4
2019.4.4f1
2020.1
2020.2
2021.1
Issue ID
1277983
Regression
No
Resolution isn't saved and changes to monitor resolution when opening player with ExclusiveFullScreen
How to reproduce:
1. Open the attached "1277983 repro" project
2. Build and Run the project
3. Press the "E" key on the keyboard
4. Press the "1" key on the keyboard
5. Close the built project
6. Launch the same project build again
Expected results: the resolution is set to 1280x720
Actual results: the resolution is set to the native resolution of the monitor
Reproducible with: 2018.4.27f1, 2019.4.11f1, 2020.1.6f1, 2020.2.0b3, 2021.1.0a1
Notes:
-This doesn't reproduce when using FullScreenWindow, MaximizedWindow, or Windowed modes
-This does reproduce with Direct3D11 and Direct3D12
-ExclusiveFullScreen isn't supported by OpenGL and Vulkan
-This doesn't reproduce with Metal
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
- Crash on "The GUID inside 'Assets/asset.png.meta' cannot be extracted by the YAML Parser." when opening the project
- Shadows disappear when looking at a certain angle in Scene view and using Cloud Shadows with Volumetric Clouds
- StackOverflowException freezes or silently crashes the Editor
- Microsoft Surface Device freezes when detaching and reattaching physical keyboard attachment to a Microsoft Surface device in Standalone Player for Windows
- Shadows are cast with artifacts on GameObjects when the light type is set to Point
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a1
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0b7
Resolution Note (fix version 2020.1):
Fixed in 2020.1.10f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.13f1