Hey, copying GASP 5.8 implementation to my project and getting this warning when putting in the orientation warping and steering nodes in my BlendStack (MotionMatching) node.
Why?
I have copied all implementation specifics. Can’t seem to find the reason.
That warning means the BlendStack node wants blueprint-driven updates but the wiring it expects didn’t fully come across with the copy. Porting GASP 5.8 into another project only works if all the supporting pieces arrive together:
Copy in dependency order and re-check after: the anim functions and interfaces from the GASP locomotion graph, the motion matching update path (the node’s update is driven through the graph, not standalone), the linked anim layers, and the enums/structs the warping nodes read.
The orientation warping and steering nodes need the locomotion velocity/angle inputs the GASP graph feeds them. If you copied the nodes into a graph without that data path, the node flags itself as needing blueprint updates. Compare the pins against the original GASP node — usually one input (velocity or the update call) is unconnected.
If everything looks identical and it still warns: delete the copied node and place a fresh one from the palette, then re-wire. Copied node state can go stale when the referenced functions live in another class.
If you post the exact warning text, that narrows it further — ‘needs blueprint updates’ specifically means the node’s update function reference is unbound, which points at the copy missing the update function rather than the animation data itself.
