Unity Issue Tracker - Second display inherits first display's resolution when loading second display on a smaller resolution monitor

Fixed in 2019.3.X

Fixed in 2019.2.X

Votes

3

Found in

2019.1.0a12

2019.1.4f1

2019.2.0a1

2019.3.0a1

Issue ID

1159209

Regression

Yes

Second display inherits first display's resolution when loading second display on a smaller resolution monitor

Window management

May 31, 2019

How to reproduce:
1. Open the attached "case_1159209.zip" Unity project
2. Set the second monitor display to a smaller resolution (such as 1280 by 800)
3. Build and Play the scene
4. Observe the effect on both displays

Expected result: the view on the second monitor is scaled to fit its resolution (picture 1)
Actual result: the view on the second monitor is in the same resolution as the view on the first monitor (picture 2)

Reproducible with: 2019.1.0a12, 2019.1.5f1, 2019.2.0b5, 2019.3.0a5
Not reproducible with: 2017.4.28f1, 2018.4.2f1, 2019.1.0a8

Note: Unity versions 2019.1.0a9 through 2019.1.0a11 do not render the second view.

Resolution Note (fix version 2019.3):

Fixed in 2020.1.0a2

Comments (13)

while-loops

Aug 17, 2021 18:08

This issue is not fixed. Having this problem in 2020.2.4f1.
Please look into this issue again.
kundankmr

Dec 07, 2020 10:16

I have checked in 2020.1.6f1, 2019.4.8f1, 2018.3.12f1, and 2019.2.1f1. so this does not appear to be fixed in any mentioned versions. Can you please look into this problem again?
LaurynasLubys

Nov 24, 2020 08:39

It is not fixed in any version that I try, even the latest official 2020.2.0 Simple replication is to create two cameras for each display, then show some UI with canvas scalar on each screen. When focused on each screen, the other screen will react to resolution scaling of the first screen.
tobii_jspg

Apr 28, 2020 08:33

This is not fixed on Linux (Ubuntu, i3wm) 2019.3.5, 11 or 2020.1.0b
DG-ABQ

Oct 03, 2019 15:34

We too are anxiously waiting for the changes to be incorporated into 2019.2. As of 2019.2.7f2 the change has not been incorporated.
IJsfontein-B-V

Oct 02, 2019 16:04

For when is this fix planned in 2019.2?
DG-ABQ

Sep 09, 2019 15:39

Presently this does not appear to be fixed in 2019.3.0b2. Should this fix be visible in the beta?

Search Issue Tracker

3