IK Foot Tracing Checks failed w/SkeletalMesh Merging

Hello!
I had set up a skeletal mesh merging with the tutorial that is in Unreal Engines website for Modular Characters. My game is mostly comprised of C++ but I did the Skeletal Mesh Merging using the blueprint nodes since thats whats in the tutorial. Problem is i also have IK Foot tracing that is in Blueprint but has variables in C++, such as, groundspeed. I use the ground speed to determine if the IK foot tracing should or should not happen. If ground speed == 0 then the IK Foot trace happens. This is done with a blended pose node. When i did the skeletal merging my IK was constantly on. The character was iceskating around because his feet where stuck to the floor. I did testing using onscreen debug messages and the ground speed is working correctly and the charactermovement component is also working properly. But the IK is still being activated regardless of the Groundspeed==0 boolean. I tried this with my normal character without the merging and it works fine. its the skeletalmesh merging that is the only thing that is changing. Does anyone know why this is the case? Im looking for resources on why it happens, a solution would be nice! But i mostly want to understand why because I am learning the engine.

If you’re using ground speed == 0 as a bool for for Should Do IK Trace input on control rig node, it might just never be reaching 0. float == nodes can be a pain when the cpu decodes to stop at 0.00001 or something instead of continuing all the way to true 0. Should probably use a nearly equals node with enough tolerance for precision errors or just use a speed <0.5 or something.

The float comparison is worth ruling out, but it does not match what you already measured. Ground speed on screen is correct, and the same graph works on the unmerged mesh. The merge is what changes the result, so the AnimBP is almost certainly reading a different instance than the one you are debugging.

SetSkeletalMesh, and the Merge Meshes node, reinitializes the anim instance on that component. GroundSpeed on the new instance comes back at its default of 0, so the “only trace when stopped” blend stays in the IK pose and the feet stick. Printing velocity from the character movement component still looks right, because that was never the value the new anim instance is using. After the merge, call Get Anim Instance on the component that actually displays the merged mesh and write GroundSpeed there every tick. A UAnimInstance pointer cached before the merge is stale.

Two other merge-specific causes of “IK Foot Tracing Checks failed”:

The merged skeleton dropped the bones the rig expects (ik_foot_l / ik_foot_r, or the virtual bones the control rig was built against). The stock merge only keeps bones from the skeleton you pass in as the base. If that is a different asset than the one the AnimBP control rig was authored for, the rig fails its hierarchy check and leaves the effectors at the last solved pose, which also looks like feet glued to the floor. Open the merged mesh and confirm those bones are still there, and that the Control Rig node points at that same skeleton.

On a modular setup the visible mesh is often a follower with Set Leader Pose Component, and the AnimBP runs on the hidden leader. Writing the bool on the follower does nothing, because the follower does not tick an anim instance. Keep the AnimBP on the leader and drive the blend from that instance.

Also make the foot trace ignore the pawn. A merged mesh often picks up a physics asset the old mesh did not have, so the trace starts hitting the body and the feet plant on the character. That is secondary to the anim-instance reset, which is what keeps IK on while the character is moving.