Search Issue Tracker
Fixed in 2018.1.X
Fixed in 5.6.X, 2017.1.X, 2017.2.X, 2017.3.X
Votes
0
Found in
2017.1.0f3
Issue ID
932044
Regression
No
OnCollisionExit2D isn't always triggered when using polygon/edge colliders and multiple collision points
How to reproduce:
1. Open "repro-project" project
2. Open "Tester" scene
3. Play and observe Game View
Expected result: Both the "Square" and "2Points Polygon Collider" gameobjects should trigger OnCollisionEnter2D and OnCollisionExit2D the same amount of times, resulting in the counter numbers (black text) never exceeding 1.
Actual result: "2Points Polygon Collider" gameobject triggers OnCollisionEnter2D more times than OnCollisionExit2D resulting in counter number always increasing.
Reproducible with: 5.5.1f1, 5.6.0f1, 2017.1.0f3
Fixed in: 5.6.4p1, 2017.1.2p2, 2017.2.0p1, 2017.3.0b5, 2018.1.0a1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment