Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
5.4.0f1
Issue ID
814366
Regression
No
[Multidisplay UI] "Display.RelativeMouseAt" z axis only shows value of 0.
Steps to reproduce:
1. Open my attached project.
2. Open "test" scene.
3. Build project in windows platform.
4. Move your cursor between two screens.
--- Note that "current display" text field shows " Display.RelativeMouseAt" z axis.
Expected results: " Display.RelativeMouseAt" z axis should change when cursor moves between displays.
Actual results: It stays 0.
Reproduced with: 5.4.0f1, 5.4.0b25, 5.3.5p8, 5.3.5f1, 5.2.0f3
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
- NullReferenceException when setting 'isTextObjectScaleStatic' to false on a disabled TextMeshPro GameObject
- Shader Stripping Custom Options disappear when exiting Play mode without reloading Domain
- Decals do not get projected when 'Rendering Layer Mask' on a GameObject is 23rd Layer or above due to encoding/decoding issues
- Deriving from SearchContextAttribute doesn't always work
- Scripting API documentation is missing for macOS editor extensions
ytrew
Jul 12, 2017 21:12
Issue still prevalent in 5.6.1f1! RelativeMouseAt returns zero for each axis, so mouse input for screen space conversion to interact with UI on multi displays does not work.