Search Issue Tracker
By Design
Votes
2
Found in
5.6.1f1
Issue ID
919399
Regression
No
Windows Standalone doesn't change Resolution if Display Resolution Dialog is disabled
Reproduction Steps:
1. Import attached project.
2. Open "Main" scene.
3. In Player Settings, set the values accordingly:
-Default is Full Screen: Enabled
-Default Screen Width: 1920
-Default Screen Height: 1080
-Display Resolution Dialog: Enabled
-Supported Aspect Ratios: 16:9
4. Build and Run Standalone Windows Build.
5. In Windows, change screen Orientation to Portrait.
6. Back in Unity, again change the values in Player Settings:
-Default Screen Width: 1080
-Default Screen Height: 1920
-Display Resolution Dialog: Disabled
-Supported Aspect Ratios: Others
4. Build and Run Standalone Windows Build.
Expected results: Resolution is changed automatically. Resolution is 1080x1920.
Actual results: Resolution remains the same as in the previous build. Build remains Landscape, but in a Portrait orientation. Resolution is 1920x1080 (Image attached)
Note: This happens in reverse as well. If the previous build was 1080x1920 and a new 1920x1080 build is created with Dialog disabled, the build will remain 1080x1920. (Image attached).
Workaround: Using Screen.SetResolution to set the resolution manually.
Reproducible with: 5.5.3p4, 5.6.1p2, 2017.1.0b9, 2017.2.0a3
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
CaseyHofland
May 31, 2019 11:03
I AM using resolution dialog, but the right resolutions are just not turning up! I have an aspect ratio of 2 : 1, my default screen width and height is 1280x640 and I even made one myself with a fixed resolution, all not caring to show!
Perhaps because I was fiddling around with resizable window earlier (and unchecked afterwards), now I can only select 1280x600, but there is still absolutely no clear reason why it shouldn't just reset. It leaves my game with blue colors from the camera on both sides of the screen and it's really frustrating that after 1 hour of fiddling with settings and deleting registry keys and setting, still nothing is changing!
It is really discouraging me from trying to build correctly and when I present this to my team tomorrow I guess I'll just have to explain the issue with them and we will have to deal with blue borders and sprites coming up from the sides while playtesting. But first I'll try exporting the entire project to another computer (which is more time than this is worth), set everything there, and PRAY that it builds correctly the first time.
It might be by design, but that doesn't mean it doesn't have problems.
MegaPixel04
Mar 18, 2018 14:54
I"M experiencing this issue on Unity 5.6.2f1 as well. Took ages to figure it out. Isn't there a way to solve this without using a resolution dialog?
iflo
Jun 12, 2017 08:33
Unity will hold on to previously set game resolutions as it stores them within the registry, but unfortunately the resolution does not correctly set to native even if you delete the PlayerPrefs registry keys which contain previously run screen resolutions.
My native resolution is 2560 x 1440 and Unity Standalone is always opening for me at 1024x768, unless I enable the resolution dialog (where it defaults correctly to the native resolution). I have experienced this on 5.6, but seems to be working for me on 2017.1.0b9