OnTriggerEnter2D stopped working.

Hello,
i'm using Version 5.2.3p2 and OnTriggerEnter2D(Collider 2D) is not working with Collider2D, PolygonCollider2D, BoxCollider2D nor CircleCollider2D. I can check the objects are colliding with a simple print to the console on OnTriggerStay2D() but the collision is not triggered when it starts.

The weird thing is that sometimes it works and others it doesn't. Another important thing is that I didn't change any of the objects' properties or code for more than one year and it stopped working with the last Unity updates.

This is my code:

Code (CSharp):

1.     void OnTriggerEnter2D(Collider2D otherCol)
2.     {
3.         var enemy = otherCol.GetComponent<Enemy>();
4.         if (enemy == null)
5.         {
6.             //Debug.Log("enter field no enemy component " + otherCol.gameObject.name);
7.             return;
8.         }
9.  
10.         enemy.EnteredField();
11.     }

 

I had the same problem. The work around for me was adding a rigidbody2D, set kinematic to true. Then triggers worked.

 

Sure, some more detail. After I updated to the patch release v5.2.3p2 my animating GameObject with 2d collider triggers stopped working. I found I needed to add a rigibody2d to make the triggers work. And marked it kinematic since I was animating the object and not using physics.

And was the same problem, sometimes it would trigger, next run it wouldn't.

 

@MelvMay Thanks for the update. It seemed like I had an incorrect setup to start with, then needed to update to the correct method.

 

I am saying that sometimes I never receive one OnTriggerEnter although I receive OnTriggerStay every frame and other times I do receive one OntTriggerEnter followed by OnTriggerStay every frame. I tried with older versions of Unity such as 5.2.2p3 and 5.2.2p4 and it worked fine as in the past did. I think this problem just started with the version 5.2.3.

I read what you wrote on the other thread

... about manipulating the Transform of the objects not "activating" the physics system and it makes sense to me, but that means I must change all the old code I used to move objects in all my project..

As you said:

and if I understood it well, If I wait for your update/fix I don't need to change all the code on my project because it will work again??

 

@MelvMay Hey, I just wanted to ask something which seems related to this since updating to 5.3 some of my Physics2D checks seem to be malfunctioning.

If I use Transform.Translate to move my character which has a BoxCollider2D and a Kinematic Rigidbody2D, does this mess up some Physics2D stuff with the new updates? It worked fine in 5.2.2, but I'm wondering if there was a change in the new update related to this? Is there any method that I could call on the RigidBody2D to fix it after I do my Transform.Translate? Or do I have to use RigidBody MovePosition or set the velocity.

Cheers

 

hi @MelvMay

I'm just wondering what the correct procedure is from now?

Can I suggest 4 cases as I would normally go about making:

1. Door. Collider on door sprite, set to trigger, script using OnTriggerEnter2D
2. Animated tentacle. Collider on each segement, each segement is animated from a root object. Player is hurt when entering this collider using OnCollisionEnter2D and layers or tags to tell what layer the tenticle colliders are on.
3. Bullet. Collider on bullet, script on bullet that removes bullet with OnCollisionEnter2D
4. Left to Right enemy. Driven by Update, the enemy is moved by transform.Translate and has a Collider attached.

Case 1,2 & 4 don't use RigidBody2D

Currently 2 & 3/4 in Unity 5.3 don't make the bullet disappear if it hits the colliders.

 

@MelvMay I've made a quick demo setup and submitted as a bug, hope it helps

 

seems the bug reporter doesn't email us anymore (can't get case number) so it's in there somewhere! I set up a collision demo

 

I found it in the system, it was closed and has been marked as a duplicate of http://issuetracker.unity3d.com/iss...lisionenter2d-is-only-called-for-the-last-one

case 752567