mocap retargeting onto stylized rigs: when does the data just stop being useful

361 views 10 replies

Been working on a project with pretty stylized characters. Not full cartoon, but definitely not realistic bipeds. Long torsos, short legs, slightly elongated arms. When I got mocap data back from a Rokoko session (actor in standard T-pose, normal human proportions), retargeting it in MotionBuilder went about as well as you'd expect.

The structural mapping isn't really the problem. HIK handles basic bone mapping fine even when proportions are off. The problem is what happens to the feel of the motion after retargeting. The actor's weight shifts, momentum, and center-of-gravity read completely differently on a character with a mismatched CoM. A heavy step forward that looks grounded on the actor ends up looking floaty or rushed on a short-legged character. Contact timing is wrong. The whole physical logic of the performance gets scrambled.

What I've tried so far:

  • MotionBuilder's HIK with proportional retargeting enabled — helps somewhat, still needs heavy manual cleanup afterward
  • Retargeting in Unreal's IK Rig system — more control over the mapping, but iteration is slow and fiddly
  • Using mocap as reference only and hand-keying on top — honestly sometimes this is just the right answer and I hate that

Quadruped or creature rigs are even messier. At some point it stops feeling like you're using motion data and starts feeling like you're fighting it.

What are people here actually doing for non-standard rigs? Do you adjust the capture process — special actor performances, floor marks for proportion matching, constraints on the suit? Do you retarget and then layer corrections on top in a second pass? Or have you just accepted that mocap for stylized characters is really more "motion reference" than "motion data" and planned your pipeline accordingly?

Replying to CyberCrow: When stylization is extreme enough, it's sometimes worth treating the mocap as r...

This is where I landed after fighting the retargeter for too long. What finally clicked was realizing mocap carries timing and weight information far better than it carries literal joint angles for stylized proportions. Once I started treating it as motion reference rather than motion data, blocking in broad timing from a reference layer and animating on top, quality improved immediately. You also get faster polish passes because you're not untangling retargeting artifacts on top of everything else. On stylized characters especially, that cleanup time adds up.

Replying to RiftPike: something that doesn't come up enough in these threads: the quality of your reta...

Completely agree on the reference skeleton quality point. I was using a HIK biped I'd set up years ago and never thought to revisit it, and my retargeting results were consistently mediocre in ways I kept blaming on the mocap data itself. Rebuilt the reference skeleton from scratch using a properly proportioned capture reference, and the difference was immediate. Noticeably less foot sliding, cleaner shoulder rotation, spine movement that actually read as intentional rather than jittery.

It's the kind of thing you assume the software handles transparently, but it really doesn't. Garbage in, garbage out, just one step earlier in the pipeline than you'd expect.

Replying to ZenithMist: tbh i think the proportions problem gets overstated a bit. the real question is ...

I'd push back on the proportions-get-overstated framing. The issue isn't purely visual. The rotation values themselves can become anatomically implausible when applied to a skeleton with significantly different limb ratios. Elbows hyperextending, shoulders riding up into the neck, hips rotating past any reasonable range. That's not a visual oddity, that's contact errors and IK failures that need correction passes regardless of what you were trying to extract from the data.

The rotations are kind of correct, but they're correct relative to the capture skeleton's geometry and constraints. On a stylized rig where the same joints have different physical limits baked in, that breaks down fast. Past a certain proportion delta you're really just keeping the timing data and reconstructing the poses anyway.

Replying to EchoDusk: Completely agree. I spent the better part of a week trying to get a Rokoko take ...

The reach settings in MotionBuilder's HIK solver are worth tuning alongside bone length compensation. I had a very similar issue with elongated leg proportions and dropping the full-body reach for the legs by around 20% made a noticeable difference. The default is calibrated for realistic skeletons and tends to over-extend on stylized rigs.

Also worth auditing your reference T-pose. If the proportions in your MB reference pose don't match your game rig reasonably closely, the compensation math is working from a bad baseline before you even touch reach settings. Spent longer than I'd like to admit figuring that one out.

Replying to OnyxFern: I'd push back on this a bit. Proportions matter more than the "it depends on wha...

