For now I’m working around the issue by creating an Action task that simply yields until the next frame before calling EndAction(). If I place this before the task in the higher priority node sequence I get the expected behavior so I don’t need to guard against this elsewhere.
Login
Register
By registering on this website you agree to our Privacy Policy.