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
Comments (21)
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
- Camera Preview does not detect multiple cameras with same GameObject name
- Crash on TypeTreeIterator::Children() when renaming a corrupted asset while Asset Serialization is set to Mixed
- Cameras (Camera.targetDisplay) render only to Display 0 in the Player when Multi-Display setup is used and DX12 API is set
- [Vulkan] _CameraOpaqueTexture produces a feedback effect on Android Adreno devices when using Vulkan
- Loading animations are hitching or stopping when using "SceneManager.LoadSceneAsync" to load new scenes
Gua
Apr 27, 2018 21:05
*5.6.5f1
Gua
Apr 27, 2018 21:04
2 TECHCOR, Thanks for the workaround. It works in 5.6.1f1.
rad1c
Mar 26, 2018 10:48
Feels like I'm posting into a time capsule. Amazing.
Win7 x64, 2017.3.1p1, same issue except it goes for 1920x1200 for me (instead of 2K)
EvilScienctist451
Mar 16, 2018 15:23
Yeah, this one's pretty frustrating. Fix it soon please!
AlanMattano
Feb 08, 2018 00:01
WHERE IS THE WORK ARROUND?
AlanMattano
Feb 07, 2018 23:26
This problem is old and still there. Forum example since 2008 up to 2017
More info:
https://forum.unity.com/threads/playerprefs-for-screen-resolution-ignored-in-windows-builds.11749/
AlanMattano
Feb 07, 2018 19:01
Having this issue on 5.6.3p2 Windows10
Is bad because when the game resolution is fixed, as for example a launcher, it renders with distorted proportions.
WHY IS NOT FIX? or a solution.
teknic
Sep 25, 2017 16:02
This remains a problem in 5.6.3f1. 9999x9999 trick works.
martinamenegon
Aug 04, 2017 18:03
same issue here.. getting a bit stressed by this as i have an exhibition in 2 weeks!
running on windows 7, unity version 5.6.2.
I'm going to try the trick techcor suggested but tbh would love to see this bug fixed asap!
duplexius
Jul 17, 2017 20:51
How can such a bug remain for so long? I still have this in 5.6.2p2, which is the latest in the 5.6 branch as of today. *shakehead*