3D Modeling Services for Games

3D Modeling for Games

Consider this scenario: an artist submits a character with 120,000 polygons, arguing "it looks better that way." It might work on PC, but on mobile, a scene with just ten of these characters will drop frame rates to unplayable levels. The problem isn't the artist—it's the lack of a clearly defined polygon budget and understanding of why high-poly and low-poly models exist in the first place.

3D modeling for games isn't about "making it look nice." It's work within strict technical constraints, where every decision has direct consequences at runtime.

General Pipeline

The standard pipeline looks like this:

1. Concept / References — Before opening ZBrush, understand the silhouette, readability, and target platform.
2. High-poly sculpt — Detailed sculptural model with no polygon limits. Created in ZBrush or Blender (Sculpt Mode).
3. Low-poly retopology — Clean game mesh over high-poly, manually or semi-automatically.
4. UV unwrapping — Preparing texture coordinates.
5. Baking — Transferring detail from high-poly onto maps (normal map, AO, curvature, etc.).
6. Engine import — Importing into Unity or Unreal with LOD chain setup.

Each stage affects the next. Poor retopology will break skinning. Badly cut UVs create artifacts during baking. The stages cannot be reordered.

Polygon Budgets: Mobile vs PC vs VR

This is the aspect most often ignored at project start—and it's exactly what costs rework later.

Mobile Platforms (iOS / Android)

Mobile is the most demanding environment. Budget guidelines for characters:

For environment (single prop):

More critical than polygon count itself: draw call count and batching. A 200-triangle model with a separate material can be more expensive than a 2,000-triangle model that batches with the entire scene.

PC / Console

Budgets are looser here, but not unlimited:

• Main character in first-person shooter: 15,000 – 60,000 polygons (enemy model player sees constantly).
• Character in third-person RPG: 8,000 – 25,000.
• Vehicle in racing game: 30,000 – 80,000 (many small details, LOD is mandatory).

The key tool is LOD (Level of Detail). In Unity, this is LOD Group; in Unreal, automatic HLOD plus manual LOD levels in Static Mesh Editor. Rule: LOD0 → LOD1 should lose ~50-60% of polygons, LOD1 → LOD2 another ~50%.

VR

VR is a different story. Rendering happens for both eyes with target framerates of 90 fps (Quest) or 120 fps (PSVR2). Any frame drop is felt physically—players get dizzy.

Character budget in VR: 4,000 – 12,000 (depends on concurrent NPC count). Environment must be aggressively optimized: occluder culling, portal systems, or cluster rendering—without this, the scene won't achieve target fps.

Retopology: Why It's Artistic, Not Just Technical

Retopology is creating a clean polygon mesh over a sculpted model. Many view it as a tedious technical step that can be sped up with auto-retopology (ZRemesher in ZBrush, Instant Meshes, Auto Retopology in Maya). This is wrong.

Auto-retopology fails in three critical areas:

1. Joints — knees, elbows, wrists. These need clean edge loops perpendicular to rotation axes. Auto-retopology breaks them with chaotic diagonals, and during animation, the joint collapses ungracefully.
2. Face — Around mouth and eyes, concentric loops are required, following muscle structure. This is mandatory for correct facial animation via blend shapes / morph targets.
3. Silhouette edges — shoulders, chest, major forms. Polygons must be consciously distributed so the silhouette reads even at LOD2.

Tools for manual retopology:

• Maya — Quad Draw tool, one of the best in the industry. Draw polygons directly on the high-poly surface.
• Blender — BSurfaces addon + Shrinkwrap modifier. Less convenient than Quad Draw but workable.
• 3ds Max — Graphite Modeling Tools (Modeling tab on ribbon). Slower than Maya but familiar to Max veterans.
• ZBrush — ZRemesher with manual guide curves. Works well for organics, less for hard surface.

Mesh density should distribute unevenly: face and hands get more polygons, back and lower legs get fewer. This isn't arbitrary; it's because that's where the camera spends more time.

UV Unwrapping and Baking

UV is another stage often underestimated. A few rules:

Texel density should be consistent across the entire character. If boots have twice the texel density of the face, textures will look inconsistent. Maya has UV Toolkit with normalization; Blender has the TexTools addon.

UDIM (U-Dimension) — technology where multiple UV tiles merge into one object. This allows 4K–8K textures without single UV-space limitations. Used for high-detail characters—cinematic games, hero assets. In the pipeline, this means Substance Painter in UDIM mode with separate export per tile.

Baking — transferring high-poly detail onto maps for low-poly. Tools:

• Marmoset Toolbag — Industry standard for quality baking. Cage-based baking with fine control, convenient error visualization. Clean results first try with proper cage setup.
• xNormal — Free, battle-tested. Less convenient UI, but stable results and batch-baking support for many objects.
• Substance Painter — Built-in baker. Convenient for quick results within the texturing workflow, but less flexible than Marmoset.
• Blender — Cycles baker. Slower and requires setup, but free and integrated into the full pipeline.

Typical baked maps: Normal Map, Ambient Occlusion, Curvature, Thickness, Position, World Space Normal. Curvature and Thickness are generator masks in Substance Painter that automatically highlight convex and concave features for procedural texturing.

Hard Surface vs. Organics

These are different disciplines with different toolsets.

Hard surface (weapons, vehicles, armor, machinery):

• Sculpt in ZBrush using ZModeler brush and bevel tools.
• Alternative: direct modeling in Maya or 3ds Max with subdivision + bevel. For mechanical forms, often faster than sculpting.
• Bevels are mandatory—without them, baked normal maps create artifacts on sharp edges.

Organics (characters, creatures, vegetation):

• ZBrush is the primary tool. DynaMesh for rough volume, ZRemesher for clean subdivided mesh, detailing through standard and VDM brushes.
• For clothing: Marvelous Designer simulates fabric, then retopologized into the game pipeline.

What We Deliver

• High-poly sculpt in ZBrush / Blender based on concept or reference.
• Manual retopology respecting animation topology requirements.
• UV unwrapping with normalized texel density (optionally UDIM for hero assets).
• Baking in Marmoset Toolbag or xNormal.
• LOD chain setup for target platform.
• Asset delivery to Unity / Unreal with in-engine verification.