Search Issue Tracker
In Progress
In Progress in 2022.3.X
Under Consideration for 2021.3.X
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
- Spot Light with 'Box' Shape stops working when it collides with Mesh
- Accepting Asset Store EULA endless loop in Package Manager window
- “InvalidOperationException: Sequence contains no matching element“ error when reenabling a custom Debug Draw Mode
- Prefab that contains a layout group is marked as changed by the Editor when opened
- Emission animation does not appear when the "Emission Map" parameter is set to black in a Lit material
Add comment