A model that renders beautifully can still be unusable in a game. Optimisation is not about making things ugly — it is about spending your budget where players actually look.
Polygon Count Is Not the Whole Story
Modern hardware handles millions of triangles. What actually costs performance is often draw calls, material count, texture memory and overdraw — not raw geometry.
Ten objects with ten materials are frequently worse than one object with one atlas, even at higher poly count.
Where to Spend Geometry
Silhouette. Players read shapes against a background, so a rounded edge on a visible corner earns its polygons. Interior detail nobody sees does not.
Detail that does not change the silhouette usually belongs in a normal map instead.
The Practical Checklist
- Bake high-poly detail into normal maps rather than shipping the high-poly mesh
- Atlas your textures so an object uses one material rather than several
- Delete unseen faces — undersides, backs, interiors
- Use LODs so distant objects use cheaper meshes
- Right-size textures — 4K on a background prop is wasted memory
- Reuse modular pieces instead of unique geometry everywhere
Topology Still Matters
Clean quads matter for anything that deforms. For static props, triangles are fine — the engine triangulates everything anyway. Spending hours on perfect quad flow for a rock is wasted effort.
For characters, the opposite is true: bad topology fails the moment it is rigged. Our retopology guide covers the tooling.
Test in Engine Early
An asset that looks correct in Blender can break on import through scale, normals or material assignment. Import a rough version early. Finding a problem on a blockout takes minutes; finding it after texturing costs a day.
The Principle
Optimisation is budgeting, not reduction. Decide what the player will look at, spend there, and cut everywhere else without guilt.
More free tools in the 3DxDEV Library.
