Search Issue Tracker
Fixed in 2018.1.X
Fixed in 5.6.X, 2017.1.X, 2017.2.X
Votes
10
Found in
5.6.0p4
Issue ID
908932
Regression
Yes
Default resolution for standalone build is not correct when "Default is Native resolution" is selected
By Design:
On windows resolution is stored in the registry under keys such as "Software/<Company Name>/<Project Name>/Screenmanager Resolution Width"
If the resolution is specified in the registry, the "Default is Native Resolution" option will be ignored.
The registry key was probably set from a previous run of the game using the resolution dialog before the "Default is Native Resolution" was set.
This is expected behavior
Steps to reproduce:
1. Create a new project
2. Make sure that "Default is Native resolution" is checked
3. Make sure that "Default is Fullscreen" is checked
4. Disable the Resolution dialog
5. Build for standalone
6. Run the build
Expected result: build resolution is whatever the native resolution is
Actual result: build resolution is 1024x768
Reproduced on 5.6.0p1, 5.6.0p3, 5.6.1p1, 2017.1.0b6*
Not reproduced on 5.6.0f3
Regression introduced in 5.6.0p1
VERIFIED FIXED 2017.1.3p4, 2017.2.3f1, 2017.4.3f1, 2018.1.2f1
Notes:
-Even after disabling "Default is Native resolution", changing values and then enabling again, the bug stays.
*-2017.1.0b6 "Default is fullscreen" also does not become fullscreen by default
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
- [Android] Error "Blitter is already initialized" is present when Adaptive Probe Volumes are used with OpenGLES3
- VFX Graph effect instance stops rendering when a second instance of the same effect starts 2 frames later
- Operations on the Color32 array are not reflected in WebGL Player when HDR is off
- Rigidbody moves away from the original GameObject when Center of Mass is set in every frame
- WebGL Player does not proceed beyond logo screen when "Target WebAssembly 2023" is enabled
TechCor
Jun 27, 2017 03:19
Having this issue on 5.6.1. Deleting registry keys makes it open at 1024x768 full screen despite marking Default is Native Resolution.
For those stumbling upon this bug, The workaround is to set default resolution to 9999x9999.