Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.3.X, 2022.1.X
Votes
19
Found in
2018.3.10f1
Issue ID
1141732
Regression
No
Button's hitbox is offset when building standalone project for two screens
Reproduction steps:
1. Open the attached build of the project named "Build_1141732_New"
2. Select a non-native screen resolution
3. Start the game
4. Move the mouse over one of the buttons on the second screen
Expected result: Button's hitbox is inside the button
Actual result: Button's hitbox is offset
Reproducible with: 2018.3.8f1, 2018.3.12f1, 2019.1.0f1, 2019.2.0a11
Not reproducible with: 2017.4.25f1, 2018.3.7f1
Notes:
1. The bug only happens when the build is running with a non-native screen resolution
2. This is an existing issue (not a regression) which was masked by another bug:
https://issuetracker.unity3d.com/issues/primary-screen-window-size-turns-to-native-when-using-more-than-one-display
it preventing setting a non-native resolution and thereby kept this issue from manifesting
-
mayasarii876
Mar 09, 2022 05:03
http://103.56.148.201/
http://103.56.148.201/newmpo
http://103.56.148.201/mpo17
http://103.56.148.201/mpomm
http://103.56.148.201/mpotower
http://103.56.148.201/parisklub
http://103.56.148.201/juraganslot
http://103.56.148.201/mpo500
http://103.56.148.201/mpokick
http://103.56.148.201/mpoyes
http://103.56.148.201/xyzklub
http://103.56.148.201/betmpo
http://103.56.148.201/ogslot88
http://103.56.148.201/hoki777
http://103.56.148.201/mpojuta
http://103.56.148.201/299slot
http://103.56.148.201/mpo188
http://103.56.148.201/mpogacor
http://103.56.148.201/mpo300
http://103.56.148.201/rgo365
http://103.56.148.201/kingdom288
http://103.56.148.201/wigompo
http://103.56.148.201/mpo8899
http://103.56.148.201/mpopelangi
http://103.56.148.201/mpo555
http://103.56.148.201/dutampo
http://103.56.148.201/klik368
http://103.56.148.201/388hero
http://103.56.148.201/19dewa
http://103.56.148.201/mpoxl
http://103.56.148.201/mpoas
http://103.56.148.201/mposun
http://103.56.148.201/qqslot
http://103.56.148.201/mposport
http://103.56.148.201/dewa234
http://103.56.148.201/mesinmpo -
FSpark
Sep 08, 2020 10:58
The Unity Editor (2019.4.9f1) works with a second screen (4K) which is of a higher resolution to the primary screen of a MacBook Pro Retina 15", but the game executables do not?
Surely if Unity has already solved the issue, why can't the solution be applied to the game builds?
Come on Unity! The workaround suggested by the resolution is NOT USER FRIENDLY!!! It's a really poor and unacceptable workaround!
Unity is used for not just games but also visualisations, medical and industrial applications! Think about your end-user base please!
-
Weightless
May 23, 2020 08:18
What kind of workaround is this? "To work around this problem with Multi-Display, ensure all display have the same Resolution or screen size." Let me just ask all users to buy new monitors.
-
Pitou22
Jul 18, 2019 16:42
I confirm this problem, still present on 2019.1.10f1 ...
-
unity_92f75KLGQnUMfA
Jun 19, 2019 09:08
Same problem here. Using ScreenSpace - Camera does not help either.
-
JG-Denver
Jun 19, 2019 03:01
I believe this issue may be directly related to another issue already in Issue Tracker as well:
https://issuetracker.unity3d.com/issues/loading-second-display-on-2-different-monitor-setups-shrinks-the-higher-resolution-display-to-lower-resolution-displays-size -
m4d
Jun 18, 2019 23:02
We're having the same problem right now with ui controls (buttons, sliders, dropdowns) not receiving their raycasts when on a secondary display which has a different resolution than the first one.
-
yezzer
Apr 11, 2019 10:27
We are also experiencing this issue, it's making multi-monitor projects difficult to work on.
-
tabulatouch
Apr 10, 2019 18:50
I confirm this nasty problem, it is highly problematic on multi-display Windows system with different resolutions.
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
- [Linux] Android build fails with “CommandInvokationFailure: Gradle build failed.” error
- [iOS] Touch.rawPosition changes position when touch is dragged
- Loading a scene with a large amount of light probes causes a performance spike
- The player does not refresh window display properties when opening the Player on another display
- Spot Light flickers when when it's far from the origin point
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a4
Resolution Note (fix version 2022.1):
Fixed in Unity 2022.1.1f1
Resolution Note (fix version 2021.3):
Fixed in Unity 2021.3.3f1
Resolution Note (fix version 2020.3):
Fixed in Unity 2020.3.35f1
Resolution Note (fix version 2019.4):
Fixed in Unity 2019.4.40f1