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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
NeverTrustShadows
Mar 27, 2023 10:15
This issue is still valid in 2021.