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
- “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
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