I'm relatively new to graphically programming and I've been looking into ways to render larger heightened terrain. I keep seeing comments directing me to disregard things such as geometry clipmaps, in favor of tessellation.

From what I've read however, tessellation adds inner and outer triangles between a set of vertices. So from what I understand, you would lose the 1 to 1 relationship between height points and vertices. Additionally, the new vertices would be interpolated and therefore somewhat similar looking between points of similar height.

Is this the case or is there something I'm missing. Is tessellation exclusively the way to go or can it (/should it) be combined with other techniques?


1 Answer 1


When rendering terrain, for efficiency you usually want to reduce the level of detail of geometry in areas far from the camera. As the camera moves around, you would adjust the level of detail to keep the area near the camera at high detail.

Geomipmapping, geometry clipmaps and suchlike are ways of managing this on the CPU. Although the GPU always does the actual rendering, you have to do a certain amount of CPU work each frame to decide which terrain chunks to draw at which LOD. You also have to take care of avoiding cracks when two adjacent chunks are drawn at different LODs. This tends to add a good deal of complexity to the algorithm, as well as using more memory and performance to deal with the extra crack-filling geometry.

The potential advantage of tessellation is that you would move this work onto the GPU. You could code a hull shader that would choose the appropriate level of detail for each patch and automatically generate the geometry for it. You would not need to store any terrain geometry, just the heightfield in the form of a texture to be sampled by the domain shader. On the CPU, you would simply render a single quad-patch (four vertices) for each terrain chunk—potentially including the whole terrain in one draw call. Because the tessellation hardware allows you to independently set tess factors for each edge of a patch as well as the interior, anti-cracking is easy to accomplish.

There's no reason why you would need to lose the 1-to-1 relationship between height samples and vertices. If each chunk is 64×64 height samples, and you draw it using a single patch with tessellation factor 64 (the maximum) then it will have one tessellated vertex per height sample. As the camera gets farther away you would reduce the tess factor, and then the resulting geometry will interpolate between height samples and/or not use all of them, but that's what would happen in any other LOD scheme as well. You could also increase tessellation beyond the number of height samples (e.g. a patch with 16×16 height samples, but tess factor 64). This could be useful for extra smoothing, e.g. if you implemented bicubic interpolation for the heightfield, or adding extra detail, such as from a detail map or noise function, or procedural destruction (as seen in some games where explosions will leave craters in the terrain).

As for whether tessellation is "exclusively" the way to go, that is difficult to answer. It's a tradeoff: it will reduce CPU overhead in managing and submitting terrain draw calls, but it will increase GPU usage, which you may or may not want to do. Also, tessellation is only available on DX11-class GPUs—which is all the new desktop/laptop GPUs being sold for the past several years, as well as the new consoles, but not mobile GPUs (yet) or the last-generation consoles. So it's wise to consider the minimum hardware requirements for your project before going all-in on tessellation.

  • \$\begingroup\$ +1, is 64x64 a recommended chunk size? what are the factors that could help decide the actual chunk size? \$\endgroup\$
    – concept3d
    Feb 9, 2014 at 8:33
  • 1
    \$\begingroup\$ @concept3d When using tessellation, the maximum tess factor is 64, so one patch can't be bigger than 64×64 vertices at full detail. So at least when drawing the terrain, it has to be split into 64×64 patches. For loading/streaming or other things I think you might like to have larger chunks. It depends on the terrain resolution, how much memory you want to consume, how much disk bandwidth you have for streaming, etc. \$\endgroup\$ Feb 9, 2014 at 22:22

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .