The two common measurements of a game model’s “cost” are polygon count and vertex count. Polygon is interchangeable with triangle in these measurements, as GPUs only see vertices and triangles, not 4+ sided polygons. Depending on the use, a game model may stretch anywhere from 2 triangles for a billboard, to 40,000+ triangles for a complex character.

## Polygons vs. Triangles

When a game artist talks about the poly count of a model, they really mean the triangle count. Games use triangles not polygons because most modern graphic hardware is built to accelerate the rendering of triangles.

The polygon count that’s reported in a modeling app is always misleading, because the triangle count is higher. Polygons are always converted into triangles when loaded in a game engine. If you’re using a polygon counting tool in your modeling app, it’s best to switch it to count triangles so you’re using the same counting method everyone else is using.

When a model is exported to a game engine, the polygons are all converted into triangles automatically. However different tools will create different triangle layouts within those polygons. A quad can end up either as a “ridge” or as a “valley” depending on how it’s triangulated. Artists need to carefully examine a new model in the game engine to see if the triangle edges are turned the way they wish. If not, specific polygons can then be triangulated manually.

When using a NormalMap some tools may require an artist to convert the model into all triangles before baking. If the triangles are flipped differently when the model is exported than they were when the normal map was baked, this can cause the final normal-mapped lighting to zig-zag across the model. Triangulating before baking will solve this.

Polygons have a useful purpose for game artists. A model made of mostly four-sided polygons (quads) will work well with edge-loop selection & transform methods that speed up modeling (see Topology). This makes it easier to judge the “flow” of a model, and to weight a skinned model to its bones. Artists try to preserve these polygons in their models as long as possible.

## Triangle Count vs. Vertex Count

Vertex count is ultimately more important for performance and memory than the triangle count, but for historical reasons artists more commonly use triangle count as a performance measurement.

On the most basic level, the triangle count and the vertex count can be similar if the all the triangles are connected to one another. 1 triangle uses 3 vertices, 2 triangles use 4 vertices, 3 triangles use 5 vertices, 4 triangles use 6 vertices and so on.

However, seams in UVs, changes to shading/smoothing groups, and material changes from triangle to triangle… are all treated as a physical break in the model’s surface, when the model is rendered by the game. The vertices must be duplicated at these breaks, so the model can be sent in renderable chunks to the graphics card.

Overuse of smoothing groups, over-splittage of UVs, too many material assignments (and too much misalignment of these three properties), all of these lead to a much larger vertex count. This can stress the transform stages for the model, slowing performance. It can also increase the memory cost for the mesh because there are more vertices to send and store.

## Tools for Counting Vertices

Because vertices are duplicated for in-game rendering, most 3D modeling tools don’t give you the correct vertex count. They only count mesh vertices.

You can use the UV vertex count as a rough guide. However, artists shouldn’t worry too much about calculating exact vertex counts, simply go for common sense and don’t be wasteful.