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
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
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