Search Issue Tracker
Fixed in 5.3.0
Votes
0
Found in
5.3.0b5
Issue ID
741751
Regression
Yes
Canvas elements are placed incorrectly when setting non-native resolution in standalone build
To reproduce the issue follow the steps:
1. Open "case_741751-New_Unity_Project"
2. Open "test" scene
3. Build the scene
4. Play the scene at native resolution and observe the button turning red when hovered over
5. Play the scene at a lower resolution and observe how the button is moved to the right of the center
You have to hover somewhere above of the button for it to turn red.
Regression:
This appears only in Unity 5.3.0b5 (70818a4976ce)
Screenshot:
http://bugs04.unity3d.com/fogfiles/741751_lrhf54e589iu9l4q/case_741751-1024x768.png
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
karl_jones
Dec 31, 2015 17:17
Some of the multiple display system was missed on the cs side. A temporary fix is available in the UI source code here https://bitbucket.org/karljj1/ui-md-fix or alternatively a fix will be available in a future patch.
poliman
Dec 31, 2015 16:50
with 5.3.1 the hover click position is patched but still if you use canvas scale with screen size - shrink, it doesnt scale in full screen standaleone with not native screen size, but it works perfectly in 5.2.4
poliman
Dec 31, 2015 16:50
with 5.3.1 the hover click position is patched but still if you use canvas scale with screen size - shrink, it doesnt scale in full screen standaleone with not native screen size, but it works perfectly in 5.2.4
vchamyp
Dec 23, 2015 07:20
Unity 5.3 Google play service and AdMob When i apply folder google-play-services_lib from Android SDK, Unity automatically delete it. If someone have same problem share..
karl_jones
Dec 14, 2015 00:24
The fix will be in 5.3.0p1. The issue is a bug in the multiple display system. The multiple display system will be disabled for the UI whilst we wait for a fix(ETA 5.4)
Zuntatos
Dec 09, 2015 13:33
They're claiming a fix is incoming in 5.3.0p1 (or whatever it'll be called, the first patch).
AndrewShouldice
Dec 08, 2015 16:15
Case 750716 was closed as a duplicate of this issue, but that case still occurs in 5.3.0f4.