It seems to be by design… So a nested FSM is by default not related and cannot use scene objects. I have to create a bound version on a GO to save it with a button from the scene, correct?
Maybe it would be more intuitive if a newly created nested FSM is automatically attached to the same GO with a new FSM Owner script and be bound, if the parent is as well?
Login
Register
By registering on this website you agree to our Privacy Policy.