Hey everyone,
So my company has recently upgraded to Unity 5.3.1f1 and the PlayMaker 1.8 beta, and noticed that we're having some issues with one of our previously working features. We had a button that with an attached MeshCollider set to be a Trigger, but we've noticed that Actions are no longer responding to the TRIGGER STAY and TRIGGER EXIT events.
If I use a TriggerEvent action, I get the same results. Both scenarios will respond to On Trigger Enter (TRIGGER ENTER) and transition to the desired state, but will not respond to Stay or Exit events. On the other hand, if I write a MonoBehaviour that uses OnTriggerStay/OnTriggerExit, everything works as intended.
Please keep in mind that this only seems to happen when using a combination of Unity 5.3.1f1 and PlayMaker 1.8; if you use the PlayMaker beta with Unity 5.3.0f4, functionality is as intended. I think that Unity 'fixed' some issues with collisions and triggers in 5.3.1, and I'm worried that might have unforeseen ramifications. I haven't tried reverting back to 1.7 yet, or tried the newer patches of Unity, but I'll keep everyone posted on any further developments.
If anyone else has any feedback, or can also confirm this, it would be greatly appreciated. I've tried a number of things recently, and given the time-sensitive nature of my company's project, this has been a rather significant hurdle. In the meantime, thanks for your time.
UPDATE: Issue still occurs with 5.3.1p3.