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
- Channel remapping dropdown in the Terrain Layer does not open when clicked on the title
- The Editor freezes indefinitely when a large number of elements are entered in the Subgraphs or Categories lists
- Some Visual Effects package Assets links to documentation are not working
- Heatmap asset’s documentation button in the Inspector window leads to “Sorry... that page seems to be missing!” page when clicked
- Crash on MonoBehaviour::CallMethodIfAvailable when performing various actions
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.