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.
-
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?
-
isoconsultation
Dec 02, 2020 07:13
Thank you for your writing! It is easy to understand and detailed. I feel it is interesting, I hope you continue to have such good posts
Certivatic is one of the best iso certification providers in major cities of Malaysia like Kuala Lumpur, Ipoh, Johor Bahru, Malacca. Certivatic helps companies to get certified by iso no matter what type of business you have. -
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
-
factocert2
Apr 04, 2020 07:02
This is one of the finest post i have ever seen. The information is genuine and relatable . We are really grateful for your blog post.
http://factocert.com/iso-9001-certification-in-saudi-arabia
http://factocert.com/iso-14001-certification-in-saudi-arabia
http://factocert.com/iso-27001-certification-in-saudi-arabia
http://factocert.com/iso-22000-certification-in-saudi-arabia
http://factocert.com/iso-45001-certification-in-saudi-arabia -
unity_5BjKXJmJC0_ouA
Mar 31, 2020 07:01
I simply cherished your method for introduction. I appreciated perusing this. Thanks for sharing and continue composing. As always, we welcome yourself confirmation and acknowledge as valid inside us.
<a href="http://factocert.com/iso-certification-in-saudi-arabia"> iso certification in saudi arabia </a>
http://factocert.com/iso-certification-in-saudi-arabia -
deamjones5247
Dec 19, 2019 13:09
These viruses directly attack your computer systems, resulting in corrupting your important data and stealing your confidential information.
http://ask-norton.com
http://assistnorton.com
https://ca-norton.com/setup
http://norton-us.com
http://stnorton.com -
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?
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
- Inspector's custom tooltip is displayed incorrectly when the name is truncated in UI toolkit
- Crash on ScriptableRenderLoopDraw when rendering a specific VFX in Play Mode
- The script is not renamed in the Project window when renaming and a compilation Error is present
- Average FPS in Play Mode degradation on a newly created BiRP project when it's upgraded from 2020.3.48f1 to a newer Editor version
- DecoratorDrawer indentation is incorrect when it is called with EditorGUI
Resolution Note (fix version 2019.3):
Fixed in 2020.1.0a2