One way to improve performance in Unity is to only have one MonoBehaviour call all the updates for all your components. This drastically saves on the overhead cost of the C# to C++ invocation.
In the profiler it shows MonoBehaviour calling PlayMakerFSM.Update for every FSM on every GameObject.
I tried setting the update to manual and calling the update myself and that works, but there are still calls to the MonoBehaviour PlayMakerFSM.Update methods. So even though it's not doing anything in the update it still pays the overhead cost of calling it. Which means setting it to manual update and calling it with one component doesn't save anything.
Is there anyway to setup PlayMaker to use this pattern to gain performance?
