Feedback OnTriggerEnter/Exit triggers when toggling state on iskinematic

This change was introduced in 2019.3 before that the events correctly only fired when a collider entered or exit a triggers bounding volume. I really dont care about the underlying technical change in physx.

Unity is an abstraction ontop of SDKs like Physx. So it should provide a semantic correct API.

OnTriggerEnter/Exit indicates that when a collider leaves or enter the boundaries of a trigger those events will fire. Not when toggling state of the attached rigidbody iskinimatic. My suggestion is that you make sure the events work like before 2019.3. Keep track of which triggers you are inside, and when lower level physx events trigger because of iskinimatic make sure not to bubble this up to the subscribers of OnTriggerEnter/Exit.

This change competently breaks our game, and its unfixable without introducing alot of complexity and not to mention unwanted dependency.

 

Same Issue !!! WTF ?

 

Another option would be to expose a bit of info about the event so that we can decide when we want to use it on our end.

I bug reported this when it also caused issues with our project, and was just told it was by design.

 

Yeah got the same response for my bug report. Its a bit insane though having a event called OnTriggerEnter/Exit that triggers when you toggle iskinimatic state.

Unity should have kept it as is and abstracted the change to a new event if people are interested in knowing when internal flags are changed in PhysX

 

Also there is no clean way of working around this without introducing alot of complexity in your domain

 

Same issue here!