Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
1
Found in
2019.1.0a12
2019.2.0a1
2019.2.0f1
2019.3.0a1
Issue ID
1174546
Regression
No
OverlapCollider() registers an overlap only at specific points when a CompositeCollider2D with Outlines Geometry is used
How to reproduce:
1. Open the "Main" Scene in the attached "case_1174546-Composite_Collider_Bug" project
2. Enter Playmode
3. Open the Scene Window
4. Drag the Gray box to make its collider overlap completely with a green box collider
Expected results: Gray boxes that have their colliders overlap with green box colliders at any point become red
Actual results: Only gray boxes with colliders that overlap with the left edge of green box collider become red
Reproducible with: 2019.1.14f1, 2019.2.1f1, 2019.3.0a12
Additional notes:
1. Such an issue occurs only when Outline Geometry is set. Setting the Geometry to Polygons fixes the problem, but it is not a solution when a collision needs to be calculated outside the GameObject visual.
2. Project in versions before 2019.1.0a12 could not be compiled due to missing references to asmdef files.
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
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
Resolution Note (fix version 2020.1):
Internal overlap AABB was being calculated incorrectly. Also the edge-radius wasn't being taken into account.
Resolution Note (fix version 2019.3):
Internal overlap AABB was being calculated incorrectly. Also the edge-radius wasn't being taken into account.