Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.32f1
2022.3.14f1
2023.2.1f1
2023.3.0a15
6000.0.0b11
6000.1.0a7
6000.2.0a1
7000.0.0a1
Issue ID
UUM-56638
Regression
No
“OnMouseEnter” or raycast is triggered when the cursor is not on the target object if the object is moving together with the camera
How to reproduce:
1. Open the user’s attached “Ray timing demonstration.zip” project
2. Enter Play Mode
3. Place the cursor near the arrow where “Hold mouse cursor here ->” text is
4. Press the spacebar button
5. Observe the Game window
Expected result: The Cube in the middle doesn’t change its color
Actual result: The Cube in the middle does change its color
Reproducible with: 2021.3.32f1, 2022.3.14f1, 2023.2.1f1, 2023.3.0a15
Reproduced on: macOS 13.5.2 (Intel)
Not reproducible on: No other environment tested
Notes:
- this happens both using simply an “OnMouseEnter” event on the target object or a direct raycast from the camera itself onto the object (user’s info)
- reproducible in the Editor and Standalone Player (macOS)
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
We would suggest migrating from the Input Manager to the newer Input System.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.