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

Deployment Management

-

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

trunk PR: https://ono.unity3d.com/unity/unity/pull-request/51270/_/platform/windows/default-screen-resolution-bug

Comments (21)

  1. Weightless

    Aug 31, 2020 20:07

    Present in 2019.3.13f1. Come on guys I can't be asking my users all the time to delete registry entries.

  2. jnantes

    Jun 19, 2020 22:04

    Present in 2019.2.4.f1

  3. DomeCreator

    May 25, 2020 08:44

    Not fixed in 2019.3f2

    On windows resolution is stored in the registry under keys such as "Software/<Company Name>/<Project Name>/Screenmanager Resolution Width"

    To resolve the issue I had to delete my project registery keys, re-build and launch project.

  4. vsertich

    Mar 18, 2020 16:51

    This is happening to me in Unity 2018.2.4f1.

  5. chadfranklin47

    Feb 14, 2020 08:40

    Hi, for anyone still getting a similar problem, I just wanted to post here that I recently filed a new bug report and they said it has been fixed from "Unity 2020.1.0a24 and above". I asked if it would be fixed for 2019LTS and they said that cannot be guaranteed, but hopefully so. Here is the link to the new issue tracker: https://issuetracker.unity3d.com/product/unity/issues/guid/1216508

  6. chadfranklin47

    Feb 03, 2020 03:17

    The problem is still in 2019.3.0f6. Come on Unity, can't be a hard fix. All these shiny features and this can't be fixed?

  7. Talasas

    Dec 13, 2019 05:41

    I am actually seeing the opposite of this, the game keeps switching BACK to native resolution. If I make a build with Native resolution ticked, and then change the resolution in game, after a while it will switch back to the native res.

    You can actually see the Windows task bar pop up for 1 frame when it happens.

  8. Discipol

    Sep 23, 2019 15:36

    Problem is still in 2019.3.0b3

  9. Bajana

    Jan 08, 2019 15:51

    The problem persists for with all versions from 2018.2.4f1 to 2018.2.20.
    Here is my ticket:
    https://forum.unity.com/threads/unity-app-has-wrong-initial-resolution-after-upgrade-to-2018-2-4f1-and-newer.600193/

  10. Drabantor

    May 23, 2018 10:34

    Problem still persist for me in 2018.1.0f2

    Anyone tried deleting the registry keys at: "Software/<Company Name>/<Project Name>/Screenmanager Resolution Width and Resolution Height" and then setting the resolution to 9999 x 9999 in Player Settings?

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.