Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
2
Found in
2019.2.17f1
Issue ID
1212896
Regression
No
OnTriggerExit2D when disabling a GameObject
How to reproduce:
1. Open the attached project ("case_1212896-OnTriggerExit2DBug.zip")
2. Open the repro scene ("SampleScene)
3. Enter Play Mode
4. Run, click Toggle Sprite : OnTriggerExit2D gets called.
5. Inspect the console
You can verify that Destroy does NOT call OnTriggerExit2D as expected by clicking Destroy Sprite. Disabling a Game Object using SetActive(false) should have the same effect and NOT call OnTriggerExit2D.
OnTriggerExit2D is incorrectly reported when a GameObject is disabled with Physics2D.callbacksOnDisable set to false. OnCollisionExit2D is not reported as expected.
Comments (1)
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
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
- "OnTriggerExit2D" is called before "OnTriggerEnter2D" when object is destroyed immediately
NeverTrustShadows
Mar 27, 2023 10:15
This issue is still valid in 2021.