OnTriggerExit2D not firing when Kinematic Rigidbody Collider exits Trigger Collider

I have two objects:
- Object1 has BoxCollider2D with isTrigger checked.
- Object2 has BoxCollider2D with isTrigger unchecked and RigidBody2D with isKinematic checked.

When Object2 exits Object1, why does Object1's OnTriggerExit2D not get called? According to the Collision Action Matrix below, OnTriggerExit2D should fire.

 

In my experience, without a non-kinematic rigidbody, triggers and collisions just don't fire in 2D, Collision Action Matrix notwithstanding.

 

I see. So when it comes to 2D, the Collision Action Matrix is not accurate? Hmm, I wonder if this is a bug or just bad documentation (or maybe I did not read it properly).

 

I'm pretty sure it's a bug, but don't take my word for it. Try testing the behavior of ontriggerstay2d too. From my knowledge this is a bug that has been fixed already but not in a public release.

My new project is a 2d game but I'm not using 2d physics for now. It's all too new and a bit rough around the edges

 

It is by design that a 2D kinematic rigidbody does not fire an OnTriggerEnter/Stay/Exit2D event.

Link: Issue Tracker

 

Thanks! Not the answer I was hoping for but at least now I know the current status of the issue. If it is really "by design", someone should probably update the documentation then.

 

Is that status confirmed by a dev? I'm skeptic.

 

Read MelvMay's comments in this thread: 2D Physics: Collisions/Triggers

 

You're right! well that's a bummer. But I know there is a bug with these trigger functions that is not by design, where they fire erratically. I was thinking of these bugs.