Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2017.4.X, 2018.4.X
Votes
1
Found in
2017.4.0f1
2018.3.0a1
2018.3.8f1
2019.1.0a1
Issue ID
1134231
Regression
No
View on second display appears squashed when build is launched in windowed mode
How to reproduce:
1. Open the attached "1134231.zip" project
2. Build project
3. Launch the build in an Exclusive Full-screen mode
4. Observe that in the second display, the ball is round
5. Re-launch the build in the Windowed mode
6. Observe that in the second display, the ball is squashed
Expected result: The ball in the second display is round in both cases, regardless of the windowed mode being checked or not.
Actual result: The ball appears squashed, when build is launched in windowed mode.
Reproducible with - 2017.4.0f1, 2017.4.24f1, 2018.3.0a1, 2018.3.10f1, 2019.1.0a1, 2019.1.0a8
Could not test on the latest 2019.1 and 2019.2 versions due to another issue (case 1140275; view the notes).
Notes:
- On 2017.4 and 2018.3.0a1 the issue was also present when launching build in full screen mode (not reproducible on 2018.3.0a2 and later).
-
ippei
Oct 25, 2019 10:32
I received the following email from Unity Tech.
And
I have confirmed that this issue has been fixed in my differnt resolution multi display project.
-------------------------------------------------------------------
Thanks again for reporting the issue. After further investigation, we found out that issue you reported is fixed in 2019.2.9f1, 2019.3.0b1, 2020.1.0a2 and later versions. -
ippei
Oct 16, 2019 09:53
I think the following fixes are affecting this new issue.
https://issuetracker.unity3d.com/issues/primary-screen-window-size-turns-to-native-when-using-more-than-one-displayI hope this issue will be fixed as soon as possible for multi display contents.
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Resolution Note (fix version 2019.3):
Fixed in 2020.1.0a15
Backported to 2017.4.36f1, 2018.4.14f1, 2019.3.0f3