I am creating this thread so we can speedup the UAF Users exploration.
This post started this for me.
thank you David Martinez for sharing
Here is an update on Davidโs Post. He made a nice and clean version. He is figuring out a problem making it hard for him to share her and asked me to share this second itteration. Here it is!! Thanks again to David Matinez 
How to setup Mover 2.0 + Unreal Animation Framework (UAF) + Motion Matching in 5.7 | David Martinez
linked in link as well
Here is a list of differences i found in 5.6
1- UAF systems are named Modules
2- motion matching node doesnt exist in the animation graph and you have to create your own trait stack
updated list:
1- UAF systems are named Modules
2- motion matching node doesnโt exist in the animation graph and you have to create your own trait stack.
3- i couldnt make the chooser table work simply just with the character blueprint as inputs to the table.
I had to use AnimNextDataInterfaceInstance
Then input nothing to the node in the UAF animation graph
I also used a UAF data interface asset to create variables in my UAF Module and anim graph
4- (Probably not just 5.6)i had to add this logic to the module to support multiple meshes.
1 Like
An Important point to not get crazy on 5.6 UAF is to avoid double click a child node of a module in the workspace view.
It crashes 100%
1 Like
Hi. Only one animation plays (moving back) and then the SKM stops. Maybe you have an update for UE 5.6/5.7?