Search Issue Tracker
By Design
Votes
18
Found in
5.3.4f1
Issue ID
789384
Regression
No
It's not possible to change resolution beyond 16320x768
How to reproduce:
1. Open attached project
2. Build to Standalone and run
3. Use the key commands to change resolution
- a,s,d,f,g,h,j,k,l,q,w,e,r,t,y,u,i,o,p; each letter represents a different horizontal resolution
- the R key switches to 16320x768, the T key switches to 17680x768, the rest switch to larger resolutions
4. Press the T key (or any of the following ones)
- Note that the resolution is set, but results in a completely black screen
- Reproduced in Version 5.4.0b15 (2e995a1aa11c), Version 5.3.4f1 (fdbb5133b820)
- Blocked from testing 5.2 due to script errors
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