Search Issue Tracker
Fixed in 2018.4.X
Fixed in 2019.2.X, 2019.3.X
Votes
1
Found in
2017.4.0f1
2018.4.0f1
2019.2.0a1
2019.2.0f1
2019.3.0a1
2020.1.0a1
Issue ID
1183011
Regression
No
[MacOS] "Default is Native Resolution" checkbox is ignored if custom resolution was set before
How to reproduce:
1. Create a new project
2. Open Player Settings
3. Open "Resolution and Presentation" tab
4. Uncheck "Default is Native Resolution" checkbox
5. Set any resolution (800x600 for example)
6. Build & Run the project
7. Close the player
8. Check the "Default is Native Resolution" checkbox
9. Build & Run the project
Actual result: "Default is Native Resolution" is ignored and the player is launched at 800x600 resolution.
Expected result: The player is launched in native resolution.
Reproducible with: 2020.1.0a4, 2019.3.0b3, 2019.2.4f1, 2018.4.8f1, 2017.4.32f1.
Notes:
- This issue on Windows got fixed by case 908932
--------------------
Fixed in 2020.1.0a9, 2019.3.0b11, 2019.2.14f1, 2018.4.13f1.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2018.4):
Fixed in 2020.1.0a9 - the player will pickup new display settings when they are changed in the editor