Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.27f1
2022.3.3f1
2023.1.1f1
2023.2.0a21
2023.3.0a1
Issue ID
UUM-40607
Regression
No
Raycast hit detection is inaccurate when Camera's "Clipping Planes: Near" value is below 1000
How to reproduce:
1. Open the user-attached project "GraphicRaycasterBug"
2. Open the "SampleScene" scene
3. Enable the "Root2 (BUG)" GameObject in the Hierarchy
4. Select the "EventSystem" GameObject in the Hierarchy and lock it in the Inspector
5. Enter the Play Mode and hover over the Canvas in the Game View
6. Observe the "pointerEnter" field in the EventSystem in the Inspector
Expected result: Raycast hit detection is accurate
Actual result: Raycast hit detection is inaccurate, and for the big part of the Canvas, it doesn't detect hits at all
Reproducible with: 2021.3.27f1, 2022.3.3f1, 2023.1.1f1, 2023.2.0a21
Reproducible on: Windows 11 Pro, macOS 13.4 Ventura (M1)
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
- Missing Mono Scripts in Sample Scenes in URP Package Samples
- Labels to enable or disable Columns for Reflection Probes Clipping Planes do not match actual Column Labels
- Crash upon undo/redo operations performed repeatedly and errors are thrown
- Columns are mislabeled in the Reflection Probes section of Light Explorer
- Resolution is labeled as Near Clip in Cubemap Capture Settings
Resolution Note:
After investigation, we have deemed this a low priority issue that won't be fixed in the near future either because there are risks of introducing other problems doing so. There's also a simple workaround to the reported issue by using reasonable camera frustum values.
If you feel this is a wrong assessment, please reach out again, providing more details about the impact of that issue.