Rigged 3D Models

A rigged 3D model has an internal skeleton (armature) made of bones, with the mesh vertices bound to those bones via skin weights. When a bone moves, the surrounding mesh deforms with it — this is what makes a character's arm bend or a creature's jaw open. Rigged models are the starting point for all character animation in game engines (Unity, Unreal) and DCC tools (Blender, Maya, Cinema 4D). A model without rigging is a static prop; a rigged model can be animated, retargeted with motion capture data, or controlled by a physics rig.

FBX is the industry standard for game engine pipelines. Unity and Unreal Engine both import FBX natively, preserving bones, skin weights, blend shapes (morph targets), and embedded animation clips. GLB (binary GLTF) is an alternative: Unity supports it via packages, and Unreal supports GLTF import from UE5.0+. FBX remains the safer choice because it has the most consistent bone and animation data round-tripping. For web-based engines like Three.js, Babylon.js, or PlayCanvas, GLB is preferred. When a listing includes both FBX and GLB, buy it — you get the best of both.

Before buying a rigged character: (1) Open the 3D viewer — orbit around joints (elbows, knees, shoulder, spine) to check mesh quality; poor topology here means bad deformation. (2) Read the listing for bone count and naming convention — Humanoid rigs with standard bone names (mixamo-style or UE Mannequin-compatible) are easy to retarget. (3) Check if animation clips are included — idle, walk, run, and attack cover most game needs. (4) Check the polygon count in the viewer stats — 5k–25k tris is typical for real-time characters; over 100k is usually for film/pre-rendered work. (5) Verify the license covers your use (game, film, or commercial product).

Yes, if the character uses Mixamo-compatible bone names — many Proofly creators export FBX with Mixamo bone naming (Hips, Spine, Chest, Neck, Head, LeftArm, etc.). In Unity: select the FBX → Rig → Humanoid, and Unity will auto-map the bones. Then you can drag any Mixamo animation clip onto the character. In Unreal Engine: import the FBX as a Skeletal Mesh with Create Physics Asset checked; then use the IK Retargeter to remap motion capture data. If the bone naming is non-standard, check the listing description — the creator usually documents the rig schema.

For real-time game characters: Mobile (iOS/Android) → 2k–8k triangles. PC/console NPCs → 8k–25k triangles. PC/console hero (player character, frequent close-ups) → 25k–80k triangles. Cinematic/film real-time → 80k–500k triangles (for in-engine cutscenes). High-poly source mesh (for baking normals) → no limit. A 10k-triangle character with a good normal map looks nearly as good as a 40k-triangle one. When buying, check polycount in the Proofly 3D viewer stats bar, and read whether the listing includes a low-poly version, a high-poly version, or both.

Drag the .fbx file into your Unity Assets folder. Unity will auto-import it as a Model asset. In the Inspector: (1) Go to the Rig tab → set Animation Type to Humanoid if it's a biped character, or Generic for creatures. (2) Click Configure to review the bone mapping — Unity usually auto-maps correctly for standard rigs. (3) Go to the Animation tab to see embedded animation clips — rename them, set loop settings, and extract clips if needed. (4) Create an Animator Controller and assign it to a GameObject with an Animator component. Drag your FBX into the scene or use it as a Prefab. Characters with Mixamo-style bone names configure automatically in under 2 minutes.