Cool Bug.
This is misbehaving in more than 1 way. I’m looking at the underlaying class - will let you know if I find something. Meanwhile, you can use this:
Need to find out what else Event Hit is doing besides the obvious. Interestingly enough, if you query the primitive’s collision state, it reports it incorrectly, no matter what behaviour we’re after.
Here’s the Won't Fix bug:
But there’s more to it. It’s a Won't Fix for a reason - it’s about how the physX interaction is designed. @MilionX The proper way of doing what you need:
