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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
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.