OnCollisionEnter2D & OnTriggerEnter2D on 5.3 not working?

Seems OnCollisionEnter2D & OnTriggerEnter2D are very slow to register, or don't react at all. Like a threshold has been increased?

My game relies heavily on these interactions, so 5.3 is not really useable without a fix.

Anyone else?

 

I'm having the same issue since updating to 5.3 today for OnTriggerEnter2D. Code didn't change, but it stopped calling.

 

My collisions are working for the most part, but when I collide with one of my "Warp" colliders (I use it to teleport the character to another portion of the zone) it teleports me to the target I have set up but after maybe half a second it moves my character in a random direction. I had the same issue back in 5.2 which made me go back to 5.1 -_-

 

Is this the 0,0 bug? I think that was fixed.

 

I found a fix... I think this was being caused by my parallax script moving the colliders manually using transform.position. They stopped registering when I did that. However I was able to fix by adding a rigidbody to the collider and setting it to Kinematic.

 

Mine stopped working as well. I've tried rigid bodies on everything & break points to step into the code but nothing is registering (collisions or triggers)

 

Same problem. I have a few standard enemy prefabs with some sort of EnemyBehavior script attached to them. Technically they all are almost identical but few of them just don't call OnCollisionEnter2D methods. Sometimes when I manually changing the layers or tags (lets say from enemy to default and then back to enemy), everything works. But it also happens from time to time, not always.

 

I think we can safely say it's not working properly, seem to be a few threads about it.

 

The op on another thread just raised a bug report

 

The same problem here, but i think i fix it. I replace my collider2d from prefab chaild gameobject to main gameobject and now ontriggerenter2d work fine.

 

BTW the bug reporter doesn't send out emails with the bug number any more, sorry.

 

I had no rigid body2d on my moving objects (sprites with a circle collider) so just used transform.position for them. I had a kinematic rigid body on the ground object that had a collider on it.
Edit: & the collisions, & triggers when I tried them, didn't fire at all.

 

I didn't realise the rest of the sentence didn't actually appear on screen (a common problem since I need to look at the keyboard to type). I edited my post to say that using rigidbody2d didn't make any difference for me.

 

Submitted a report: (Case 774128)