Search Issue Tracker
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
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.
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note (fix version 2019.3):
Fixed in 2020.1.0a2