Circle collisions, no longer acting as accurate as in Previous Unity Versions

Hello all, thanks for reading!

My game's collisions were working fine before updating to 5.2.3 (not exactly sure which version it was at before... but it would have been active at Feb 2015)

Regardless, now my 2D character (with a circle collider, colliding with other circle colliders) seems to go past the boundaries of the circles quite often, (about 1/4 of the way into each circle) when it used to not do that at all... Any ideas as to what might have changed in the versions from Feb 2015 to 5.2.3 that might have them computing differently?

Thanks all!

 

I also discovered that Unity 5.2.3 2d physics not working properly. If you'll have collision detection set to continuous, then system does not always call OnCollisionEnter2D, only occasionally.
Also I'll have other problem in game where I modify ground collider (breaking a world) after collision inside OnCollisionEnter2D method, but now it seems that there is no always collision impact and object go much deeper in the ground. For this other case collision detection is set to discrete, but there is joints in the object.

Edit: With a quick look, it seems that 5.2.3p2 fix all those problems!

 

More test with a version 5.2.3p2 and now it seems that OnTriggerEnter2D called only occasionally.

Edit: More test. Trigger start with OnTriggerStay2D and exit with OnTriggerExit2D, but only sometimes OnTriggerEnter2D is called.

 

Here's an image of when the collision usually occurs. the BLUE arrows show the collision circle around the bubble and the fish that SHOULD be colliding. The Red arrow is pointing to a collision circle that is used for hit detection from a touch, so, no collision with other objects in scene is necessary, please ignore that.

We have looked into discrete vs continuous types, and the collision layers.

Thanks again!

 

Hi I have the same problem, After upgrade 5.2.3f1 the physics doesnt work anymore. I have to 4.2.2p3 and Its work well

 

... seems kinda like a big deal, no? anyone?

 

Hi,

On our project we are using v5.2.3p2 and the bug still exists.

 

It still exists in my project at 5.2.3p2 as well

 

I submitted some info via Unity's Help>Report Bug menu, however it did not give me a number to attach here.

 

Hey just to let you know I'm also experiencing this issue. Circle collider OnTriggerEnter function gets called very, very rarely. using patch 5.2.3p2 on Mac. Happened as soon as I updated to the latest patch.

 

Sorry for the way this thread is unfolding, I really appreciate the help and attention you are offering
Here is a bug report # 751578
I'm using this as the only code in for collisions. on the ball, as you will see in the report, but here for quick reference:

Code (CSharp):

1. void OnCollisionEnter (Collision collision){
2.         if (collision.gameObject.tag == "thumb") {
3.             this.GetComponent<Rigidbody> ().AddForce (Vector3.up * upSpeed);
4.         }

This is newest report # (based off a simpler project that shows the same issue), this is the number I received for the first report (751496) which can be deleted, as it has less information bundled with it.

 

K.
751578 uses 3D collisions, and the other game (image above with the fish) uses 2D circle colliders. However it seemed the resulting collision accuracy was similar. My apologies for grouping the two together. So, technically, I'm having issues with both 2D and 3D.

 

I worked with @skinnysimmons on the initial screenshot he sent (fish and bubble). I tried to recreate a bare scene with 3 circles that mimic the behavior that was used in that game. I was about to post it, then I saw Unity 5.3 just came out so I upgraded to that and I'm still getting the same overlapping.

It may have something to do with the speed of the object and how we are moving the object with Vector2.MoveTowards on a kinematic rigidbody. Though at the speed we are moving I wouldn't think we would get that much overlap even using discrete detection and as skinnysimmons said, this setup worked great on Unity 4.x back in Feb.

It was a fairly large upgrade to 5.2.3, so it would not surprise me at all if there is some setting that was added that we need to adjust to get this working again, but we have done quite a bit of digging into this and haven't had much success.

If you press play and pause right away you will see similar overlap to the screenshot.

 

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.     }

 

Sorry but I think you are being rude with answers like "Please don't hijack threads like this." and "Let's stop the 'me too' until we get some real information otherwise these threads become confusing."

As you asked I provided more information about the problem instead of just saying me too... I thought you would prefer to have all the related issues inside the same thread to gather all the useful information from you users in just one thread instead of all of us spamming new threads with the same bug. But... if you prefer so, I created a new thread for this issue.

Regards.

 

@MelvMay Hey, I also want to say that my Physics2D.OverlapArea checks which were working in 5.2.2 started malfunctioning in 5.3. I'm also doing stuff in Update and using my own custom Character Controller and I basically used Physics2D as utility methods to check bounding boxes and to do raycasting, and since they worked in the previous version I think you guys must have messed something/somewhere up. Some of the changes you've made must have influenced this.

I'd really like to know why these things are happening right now.

Regards

 

Thank you for all your help @MelvMay

 

@MelvMay it looks like your solution will solve our problem. Not sure how I missed it, but I was not even aware of the Rigidbody2D.MovePosition method. I think we were just lucky that it was working so well before. Thanks!