Just to confirm, how are you Pausing the FSM? Are you doing it from within the FSM itself and if yes, do you use the included “GraphOwnerControl” action, or a direct call to PauseGraph()?
If you check the “GraphOwnerControl” action code, you will notice that for that reason, Pausing, or Stopping the graph from within it’s own update call, is done with a co-routine that simply yields one frame. This way, Pausing or Stopping the graph is called after the Update call is completely done.
What you do though to solve it seems quite logical as well 🙂
I will take a look at if your fix creates any other problems and if not I will make that change as well, otherwise I will try find an alternate solution, since I understand that a co-routine solution like it is done in the included action, is certainly not ideal.
Thanks again for taking the time to explain the situation thoroughly!
Join us on Discord: https://discord.gg/97q2Rjh
Login
Register
By registering on this website you agree to our Privacy Policy.