Sockets and Object Origins when animating (Pose Leader and Copy Pose)

A bit confused on where object origins and sockets should be for modular characters.

What works: Object Origin and socket = World Origin Mesh stays in-place (rather than geo to world origin)

Then attach the skel mesh asset to the Leader Pose Component

Do static objects work as follows?:

Blender: Mesh Geo AND Origin = World Origin

Unreal: Socket is attached to bone and offset to fit

so far, Pose Leader hasn’t worked for me when my socket isn’t at world origin. If I offset a socket to correct it, I get major following-lag during anims.

I’m having trouble understanding, through docs and tuts, when to use which methods. And I’m sure I’m misunderstanding some principles along the way.

For objects with anims of their own, should they use Copy Pose from Mesh and a Socket? My understanding is that Leader Pose Components only allow objects to follow their Parent Bone.

Crude illustration from my notes for reference

The lag is what you get from mixing two different attachment models. Leader pose is not a socket attach.

Set Leader Pose Component copies the leader’s bone transforms onto a follower that shares the same skeleton (same bone names and hierarchy). The follower’s vertices stay in the leader’s bind-pose space. Both meshes need the same origin: character root at the origin, geometry skinned in place, component relative transform left at identity. You do not also attach that component to a socket.

Leader pose writes bone transforms every tick, and a socket attachment writes the component transform from the bone. Those two fight, and you see a one-frame follow. A socket left at the world origin hides it, because the extra transform is zero. Offset the socket and the lag shows up. That matches what you already found.

Use one of these, not both:

Skinned modular parts (torso, arms, clothing on the same skeleton). Leader Pose only, or Copy Pose from Mesh if that part needs its own AnimBP. Parent the component to the capsule or the mesh with a zero relative transform. No socket. In Blender the origin matches the master mesh origin. Copy Pose and Leader Pose are alternatives, not a stack. Copy Pose is the one you want when the follower still needs an AnimBP. It still does not want a socket offset on top.

Rigid props (sword, hat, any static mesh). Socket only. No leader pose; a static mesh has no bones to follow. Put the mesh origin at the grip pivot, put the socket on the bone at that same pivot, attach, and leave the relative transform at zero. Authoring the prop at the world origin and the socket at the world origin also works, but then the socket is not really on the hand. If you then offset that socket, you are moving a mesh whose vertices are already in skeleton space, so it drifts.

Props with their own skeleton and their own animation. Attach to the socket for placement, and play that mesh’s own AnimBP. Do not set Leader Pose unless the skeletons match, and do not Copy Pose across different hierarchies.

Rule of thumb: origin at the attachment pivot for rigid props; origin at the character root for anything skinned to the shared skeleton.

If a correctly socket-attached rigid prop still lags, the skeletal mesh is ticking after the attachment. On the attached component, add the leader mesh as a tick prerequisite so the socket updates first. For the modular skinned pieces, delete the socket attachment instead. There is nothing there that should be lagging.

Ah, that’s so much more clear now! Thank you for taking the time to explain. I’m much more confident moving forward.