Search Issue Tracker
By Design
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.0f2
2019.1.0a1
2019.2.0a1
Issue ID
1111499
Regression
No
OnCollisionEnter & Exit events fired for each individual collider on composite colliders
Steps to reproduce:
1. Download latest attached project(1111499-compositecollider.zip)
2. Enter play mode
3. Move "parent" gameobject to collide with another object
Expected result: only one OnCollistionEnter and exit event is activated
Actual result: the event activates for each collider on the gameobject
Reproduced on 2017.4.0f1, 2017.4.18f1, 2018.3.2f1, 2019.1.0a14, 2019.2.0a1
Notes:
- a debug log appears for each collision enter for clarity
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
- Fixing Message Loss in UMPE During Domain Reload
- The Editor freezes when ScheduleReadOnly of IJobParallelForTransform with dependency is used
- Text is truncated in the Inspector when the display scale is set to 150%
- CancellationTokenSource(<timeout>) has incorrect cancellation status when used in WebGL Player
- VFX property value names are cut off when properties with 'Arc' are viewed in the VFX Blackboard
Resolution Note:
Every compound collider is treated as a single Rigidbody and each individual collider in the composite is still treated as its own collider for the purposes of collision. Collision events (Enter, Stay, Exit) happen between pairs of colliders which is why a single Rigidbody can produce multiple collision events if it has a composite collider.