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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment