Yeah, I have only one playmaker gui component. And I like it that you batched/optimized them! There's something slippery going on though and I'm having a hell of a time nailing down exactly what it is. Not sure I can without seeing under the hood, and maybe I'm just implementing something in a completely wrong way! Some details, if it helps:
- I have one Playmaker gui component, and all the FSMs are on it
- I have seven FSMs, with either GUI buttons or a background texture in them. But the behavior started to show up when I added my second FSM. I can "fix" the behavior by deleting the offending FSM, and recreating it from scratch. But then the behavior pops up somewhere else.
- I did copy/paste a couple FSMs, and it was right around then the bugs started. Might be related
- All FSMs are fairly simple, 3 - 5 states, toggle buttons between on/off and set some global vars, etc
- The creation of a new FSM with a button is the thing that changes the behavior of previously created stuff. This is trigger that makes the magic happen!
- I've tried using GUI Depth in various places. It doesn't seem to give me any noticeable results, and this bug/behavior happens whether or not GUI Depth is present in any states
- I am using a GUI Skin. I've tried applying it globally once and individually in several places, and it seems to make no difference in the behavior of the bug.
Hopefully something in there helps narrow it down!
Thanks!