3D Models for MotionBuilder

Autodesk MotionBuilder's primary import format is FBX (.fbx). FBX is native to the Autodesk ecosystem and transfers mesh geometry, skeletal rigs, skin weights, blend shapes/morphs, and animation clips with full fidelity into MotionBuilder. MotionBuilder can also import OBJ files for static geometry and BVH (.bvh) files for raw motion capture data (bone hierarchy + animation curves). For character retargeting workflows: import your character FBX, characterize the rig using HIK (Human IK), and MotionBuilder can map any mocap source (BVH, C3D, live suit data) onto it. Most Proofly rigged character models export as FBX — check the listing for rig type and bone naming convention.

HIK (Human IK) is Autodesk's full-body inverse kinematics and character retargeting system built into MotionBuilder, Maya, and 3ds Max. In MotionBuilder, you characterize a rigged FBX character by mapping each bone in the skeleton to HIK's standard bone set (Hips, Spine, Chest, Neck, Head, Shoulders, Arms, Hands, Legs, Feet). Once characterized, MotionBuilder can retarget any HIK-compatible motion source — including raw mocap (BVH/C3D), optical data, or suit streams — onto your character in real time. HIK handles proportional differences between the source and target character automatically. For best results: choose characters with Mixamo, Maya Biped, or HIK-compatible bone naming — these characterize with fewer manual bone mappings.

For smooth HIK characterization and mocap retargeting in MotionBuilder, the character skeleton should have: a pelvis/hips root bone, spine chain (3–5 bones), neck, head, clavicles, upper/lower arm, hand with at least 3 fingers (index, middle, ring), upper/lower leg, and foot with toe bones. The T-pose or A-pose bind pose is strongly preferred — MotionBuilder's HIK characterization works best when the skeleton is in a standard rest pose at frame 0. Most rigged Proofly character models use industry-standard bone naming conventions compatible with Mixamo, Maya HumanIK, or Epic Games skeleton — check each listing's description for specifics. You may need to remap a few bones in HIK's Character panel, but full re-rigging should not be necessary.

Yes — Proofly's Commercial license covers use of purchased models in professional studio pipelines, including MotionBuilder-based mocap processing for commercial game titles. The workflow is: purchase and download the FBX character from Proofly → import into MotionBuilder → characterize with HIK → retarget your studio's mocap data → export the resulting animations to FBX → import into your game engine (Unity, Unreal, or CryEngine). The Commercial license covers including the model and its driven animations in a shipped commercial product. For projects where the model itself is part of a sold product (e.g., a commercial animation pack), the Extended license applies — check the listing for license tier.

MotionBuilder is an animation tool, not a real-time engine, so it tolerates higher polygon counts for preview and animation work. However, the character mesh you animate in MotionBuilder will eventually be used in a real-time engine, so stick to the target engine's LOD0 budget. For most game pipelines: humanoid characters: 10,000–30,000 triangles; creature characters: 8,000–25,000 triangles; hero/hero-close-up characters (film/cinematic): up to 80,000–150,000 triangles. MotionBuilder's own viewport can handle several million triangles before performance degrades — you can preview high-poly cinematic models directly in MotionBuilder while animating, then export decimated versions for the real-time engine.