- Home /
Delayed Collisions Bug (includes video demonstration)
A video explanation of this bug can be found here.
There appears to be a serious flaw in Unity related to when collisions are triggered. Both OnCollisionEnter and OnTriggerEnter are called on the frame after the objects intersect. This seems to happen with every collision in Unity and is more noticeable when objects are moving quickly because you will see the object clip through the object it hits before the collision occurs. I was surprised this has not been mentioned much because it's one of the first things I noticed when I started working with Unity.
Please help me out with this one. If you believe it's a bug, submit a bug report in Unity so that it will be fixed. I already submitted a bug, but more reports will help it to get fixed faster. The reason I posted this was to confirm that it's a bug and that I'm not just doing something wrong. Does this appear to be a bug to you? Thanks.
Well, sounds like you're right ! Can't believe I never noticed that. For one second I thought it could be print waiting the next frame, but accessing a null reference does send the error at the same time as well. Not to be pessimistic, but that guy didn't have any success.
Yeah that was one of the few posts I've seen mention it. I thought if I included a video it might get more attention. If a lot of people contact Unity about it they're more likely to address it.
I couldn't send a report, I think it's because there was some log missing :/
It's supposed to send your project file when you report a bug so that they can reproduce it. Not sure why it wouldn't work though.
Answer by Jay-Pavlina · Feb 29, 2012 at 03:43 AM
Unity responded to my bug report and said that they are sending it to the developers to be fixed. So it was a bug, and it's being fixed. Yay.