Animation clips address bones by name. A rig whose joints are called
Bip001 L UpperArm loads perfectly, renders perfectly, and then
stands frozen forever. Drop your .glb and know in one second,
before you upload it anywhere.
This is the same retargeting path the platform uses, running on your file.
If these are a standard rig, they belong in the canonicalizer. Open an issue with this list and every future upload of that rig animates.
Replace the placeholder URI and owner, then validate it with the CLI.
Every clip in the three.ws library is authored against one canonical
skeleton: Hips, LeftForeArm,
RightUpLeg, 52 joints in total. A track that names
LeftForeArm drives nothing on a rig that calls that joint
lowerarm_l.
Nothing errors. The GLB loads, the material renders, the mixer runs, and the character stands in its bind pose. Nobody tells you why, which is why this page exists and why it runs before you upload rather than after.
Mixamo, Avaturn, Ready Player Me, Unreal, VRM, Daz, Rigify, Biped, HumanIK, Reallusion, and MakeHuman all name the same joints differently. The canonicalizer already knows every one of those dialects, and it can rewrite your file in place.
A rig rarely fails outright. Far more often the torso and arms map and the legs do not, so the avatar glides across the floor with frozen knees. Scoring each limb group separately is the difference between "62% covered" and "your legs will not move".