Professional Weight Painting for Game Models

Imagine you're developing an RPG: the character in T-pose looks perfect, but bending the elbow at 90° collapses the armpit geometry, the knee pinches, and the neck tears. This is a classic problem of inaccurate vertex weight painting, where each vertex doesn't receive correct bone influences. Our team — with 10+ years in gamedev — solves such tasks: we provide skinning and weight painting for models of any complexity, from simple NPCs to creatures with non-standard anatomy. Below we break down why automatic weights aren't a panacea, which areas require manual correction, and how our process ensures correct deformations in animation.

Why Automatic Weights Are Just the Start

Tools like Automatic Weights in Blender (using the Heat Diffusion algorithm) produce acceptable results for 60–70% of the mesh. The rest — joint areas, clothing edges, complex intersections — need manual editing. Maya's Smooth Bind with Closest in Hierarchy works better on anatomically correct meshes, but creatures and mechanical models show the same errors.

First step after autoweights: test in pose mode. Bend the elbow 90°, the knee, raise the shoulder, rotate the neck. Document all issues before manual editing — it's faster than redoing after accumulation.

Critical Areas: Where Weights Always Break

Shoulder. The transition between Shoulder and Spine/Chest — the armpit area. Autoweights spread influence across 3–4 bones, creating a collapse when the arm is raised. Solution: vertices on the inner side of the arm go only to UpperArm; torso vertices only to Chest; transition along a clear line.

Wrist and pronation. Wrist rotation is driven by the Forearm bone. Without a Twist bone, the forearm twists like a rope. With a Twist bone: half of the forearm weight is redistributed to the Twist with a gradient from 0 (at elbow) to 0.5 (middle) to 0 (at wrist). This gives smooth unwinding.

Knee. The mistake is too large a blending zone between UpperLeg and LowerLeg. At 90° bend, a pinch appears — the front part of the knee loses volume. Solution: strict division along the joint axis. At the joint itself, equal weight (0.5/0.5) for 2–3 edge loops.

Neck. The opposite problem — too rigid division. Vertices at the back of the neck should smoothly transition from Spine2 to Neck with a contribution from Chest, otherwise a gap appears when tilting the head back.

How to Avoid a Pinched Knee

A pinched knee occurs due to excessive mixing of UpperLeg and LowerLeg weights. Solution: in Weight Paint mode, assign a weight of 0.5 to both bones on 2–3 edge loops around the joint, and strictly 1.0 for the respective bone above and below. This ensures a sharp transition, preserving volume when bent.

Why Clothing Requires Separate Weighting

If clothing is a separate mesh, it should copy the body's skinning but account for fabric. Use a Data Transfer Modifier to transfer weights, then manually adjust edges where the clothing geometry diverges from the body. Otherwise, the fabric will snag or deform unnaturally during movement.

Tools and Techniques for Weight Paint

In Blender, Weight Paint mode is primary. Important nuances:

• Normalize All before finalization: sum of weights per vertex = 1.0.
• Limit Total with Max Influences = 4: standard for Unity GPU skinning. On mobile, reduce to 2–3.
• Smooth brush with Strength 0.3–0.5 for smoothing influence zone edges, not on joints.
• Vertex Group Lock — lock completed groups against accidental changes.

In Maya, Component Editor provides numerical access to selected vertex weights — indispensable for fine-tuned editing.

Table of Common Problems

What's Included in the Work

• Inspection and refinement of the rig (twist bones, IK)
• Accurate weighting of all vertices
• Testing in pose mode and engine (Unity, Unreal)
• Adjustments to performance requirements (Max Influences)
• Final files in required format (FBX, blend, ma)
• Result guarantee — free fixes if deformations don't meet expectations

How We Do It: Work Stages

1. Mesh and rig analysis — checking topology, polygon count, bone structure.
2. Rig creation or adaptation — adding twist bones, IK, animation-ready setup.
3. Autoweight assignment — initial skinning with chosen tool.
4. Manual weighting — correcting critical zones (shoulders, knees, wrists, neck, clothing).
5. Testing in pose mode — all movements, extreme poses, artifact fixes.
6. Export and integration — export with set influence count, engine check.

Timeline and Pricing

Pricing is calculated individually based on mesh complexity, number of separate objects, and platform requirements. This saves your budget by eliminating rework during animation. Contact us for an accurate assessment.

Guarantee and Experience