Completely agree. I spent the better part of a week trying to get a Rokoko take onto a character with roughly 1.5x normal leg length. MotionBuilder's retargeter has bone length compensation settings, but even maxed out you get this floating hover on flat ground because the stride length in the capture was calibrated for a much shorter hip height. Ended up manually scaling root motion and redoing foot contact corrections by hand. At that point you've spent more time cleaning the retargeted data than you would have keyframing the broad strokes and using mocap only for fine detail on a properly proportioned rig.

It compounds too. It's not just the legs either. Spine and shoulder timing reads wrong because the pelvis offset from the ground is incorrect relative to everything else hanging off it.

tbh i think the proportions problem gets overstated a bit. the real question is what you actually need from the mocap. if the answer is naturalism, subtle weight shifts, micro-adjustments in the spine, the way momentum carries through, then yeah, a rig with completely different proportions is gonna fight that constantly. but if you just need rough timing and blocking, a busted retarget is totally fine because you're polishing everything by hand anyway.

on my last project i gave up trying to fix the retarget and just used it as a ghost layer for timing reference while re-keying on top by hand. probably took longer overall than animating from scratch. but it completely killed the blank-page problem. having something moving on screen, even badly, makes it way easier to see what the performance is actually doing and where you want to go.

Replying to ZenithMist: tbh i think the proportions problem gets overstated a bit. the real question is ...

I'd push back on this a bit. Proportions matter more than the "it depends on what you need" framing suggests. Rotation data from mocap encodes joint angles that make physical sense on the skeleton they were captured on. When you retarget to a character with a torso that's 40% longer, those same rotations don't produce equivalent body language, not because the retargeting is broken, but because the visual weight and leverage are completely different. A subtle spine lean that reads as casual confidence on a realistic biped can look like a full-body crunch on an elongated character.

The question isn't just whether you need naturalism. Even stylized animation benefits from mocap for timing and weight reference, but extreme proportion mismatches can scramble both of those things. I've had takes that looked perfectly fine in isolation but felt completely wrong on the actual character in context, and the fix was always dealing with the proportions, not cleaning the mocap data further.

something that doesn't come up enough in these threads: the quality of your retargeting skeleton in the mocap software matters almost as much as the algorithm itself. if your HIK skeleton in MotionBuilder or your control rig in Blender doesn't closely match the proportions of the actual capture performer, you're correcting for two proportion mismatches at once before the stylized rig even enters the picture.

i've had noticeably cleaner results building a proper HIK setup matched to the performer, retargeting to that intermediate skeleton first, and then going to the stylized rig, rather than performer → generic HIK → stylized in one shot. extra step, but the intermediate data is so much cleaner that it saves time on correction passes downstream.

Replying to ChronoReed: Completely agree on the reference skeleton quality point. I was using a HIK bipe...

Rebuilding from scratch is the right call, and the thing that most consistently kills HIK retargeting quality is non-zero rotations baked into the bind pose of the reference skeleton. If any bone in your T-pose reference has rotation values in the transform, the solver has to compensate on every frame, and it compounds badly in the spine and shoulders where small angular errors stack up. Every bone in the reference should be rotation-zero in T-pose, with orientation encoded purely in the joint orientation attribute, not the transform rotation.

Had an old HIK biped with accumulated 2–3 degree offsets scattered through the mid-spine joints that I'd never noticed. Zeroing everything and resetting the character definition improved results immediately in ways I hadn't been able to get out of the solver settings alone.

When stylization is extreme enough, it's sometimes worth treating the mocap as reference only and hand-keying from it. Play the take back on a second viewport or a reference layer and key the broad strokes, timing, weight shifts, major contact points, while ignoring the rotation data entirely. You get the performance quality without fighting a retargeter that's trying to make anatomically implausible things work on proportions it wasn't built for.

Slower than a clean retarget, obviously. But if you're already spending more than a few hours on per-bone corrective animation to fix what the retargeter mangled, it's sometimes faster to just key it from scratch with the mocap as a guide.

Moonjump
Forum Search Shader Sandbox
Sign In Register