Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.2.X, 2019.3.X
Votes
0
Found in
2017.4
2018.4
2019.2
2019.2.5f1
2019.3
2020.1
Issue ID
1190905
Regression
No
Physics2D.BoxCast doesn't detect the "Edge Collider 2D" when hitting the Collider's corner
How to reproduce:
1. Open the attached project's ("case_1190905-Project.zip") Scene labeled "IssueScene"
2. Enter the Play Mode
3. Press the Right Arrow key on the keyboard a few times
4. Observe the Game View
Expected result: there's a collision point shown on the corner of the Edge Collider
Actual result: the corner of the Edge Collider is ignored and the cube passes it
Reproduced in: 2017.4.33f1, 2018.4.11f1, 2019.2.10f1, 2019.3.0b7, 2020.1.0a9
Note: there's no issue when the corners of the Collider and the Raycast is not at the same height
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment