A modern asset pipeline: 7 reasons to optimize content

Find the previous post in this series here: A modern asset pipeline: Introduction.

The reasons to why and how to optimize content differs a lot from case to case, depending on asset complexity, platform, game engine, viewing distances etc. I will give you a brief overview of a number of reasons why optimizing content is a good idea if you want to keep your game running smoothly.

Reducing over shading

Small polygons are not utilizing the hardware efficiently. In order to get maximum performance out of the hardware the recommendations from many vendors is that triangles rendered should be at least 16 pixels in size. Sliver triangles are not recommended, because they have long edges but small contributing areas.

Here we have two triangles, and a few pixels on a screen. The pixels are organized on the hardware into 2x2 quads, and all pixel processing is done on the quads.

When shading, a pixel will be drawn if the triangles overlaps the center position of the pixel.

However, most GPUs have even wider SIMD units. In this example we would need 16 pixels to utilize the hardware most efficiently. In the case to the right the triangle only covers small portions of each unit.

Since pixel processing is done per quad, we have to disable some of the edge pixels, and output results only from the covered pixels.

This is a bigger issue with smaller triangles. You can see in the example images that the left triangle has really bad usage, but the triangle on the right have much better usage, even though it is only a bit larger.

In short, highly tesselated objects are more expensive to render. Here is a video that hihglights the difference in cost of rendering. The mesh to the left contains a large number of triangles while the object to the right contains fewer and larger polygons.

Example techniques to reduce over shading are:

Reducing data per frame

Even though you have a lot memory at disposal in today’s consoles the data transfer bandwidth limits how much you can use per frame. Realistically you cannot count on using much more than 100GB/s in a PS4 or Xbox One. Which means that if you are running a game at 60FPS the amount of data you can render to screen per frame is around 1.6GB. When this becomes the bottleneck you optimize content so that you don’t send unnecessary data to the GPU.

Example techniques to reduce data per frame are:

Reducing draw calls

One of the most common bottle necks in game development today is the number of draw calls per frame. Modern GPUs are very fast at processing vertex and polygon data, but the cost of starting a new batch is significant. Hence it’s a good idea to optimize content so that the number of draw calls per frame are reduced. Each new material and object is likely to generate a new draw call, depending on engine architecture.

Example techniques to reduce draw calls are:

Reducing animation cost

In games where you have a lot of animated objects animation cost may become a bottle neck. This is especially true if you are using procedural animations, for example physics-driven, you would prefer not to calculate things that aren’t visible from the viewing position.

Example techniques to reduce animation cost are:

Reducing vertex transformations

Assets are usually created around the origin and then placed in the world. Each frame vertices for the each asset has to be transformed into world space. Each operation is quite cheap, but when you do this a million times per frame it adds up to a significant cost. Reducing the number of vertices that are drawn every frame will decrease the cost to render.

Example techniques to reduce transformation cost are:

Reducing overdraw

Overdraw is covering a pixel multiple times, with overlaying triangles.

Most engines use a Z-pre pass to fill in the Z-buffer beforehand and reject layers behind the first layer.

However, this is ineffective on meshes with multiple layers of triangles that are really close. The reason is that the Z-pre pass uses hi-z early rejection, but it is coarse and cannot reject surfaces close to the nearest surface.

Transparent surfaces are also a huge time sink as every pixel behind the surface will have to be drawn at least twice.

Example techniques to reduce overdraw cost are:

Reducing shading cost

For example, the skin shader is typically one of the most expensive in games with characters. There are a lot traits of skin that makes it expensive to simulate in a natural way. As a character gets further away a lot of those traits would not be noticeable. Hence it’s a good idea to use a cheaper shader at a distance.

Example techniques to reduce shading cost are:

In the next post in this series we will look into some stats regarding optimization.

How much time is spent optimizing?