I get the impression that Muse Behavior always does it’s updates during Update(). In some cases, I would prefer it to run on FixedUpdate() (because the behaviour actions need to do stuff with physics). I’d like to request this be made configurable on a per-agent or per-behavior basis if possible… or if it is already possible please let me know how! Thanks, kind regards,
Andy
1 Like
Hi @Andy-Block ! It’s currently not possible. Would you like the entire graph to tick on FixedUpdate, or would you like us to expose a FixedUpdate and potentially LateUpdate methods to the nodes so all the options are called correctly? That way we can maintain certain updates in OnUpdate but others will be moved to FixedUpdate?
Thanks!
~ Shanee
Hi Shanee,
For my purposes, either would work fine, but I guess you are correct that supporting having multiple update actions called in a single action would be the most flexible. Hope to see it in a future version then, thanks! Kind regards,
Andy
1 Like
Are there any updates <_< regarding this topic? I am currently working on 2d physics-based game. Game Agents should change behaviors regularly (after collision and conditions are met). Behavior Graph looks such a great solution in this case. But I have concerns about OnUpdate method, currently, I am using FixedUpdate. Should I use behavior graph or for physics-based games, it is not useful yet?
Looking forward to your reply!
Hey @feanture_unity ,
Unfortunately not yet! We’re focusing on bug fixing and handling issues reported by users, but we’ll look into it soon.
Can you give this a try as it is and let us know how it works? Most logic should still be maintained in OnUpdate anyway, it’s mostly physics calls that should be in FixedUpdate.
1 Like