Can you please show a screenshot of your FSM and also expand on the ‘FSMState.OnExecute’ in the profiler to see what is actually causing this. It seems this is not from initialization, but rather from what the FSM STATE is actually doing in its execute.
Gavalakis
