Search Issue Tracker
By Design
Votes
0
Found in
5.3.3f1
Issue ID
777460
Regression
Yes
SphereCastAll and SphereCastNonAlloc cast inside collider return hit point is 0,0,0
Steps to reproduce:
1. Open attached project "777460.zip"
2. Open scene "repro"
3. Make sure Console is visible and run the scene
4. Notice that once sphere cast origin is inside collider (cube) then returned RaycastHit.position is (0, 0, 0)
Regression introduced in: 5.3.0b5
Not reproducible: 5.2.4f1, 5.3.0.b4
Reproduced with: 5.3.3.p3, 5.4.0b9
Comments (3)
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
- TreeView.AddItem performance regression when opening EditorWindow
- Shadows are not visible in Player when using DX12 with Forward+ or Deferred+ rendering in URP
- Rendering Debugger Playmode debug UI scrolling is jittery when using click and drag to scroll
- Frame Debugger Target Selection Search Results window becomes too tiny to even see the default “Editor” selection when there are no search results
- Async method in Play Mode being aborted when calling `new System.Windows.Forms.Form`
Vectrex
Feb 22, 2025 09:23
Bizzare behaviour. When would 0,0,0 ever be by design??
Zergling103
May 27, 2018 03:05
How the **** is this by design? It just seems broken to return a point at 0,0,0 when the object is nowhere near 0,0,0.
xiaohai_pan
Oct 19, 2016 05:24
Reproduced with: 5.4.0f3