Search Issue Tracker
Fixed
Votes
4
Found in
4.3.0f1
Issue ID
573682
Regression
No
OnTriggerEnter2D called too many times
To reproduce:
1. Open the "Unity Projects 02: 2D Platformer v2.1" from the Asset Store
2. Open the scene called "Level"
3. Attach a script with "void OnTriggerEnter2D() { Debug.Log("enter"); }" to "hero"
4. Run the scene
5. Notice how "enter" is logged many times when player gets thrown to the river by zombies (dies)
Comments (24)
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
- Memory leak occurs when focused on Player while using Direct3D12
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
haan
Nov 07, 2014 06:16
I am getting this issue in 4.6 beta. OnTriggerEnter2D is called 2 times. Is there any condition when this issue happens?
@BUBURIMU what was your problem? And how did you solve that problem.
druphoria
Aug 06, 2014 04:17
I'm also experiencing this issue. OnTriggerEnter2D is calling too many times and OnTriggerExit2D is sometimes being missed altogether.
Tricephalus
Jul 15, 2014 12:21
I'm using 4.5.0f6 and it's still present. OnTriggerEnter2D still keeps getting called while the two triggers are in contact, and not just once when they intersect.
buburimu
Jun 26, 2014 02:14
My code was broken: the issue seems resolved in 4.5.1f3 (Mac). Sorry for the wrong report!
buburimu
Jun 24, 2014 06:50
Still here in 4.5.1f3 (Mac). Worked around with a flag but still... it's not fixed
coshea
May 15, 2014 15:03
Says here fixed in future release, but no idea when :) http://issuetracker.unity3d.com/issues/ontriggerstay2d-is-called-not-properly
siceblue
May 12, 2014 03:25
Still present in 4.3.4f1. I need this fixed
IntDev
Mar 28, 2014 17:47
Still present in 4.3.4f1. I need this fixed. HELP.
rjoly
Feb 01, 2014 15:35
still in 4.3.4f1.
Jason Tartaglia
Jan 27, 2014 18:27
How do we track resolution of an issue to deployment in an update? Meaning, is there a way for me to tag this issue so that when the fix is actually deployed I will be notified? I can't think of an acceptable workaround for this issue and will be waiting on the fix.