I noticed the warning beside “Enter State Event”, “Left State Event” and “Fully Blended State Event” after upgrading to 5.3.
Where can I access the “anim node function versions”?
If they are the functions bound to a state machine, namely OnInitialUpdate, OnBecomeRelevant and OnUpdate, these 3 functions are now recommended to handle all state events?
I think they added these functions to the state pose output node. I also noticed now there are nodes for calling functions from the anim graph too. Took me a while to figure this out too, they could’ve done a better job explaining that.
I think Epic doesn’t know what they’re doing. The functions must be “thread-safe”. Totally useless since you can’t use call events.
I did notice that. They’re not a replacement.
They run in a different way where they run immediately similar to a branch point, but on the anim thread, while the other version is a queued event on the game thread.
They need to both be supported depending on what you need rather than deprecating the other one.
I wanted to summarize this topic, as this seems to still be relevant in 5.4, there doesn’t seem to be documentation on it, and I spent a good couple hours banging my head against this.
As illYay mentioned, once a function is bound to a State’s result node it can be called in the Anim Graph, albeit with an experimental warning.
Again as illYay mentioned, the functions bound to the anim node must be thread-safe, and therefore don’t have the same functionality as the older anim state custom events. I suspect the warnings are a way to encourage people to use more performant thread-safe functions, but as it stands they simply aren’t a replacement.
After a bit more digging, the answer seems to be a lot simpler. You can implement custom transition events that do the same thing as the state ones. These ones don’t have any warnings, so I suspect they are the preferred method.
I’m not sure why these aren’t recommended over the anim state ones.
Click on this little guy :
then scroll down in details until you find the same things
What @Axiles said. You won’t see a transition rule between entry and your first state because there can’t be a transition there, since there’s no state before your first state.
To clarify, there is no error. You can still use the older animation state events if you want, it’s just that epic now recommend you not use them.
Are these Animation State functions working? I’m puttting OnStateEntry in OutputAnimationPose node in a subanim graph, and it’s not called.
