Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.3.X, 2020.1.X
Votes
0
Found in
2017.4
2018.4
2019.3
2019.3.0f1
2020.1
Issue ID
1219837
Regression
No
BoxCollider2D with an EdgeRadius > 0 results in "Physics2D.queriesStartInColliders" being ignored for queries.
Reproduction steps:
1. Open user's attached project "2d" and scene "SampleScene"
2. Enter Play Mode
Expected result: Raycast from both boxes doesn't detect any Colliders
Actual result: Raycast, from the box with EdgeRadius greater that 0, detects a collision with the Collider that it originates from
Reproducible with: 2017.4.37f1, 2018.4.17f1, 2019.3.3f1, 2020.1.0a24
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
- [Android][iOS] The keyboard closes and re-opens when consecutive input fields are selected
- Complex Sub Graph connected to a Voronoi node is ignored when the shader gets applied as a Material
- Compute Shader property not set error when entering play mode with path tracing and PBR sky
- "WebGL Publish" detects WebGL module and allows building when it is installed without restarting the project
- Editor is non-responsive and flickers when multiple Water System instances are enabled
Resolution Note (fix version 2020.2):
This is caused cause when EdgeRadius > 0, edges of a polygon use a capsule intersection test. Unfortunately that test didn't take into account that one side of the "capsule" will be an interior edge therefore should not be detected. This has now been fixed.
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0b2
Resolution Note (fix version 2019.3):
Fixed in 2019.3.10f1