We've been in gamedev for over 10 years, having completed skinning for 50+ characters in projects ranging from indie to AAA. We use professional tools and proven methods. Reach out to us for quality skinning — your model will animate correctly without artifacts.

Order accurate weight painting — get a model that animates correctly without artifacts. Need a consultation? Contact us to discuss your project.

Why Does Game Character Rigging Often Break the Animation Pipeline?

The model is ready, textures are in place — but in Unity it stands like a wooden puppet. Bones are set arbitrarily and don't map to Humanoid Avatar. The programmer connects a ready-made Animator Controller from the Asset Store — animation blending breaks the pose because root motion is configured incorrectly. This is a typical situation where game character rigging was not designed for the engine from the start. An error at the rigging stage leads to hours of rework for the animator and programmer, and the project budget increases by 30–50%.

Rigging is not just "adding bones." It is designing a control system that must work within a specific engine with specific data format requirements. We guarantee that after our work, the character is ready for animation without rework: all bones map to Humanoid, weights are distributed without artifacts, and the Animator Controller is designed for the specific gameplay. Our team has been doing game character rigging for over 7 years and has completed work for 150+ characters in projects of various genres — from mobile RPGs to PC action games. Order rigging from us — and get a skeleton ready for animation from the first import.

What Are the Skeleton Requirements for Humanoid Avatar?

Unity works with two rig types: Generic and Humanoid. The choice affects the entire animation pipeline.

Generic rig — arbitrary bone hierarchy. Animations are tied to a specific model, retargeting is impossible. Suitable for non-character animation (vehicles, doors, creatures with non-standard anatomy).

Humanoid rig — Unity maps bones to a standard schema of 17 mandatory bones (spine, head, arms, legs) and up to 32 optional ones. After that, any Humanoid animation can be applied to any Humanoid character. This is the foundation for retargeting and Animator Controller with Blend Tree. Humanoid rig speeds up animation creation by 2–3 times compared to Generic, since ready-made animations from the Asset Store work without adaptation.

Errors that break Avatar mapping:

• Incorrect bone orientation. Unity expects the X-axis to point along the bone toward the child bone. If the arm points along Z or -Y — the Avatar will be generated with a distorted T-pose.
• Extra intermediate bones in the spine chain. If there is an unmapped intermediate bone between Spine and Chest — it gets lost during retargeting, spine animation looks stiff.
• Roll bones (twist bones) — bones for distributing forearm and thigh twist. In Humanoid, they must be added as additional (non-mandatory) bones with correct weight painting. Without twist bones, the forearm twists unnaturally when the hand rotates.

T-pose vs A-pose

Unity recommends T-pose as the bind pose. A-pose (arms down at ~45°) technically works, but retargeted animations will have small shoulder joint errors — up to 5° deviation. For characters with armor or broad shoulders, A-pose is sometimes preferable: less mesh stretching during retargeting. The decision is made at the rigging stage, redoing it later is expensive.

Avatar Mask

Avatar Mask is a tool for partial application of animations. For example: the lower body plays a run animation, the upper body plays a shoot animation. Without Avatar Mask, these states conflict. The correct Animator Controller structure for a shooter:

Base Layer (Full Body weight: 1.0)
  └── Locomotion Blend Tree (idle / walk / run / sprint)

Upper Body Layer (Avatar Mask: upper body, weight: 1.0)
  ├── Idle_upper
  ├── Shoot
  ├── Reload
  └── Aim_offset (2D Blend Tree by pitch/yaw)

Additive Layer (Avatar Mask: spine, weight: by parameter)
  └── Lean_left / Lean_right

Example of Avatar Mask setup: in Unity Inspector, select Animator Controller, open Layers -> Add Layer -> choose Avatar Mask. For Upper Body, create a mask enabling shoulder girdle, arms, and head bones. For Additive, only spine. Uncheck the legs.

Additive layer for leaning is a typical optimization: instead of 8 separate animations (run_left, run_right, walk_left...), one additive lean is applied on top of any state. Time savings on clip creation — up to 40%. For complex projects, this reduces the animation budget by 15–20%.

How to Set Up a Blend Tree for Locomotion?

Blend Tree is a system for blending animations based on one or two parameters. For character locomotion, the standard is 2D Freeform Directional with parameters velocityX and velocityZ.

Minimum set of clips for basic locomotion:

Freeform Directional interpolates between clips by angle and magnitude of the velocity vector. At velocity (0.35, 0.35), Walk Forward and Strafe Right are mixed with weights calculated by distance to each point in 2D space.

