Search Issue Tracker
By Design
Votes
1
Found in
2017.3.0f3
Issue ID
1005906
Regression
Yes
Shape raycast with a dimension set to 0 and hitting at an angle reports incorrect hit.point
Dev notes:
https://docs.unity3d.com/ScriptReference/Physics.SphereCast.html:
Notes: SphereCast will not detect colliders for which the sphere overlaps the collider. Passing a zero radius results in undefined output and doesn't always behave the same as Physics.Raycast.
Any shape casts with zero radius/size are very likely to produce undefined results. It's better to just use normal Raycasts in those situations.
Steps to reproduce:
1. Download and open the latest attached project("Repro.zip")
2. Move the "RaycastHelper" gameobject around the scene to hit objects at an angle
Expected result: hit.point is always where the Raycast hits
Actual result: hit.point is often reported at the start of the Raycast or behind the actual hit
Reproduced on 2017.1.3p1, 2017.2.2f1, 2017.3.1p2, 2018.1.0b9, 2018.2.0a1
Notes:
- This happens with every shape collider, with radius needed to be set to 0 for the bug to occur
- The project provides a visualization of where the hit occurs, placing a debug display at that point
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
- [Build Profile] [VisionOS/iOS/tvOS] - Build Player Library button is getting displayed depending on the selected build target
- EnsureRunningOnMainThread error in TessellationJob.ApplyInset
- MultiColumnListView causes a memory leak when repeatedly shown and hidden
- Position Node with Object Space has a wrong value when there are multiple active GameObjects with the same shader
- [URP][RG] Fullscreen blit is not working when Render Graph is enabled
canis
Mar 07, 2018 03:43
https://youtu.be/8cdw7g8MLXQ