Search Issue Tracker

Fixed in 2018.4.0f1

Fixed in 2018.4, 2019.1, 2019.2

Votes

64

Found in

2018.3.8f1

2019.1.0b5

2019.2.0a6

Issue ID

1137204

Regression

Yes

Fullscreen mode: Maximized Window functionality is broken and any built Player changes to Non-Window mode when Maximizing

Windows

-

How to reproduce:
1. Create a new project and open its Player settings
2. Under the "Resolution" settings change the "Fullscreen Mode" to "Maximized Window" and checkmark the "Resizable Window" option
3. Build the project
4. Run it in fullscreen mode (The Player will be fullscreen in non-window form)
5. Run it again in windowed mode and maximize the window (The Player will still be in fullscreen non-window form)

Expected result: when maximizing the player is still in window mode
Actual result: maximizing the player results in it changing modes to regular fullscreen, making the title bar disappear

Reproduced in: 2019.2.0a8, 2019.2.0a6, 2019.1.0b7, 2019.1.0b5, 2018.3.9f1, 2018.3.8f1
Not reproducible with: 2019.2.0a5, 2019.1.0b4, 2018.3.7f1, 2017.4.23f1 (The 2017.4 versions had a separate D3D11 Fullscreen Mode setting which works as expected when setting it to Exclusive Mode)

Fixed in: 2019.2.0a15, 2019.1.2f1, 2018.4.0f1

  1. Response avatar

    Resolution Note (fix version 2018.4.0f1):

    The behavior of the Maximize button was changed in order to fix another (more serious) issue: https://issuetracker.unity3d.com/issues/buttons-dont-record-input-when-the-window-is-maximized-and-then-set-to-2560x1080-resolution

    Clearly we made a bad call. So, we've implemented a different fix to the aforementioned bug which also maintains the correct maximize window behavior.

    A workaround to automatically revert the app out of fullscreen mode can be found here: https://forum.unity.com/threads/unity-2019-1-is-now-available.661885/page-3#post-4491478

    Verified fixed in: 2019.2.0a15, 2019.1.2f1, 2018.4.0f1

Comments (31)

  1. C8b61eb15d766d89ce02c5593e57cd2b?d=mm

    Trunex

    Dec 06, 2019 00:36

    I have same issue in Unity 2019.2.7f2

  2. 8acde85398292b1a42a3833a089d5cea?d=mm

    ttmmiizz100

    Dec 03, 2019 23:20

    Nevermind, a fixed this by setting fullscreen mode to windowed and setting "allow fullscreen" to false. Now, it maximizes normally when maximizing.

  3. 8acde85398292b1a42a3833a089d5cea?d=mm

    ttmmiizz100

    Dec 03, 2019 23:12

    Reproducible in 2019.3

  4. 0405f320acf913f5ef8a78ffdb3c11df?d=mm

    djDavidj

    Jun 28, 2019 20:58

    I also have same issue in 2019.1. After I build and run the app on a Mac my game is stuck in 4:3 aspect ratio. With no choice to pick another one. My game is in 16:9 and I keep running into this issue with other projects. I have the correct settings in player settings. It just wants to only build in 4:3. I tried to fix it in code and we’ll it kinda worked. But had a backdrop of my background colour. Oh well. I’ll keep searching before I down grade. Frustrating.

  5. Aae99a07af40cf0b9144c7693ff44888?d=mm

    Danielfc

    May 13, 2019 11:56

    This is very strange, let me get this straight.

    if i am building with "Maximized Window" it should open the application in Maximized Window.
    i tried both version 2019.1.2f1 and 2018.4.0f1 and its opening the app on FullScreenWindow.

    am i missing something?

  6. 0fd3707fd87030cbe8e9ded4febf6d13?d=mm

    Huacanacha

    May 01, 2019 15:09

    The fix is scheduled for 2019.1.2 which is due in approximately 2 weeks. See:
    https://forum.unity.com/threads/unity-2019-1-is-now-available.661885/page-3#post-4484548

  7. 08a38a886d9b56b85b4e547fb43f43bb?d=mm

    EthanFischerICS

    Apr 29, 2019 14:58

    This was not fixed in 2019.1.0f2

  8. Eee02e3bbfc9dea09ccf9fc5a96465af?d=mm

    digipaul

    Apr 27, 2019 21:03

    This is marked as resolved in 2019.1, yet it is still happening for me with 2019.1.0f2.

  9. C311929d21e6a56dafb09b8e6a7a589a?d=mm

    WrexialMT

    Apr 26, 2019 21:07

    "Fixed in Unity 2019.1" will this be applicable to 2018.3 LTS? It'd be a shame we'll have to stay stuck on 2018.3.7 without this fix.

  10. 0fd3707fd87030cbe8e9ded4febf6d13?d=mm

    Huacanacha

    Apr 24, 2019 21:06

    This may block our releases. It's very poor form to introduce known core UX regressions between major engine versions (seems like it was introduced in a 2018.3 patch but is a regression between 2018.3.0 and 2019.1.0). Also... this issue is NOT MENTIONED in the 2019.1 release notes. Why not? If I had seen this issue we would have delayed upgrading to 2019.1 until it was fixed. As it stands we now have a choice between introducing a UX regression in our application or delaying feature releases.

    In my opinion, if Unity wishes to be taken seriously for non-gaming applications 2019.1 should not have been released with this regression. And it definitely should not have been released without disclosing this as a known issue.

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.