Search Issue Tracker
Fixed
Fixed in 1.4.3
Votes
0
Found in [Package]
1.3.0
Issue ID
ISXB-41
Regression
No
Physics.Raycast doesn't trigger OnPointer events when mouse cursor is locked and Input System Package (New) is used
How to reproduce:
1. Open the user's attached project "FirstPersonTest.zip"
2. In Player Settings change the Active Input Handling to Input System Package (New)
3. Press Play
4. In Game view point the crosshair to a red cube and move the crosshair away after
5. Observe the Console window
Expected result: OnPointerEnter and OnPointerExit events are logged in the Console
Actual result: No OnPointerEnter and OnPointerExit events are logged in the Console
Reproducible with: 1.0.2 (2019.4.34f1, 2020.3.26f1), 1.2.0 (2019.4.34f1, 2020.3.27f1, 2021.2.9f1, 2022.1.0b5), 1.3.0 (2019.4.34f1, 2020.3.27f1, 2021.2.9f1, 2022.1.0b5, 2022.2.0a2)
Note: When the mouse cursor is unlocked, hovering the cursor over the red box, Physics.Raycast detects the intersection
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment