Search Issue Tracker
Fixed
Fixed in 2022.3.55f1
Votes
0
Found in
2021.3.43f1
2022.3.44f1
Issue ID
UUM-78726
Regression
No
PhysicsRaycaster.ComputeRayAndDistance() does not detect mouse input on colliders when multi-display setup is used
Reproduction steps:
1. Open the attached “PointerInputTest.zip” project
2. Have a setup of at least two displays
3. Build and Run the project (File > Build and Run)
4. In the Player on a secondary display, click on colliders
Expected result: The colliders get clicked on and the clicks are logged in the Player
Actual result: The colliders do not get clicked on or incorrect colliders get clicked on
Reproducible with: 2021.3.43f1, 2022.3.44f1, 6000.0.1f1
Fixed in: 6000.0.2f1
Not reproducible with: 6000.0.17f1
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes:
- The mouse input detection on the primary display works correctly
- Modifying PhysicsRaycaster.ComputeRayAndDistance() to use GetRelativeMousePositionForRaycast() instead of RelativeMouseAtScaled() fixes the issue and enables correct input detection across multiple displays
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android][IL2CPP][ARMv7] Struct field value corrupts when invoking a generic delegate with a large struct by value
- Highlights persist throughout Options Panels in the Rendering Debugger Window
- Typing numbers in Matrix node’s numeric fields stretches Node
- Streaming is misspelled as "Steaming" in "Enable GPU Streaming" and "Enable Disk Streaming" tooltpis
- "IndexOutOfRangeException" thrown when moving caret left at start of TMP Input Field with rich text
Add comment