Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2017.4.X, 2018.4.X, 2019.2.X, 2019.3.X
Votes
11
Found in
2017.4.0f1
2018.2.5f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
Issue ID
1146233
Regression
No
UI Sliders on secondary screens do not respond correctly when using Multiple Displays
Reproduction steps:
1. Open the attached build of the project named "Build_1146233"
2. Move the slider on the first screen. Slider functions properly
3. Try to move the slider on the second screen
Expected result: Slider behaves the same way as in the first screen
Actual result: Slider is broken and instantly turns into max value
Reproducible with: 2017.4.26f1, 2018.3.13f1, 2019.1.0f2, 2019.2.0a12
Notes:
1. The behavior of the slider depends on Windows positioning of the monitor. When setup is like in Snapshot_1146233_V1 behavior is as shown in Track_1146233_V1. When setup is like in Snapshot_1146233_V2 behavior is as shown in Track_1146233_V2.
2. Testing is hampered in 2018.3.8f1 and above due to another issue ( case 1141732 ).
3. The issue also happens when Scrollbar or Scroll View UI components are used.
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
- Value on Slider (Int) control in UI Builder displays as default when saving UI Document
- Color mismatch in UI Builders Library panel when the Editors theme is set to Light Mode
- [Android ] "AndroidJNI.ToBooleanArray" returns a random non-zero value instead of "IntPtr.Zero" when the method argument is null
- Non-HDR color picker opens when selecting material color with HDR enabled
- Crash on EditorApplication:Internal_CallUpdateFunctions when pushing property block by index to SpriteShapeRenderer
ebadier22
Nov 22, 2019 11:27
The issue is still not fixed in Unity 2017 (tested version : 2017.4.34f1) !
Please fix it or remove wrong information on this page.
m4d
Jun 18, 2019 23:05
We're also having this issue and it's hindering us from delivering an app to a client. Plz fix this! :)
pfSRT
May 21, 2019 08:28
Hi, we are having this issue in 2019.1.3f1. Do we have any estimate on a fix?