Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
1
Found in
4.0.0b5
Issue ID
483300
Regression
No
Default screen resolution is ignored if no supported aspect are selected
- Go to Player Settings for Windows Standalone
- In Resolution and Presentation set the resolution to 600 by 350
- Deselect all supported aspect ratios
- Build and Run
Result: the only available resolution is 1920 by 1200
- Go to player setting and check the Others option in the supported aspect ratios
- Build and Run
Result: Available resolutions are 720 by 480 and 1280 by 768
Expected: in both cases I would expect my custom resolution of 600 by 350 to be in the available screen resolution dropdown when I run the build
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment