Setting a polygon budget

Optimization

How to arrive at a number for an asset, rather than copying one from a different project.

A polygon budget is a per-asset allowance derived from a whole-scene target. Numbers quoted without that context are close to meaningless.

How do you set a polygon budget for an asset?

Work backwards from the frame. Start from the target — platform, resolution, frame rate — and profile what that hardware renders comfortably per frame. That is the scene's geometry budget. Divide it by how many objects are typically visible, then weight by role: a hero asset takes a large share, a background prop a small one.

An illustration, with made-up inputs: a scene that can afford 2 million triangles with 200 objects in view averages 10,000 per object. Weighted by role, that might be 50,000 for the hero character and 2,000 for a crate. The arithmetic is trivial; the inputs are the work, and the first one has to come from profiling your own target rather than from a number someone quoted for theirs.

The result is a budget you can defend, and it changes if the scene composition changes.

Role-based tiers

Rather than one number, define tiers:

  • Hero. Seen close, inspected, central. The largest allowance.
  • Standard. Normal props at normal distance.
  • Background. Never approached. Cheap.
  • Instanced. Repeated many times. Cheapest per instance, because the cost multiplies.

Assign every asset a tier at planning time and the budget conversation happens once rather than per asset.

Count triangles, and watch vertices

Everything renders as triangles, so quote triangles. But the vertex count is what the vertex shader processes, and vertices duplicate at every UV seam, hard edge and material boundary — so a mesh's effective vertex count can be well above what its triangle count suggests. Two models with identical triangle counts can differ substantially in cost.

Geometry is often not the bottleneck

On modern desktop hardware, a typical scene is limited by draw calls, texture memory or overdraw long before vertex count. Optimising polygons in a draw-call-bound scene achieves nothing.

Measure first. The profiler tells you which budget is actually binding.

Where it is binding

Mobile, VR (two eyes, high frame rate), very large scenes, and anything heavily instanced. There, geometry discipline matters directly.

Generated meshes

Reconstruction density is arbitrary — an artefact of the algorithm rather than a decision. It bears no relationship to your budget and is usually far above it. The budget is the input to retopology, not something the generated mesh informs.

Last reviewed