Search Issue Tracker
By Design
Votes
0
Found in
2020.3.37f1
2021.3.7f1
2022.1.9f1
2022.2.0b1
2023.1.0a3
Issue ID
UUM-10235
Regression
No
SphereCast RaycastHit.point seems to be in local space rather than world space
How to reproduce:
# Open the user attached project
# Open the MyMouseLook script and place a breakpoint in line 112
# Start the debugger
# Enter Play Mode
# Zoom in and/or right-click and drag to make the camera rotate
Expected result: The cast collides with the sphere collider
Actual result: RaycastHit.point is (0, 0, 0) even though the sphere is far from it
Reproducible with: 2020.3.37f1, 2021.3.7f1, 2022.1.9f1, 2022.2.0b1, 2023.1.0a3
Reproduced on: Windows 10 (Intel)
Note: If you disable the breakpoint you will see the camera flickering, alternating its position to (0, 0, 0) for every collision
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
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Resolution Note:
The RaycastHit.point is (0, 0, 0) because the SphereCast does not hit anything. The boolean return value of the method should be checked before evaluating the RaycastHit result.