Root Motion vs. In-Place Animations

Root Motion — character movement is driven by the root bone displacement in the animation clip. The animator "bakes" movement speed into the animation. Unity reads this displacement and moves the character Transform. Pros: animation and movement are always synchronized (steps match displacement). Cons: harder to control speed via code, requires correct setup in Animator (Apply Root Motion: true).

In-Place — the pelvis bone stays in place, movement is controlled by code (CharacterController or Rigidbody). Easier to integrate with physics systems, but risk of step-to-speed desynchronization (slipping feet).

In-Place animations with Foot IK via the Animation Rigging package (Unity) are better for games with complex terrain, as they ensure precise foot placement on uneven surfaces, saving 15–20% of time on manual animation correction.

Why Do Skinning Problems Occur and How to Solve Them?

Skinning (binding mesh to bones via weights) is the most labor-intensive stage of rigging organic characters.

Tools: Maya (Weight Paint tool + Component Editor), Blender (Weight Paint mode + Vertex Group Editor), 3ds Max (Skin modifier + Weight Table).

Problem areas and solutions:

Proper skinning from the start saves up to 60% of the animation rework budget. — and we add weight math and blendshapes to make movements look natural. To avoid similar issues on your project, get a rigging consultation right now.

Combat Animations and States

A combat animation system is not just a set of clips. It is a state graph with transition conditions and interrupt priorities.

Typical mistake: transition from Idle → Attack with Has Exit Time: true and Exit Time: 0.9. This means the attack will start only when idle has played 90% (0.5 seconds). The player presses the attack button and waits half a second. Solution: Has Exit Time: false, transition by trigger, Interruption Source: Current State with priority.

Combat states structure:

Any State → Hit Reaction (trigger: onHit, interrupts current)
Any State → Death (trigger: onDeath, interrupts all)

Attack Layer:
  Idle → Attack1 (trigger: attack)
  Attack1 → Attack2 (trigger: attack, exit time: 0.6)
  Attack2 → Attack3 (trigger: attack, exit time: 0.6)
  Attack1/2/3 → Idle (no trigger, exit time: 1.0)

Combo-window opens at ~40% of animation length and closes at ~80%. This creates a sense of responsiveness without breaking the animation.

When Should You Use Spine 2D?

Spine is the standard for 2D animation in mobile RPGs, idle games, action-platformers. The character mesh is split into parts attached to a 2D skeleton. Animation — bone transformations, mesh deformation via weighted vertices.

Advantages over frame-by-frame:

• Animation file size is kilobytes instead of megabytes (spritesheets). Typical savings — 80–90% of build size.
• Retargeting: same attack animations work on different characters with identical skeleton structure.
• Animation blending and IK — same concepts as in 3D.

Integration in Unity: official Spine Runtime for Unity. The SkeletonAnimation component controls playback, SkeletonMecanim allows using Animator Controller on top of the Spine skeleton. For programmatic animation — direct control via API: skeletonAnimation.AnimationState.SetAnimation(0, "walk", true).

DOTween is often used in conjunction with Spine to control non-skeletal animations of UI elements attached to the character (health bar, damage numbers) — not for the skeleton itself, but for synchronizing UI with game events.

How We Work

1. Analysis — examine gameplay, determine list of animations, rig type (Humanoid/Generic), IK and layer requirements.
2. Skeleton design — create bone hierarchy in Maya/Blender considering Humanoid Avatar, add twist bones, corrective shapes.
3. Skinning — manual weight refinement in problem areas, verification via Unity Avatar Tester.
4. Animation creation — locomotion, combat, reactions, cinematics. Set up Animator Controller with Blend Tree and Avatar Mask.
5. Testing and optimization — check in target scene, profile draw calls, eliminate stutter, configure asset streaming.
6. Delivery — hand over project with documentation and support.

What You Get

• Skeletal model with correct Humanoid Avatar (or Generic) — FBX/glTF file.
• Set of animation clips — FBX with AnimationClips.
• Animator Controller with configured layers, Blend Tree, and transitions.
• Documentation on controller structure and code usage.
• Support during integration — we answer questions, fix inaccuracies.

Estimated timeline: 5 to 15 working days depending on complexity (number of animations, rig type, Spine 2D presence). Cost is calculated individually after scope assessment — contact us for consultation and a rough estimate. Order game character rigging — and your characters will come to life without animation bugs.