OnTriggerExit triggered when it shouldn't be.

I have a capsule collider inside a box trigger volume. I also have some spheres that fly through the same position as both the capsule and the box trigger. The spheres are filtered to not collide with either the capsule or the box trigger but every so often I get a OnTriggerExit event in a script attached to the box trigger.

The event says that the capsule has left the trigger box when in fact the capsule has not moved and has not exited the box trigger. The capsule is the only object in the scene that can collide with the box trigger. The event seems to happen most often when there are two spheres on top of the capsule and the trigger box.

Is this a known issue or should I try reproduce it in a blank scene rather than sending my entire game? If I do send it what's the chance you guys will actually fix it before I ship my game... This is a pretty ugly bug as it means I cannot trust any OnTriggerExit events at all.

Note that I never get OnTriggerEnter events that I shouldn't. Only OnTriggerExit seems broken.
I'm on the latest version of Unity.

 

I've found a horrible hacky hack of a hack solution to this problem. When I receive the OnTriggerExit event I check the Trigger box with the Physics.Sphere overlap function and use the same radius and position as my player object. When it return true I know the OnTriggerExit event is a bug and I ignore it, otherwise I do things as normal... Seems to be holding up so far. Fingers crossed.

 

I've revisited this issue and I found the real problem here. When a rigidbody enters a trigger zone and then falls asleep inside of it sometimes this event is fired. I believe this is a bug as the rigidbody did not leave the trigger zone at all.

My solution now if to set the rigidbody in questions' sleep variables to 0, preventing it from sleeping and resolving the issue.

 

I've just discovered the same bug and workaround. Would be nice if some Unity engineers could take a look at this bug!

 

+1

Same bug on Unity 3.5.7. This issue totally broke my gameplay.

My workaround was similar to OverlapSphere, but I prefer using a simple math function to determine if object was inside sphere, which was faster for me than rely on Physics.OverlapSphere.

This should be enough critical to release a patch for Unity 3.5.7.

 

From 2023, I can't be sure this is exactly what is happening to me but I think the sleep/awake issue was affecting me as well so this workaround may still be needed even in 2020.3.43f1. The true issue I was facing is that exit/enter would get called when changing to and from kinematic, for my particular issue I just swapped to freezing constraints instead of using isKinematic, but your work around would probably have worked as well for me. Sorry for the necro but I think the info is useful still.