Discussion and diagrams to help you understand how nonlinear depth mapping works in different situations, intuitively and visually.

*This post was originally published on the Developer Zone.*

Depth precision is a pain that every graphics programmer has to struggle with sooner or later. Many articles and papers have been written on the topic, and a variety of different depth buffer formats and setups are found across different games, engines, and devices.

Because of the way it interacts with perspective projection, GPU hardware depth mapping is a little recondite and studying the equations may not make things immediately obvious. To get an intuition for how it works, it’s helpful to draw some pictures.

This post has three main parts. In the first part, I try to provide some motivation for nonlinear depth mapping. Second, I present some diagrams to help understand how nonlinear depth mapping works in different situations, intuitively and visually. The third part is a discussion and reproduction of the main results of Tightening the Precision of Perspective Rendering by Paul Upchurch and Mathieu Desbrun (2012), concerning the effects of floating-point roundoff error on depth precision.

## Why 1/z

GPU hardware depth buffers don’t typically store a linear representation of the distance an object lies in front of the camera, contrary to what you might naïvely expect when encountering this for the first time. Instead, the depth buffer stores a value proportional to the reciprocal of world-space depth. I want to briefly motivate this convention.

In this post , I use *d* to represent the value stored in the depth buffer (in [0, 1]), and *z* to represent world-space depth, that is, the distance along the view axis, in world units such as meters. In general, the relationship between them is of the following form:

In this formula, *a* and *b* are constants related to the near and far plane settings. In other words, *d* is always some linear remapping of

On the face of it, you can imagine taking *d* to be any function of *z* that you like. So why this particular choice? There are two main reasons.

First,

The real power in this approach, of course, is that the projection matrix can be multiplied with other matrices, allowing you to combine many transformation stages together in one.

The second reason is that *d* across a triangle while rasterizing, and things like hierarchical Z-buffers, early Z-culling, and depth buffer compression are all a lot easier to do.

## Graphing depth maps

Equations are hard; here are some pictures!

The way to read these graphs is left to right, then down to the bottom. Start with *d*, plotted on the left axis. Because *d* can be an arbitrary linear remapping of

Trace the tick marks horizontally to where they hit the

Figure 1 shows the “standard”, vanilla depth mapping used in D3D and similar APIs. You can immediately see how the

It’s also easy to see why the near plane has such a profound effect on depth precision. Pulling in the near plane will make the *d* range skyrocket up toward the asymptote of the

Similarly, it’s easy to see in this context why pushing the far plane all the way out to infinity doesn’t have that much effect. It just means extending the *d* range slightly down to

What about floating-point depth? The following graph adds tick marks corresponding to a simulated float format with three exponent bits and three mantissa bits:

There are now 40 distinct values in [0, 1]—quite a bit more than the 16 values previously, but most of them are uselessly bunched up at the near plane where you didn’t really need more precision.

A now-widely-known trick is to reverse the depth range, mapping the near plane to *d=1* and the far plane to *d=0*:

Much better! Now the quasi-logarithmic distribution of floating-point somewhat cancels the

The reversed-Z trick has probably been independently reinvented several times, but goes at least as far back as a SIGGRAPH ’99 paper: Optimal depth buffer for low-cost graphics hardware by Eugene Lapidous and Guofang Jiao (no open-access link available, unfortunately). It was more recently re-popularized in posts by Matt Pettineo and Brano Kemen, and by Emil Persson’s Creating Vast Game Worlds SIGGRAPH 2012 talk.

All the previous diagrams assumed [0, 1] as the post-projection depth range, which is the D3D convention. What about OpenGL?

OpenGL by default assumes a [-1, 1] post-projection depth range. This doesn’t make a difference for integer formats, but with floating-point, all the precision is stuck uselessly in the middle. (The value gets mapped into [0, 1] for storage in the depth buffer later, but that doesn’t help, since the initial mapping to [-1, 1] has already destroyed all the precision in the far half of the range.) And by symmetry, the reversed-Z trick does not do anything here.

Fortunately, in desktop OpenGL you can fix this with the widely-supported ARB_clip_control extension (now also core in OpenGL 4.5 as glClipControl). Unfortunately, in GL ES, you’re out of luck.

## Effects of roundoff error

The

As mentioned earlier, Upchurch and Desbrun studied this and came up with two main recommendations to minimize roundoff error:

- Use an infinite far plane.
- Keep the projection matrix separate from other matrices, and apply it in a separate operation in the vertex shader, rather than composing it into the view matrix.

Upchurch and Desbrun came up with these recommendations through an analytical technique, based on treating roundoff errors as small random perturbations introduced at each arithmetic operation, and keeping track of them to first order through the transformation process. I decided to check the results using direct simulation.

Here’s my source code—Python 3.4 with numpy. It works by generating a sequence of random points, ordered by depth, spaced either linearly or logarithmically between the near and far planes. Then it passes the points through view and projection matrices and the perspective divide, using 32-bit float precision throughout, and optionally quantizes the final result to 24-bit integer.

Finally, it runs through the sequence and counts how many times two adjacent points (which originally had distinct depths) have either become indistinguishable because they mapped to the same depth value, or have actually swapped order. In other words, it measures the rate at which depth comparison errors occur—which corresponds to issues like Z-fighting—under different scenarios.

Here are the results obtained for near = 0.1, far = 10K, with 10K linearly spaced depths. (I tried logarithmic depth spacing and other near/far ratios as well, and while the detailed numbers varied, the general trends in the results were the same.)

In the table, “indist” means indistinguishable (two nearby depths mapped to the same final depth buffer value), and “swap” means that two nearby depths swapped order.

**Precomposed view ****Projection matrix****Separate view and****projection matrices****float32****int24** **float32****int24****Unaltered Z values(control test)**0% indist

0% swap0% indist

0% swap0% indist

0% swap0% indist

0% swap

**Standard projection**45% indist

18% swap45% indist

18% swap77% indist

0% swap77% indist

0% swap

**Infinite far plane**45% indist

18% swap45% indist

18% swap76% indist

0% swap76% indist

0% swap

**Reversed Z**0% indist

0% swap76% indist

0% swap0% indist

0% swap76% indist

0% swap

**Infinite + reversed-Z**0% indist

0% swap76% indist

0% swap0% indist

0% swap76% indist

0% swap

**GL-style standard**56% indist

12% swap56% indist

12% swap77% indist

0% swap77% indist

0% swap

**GL-style infinite**59% indist

10% swap59% indist

10% swap77% indist

0% swap77% indist

0% swap

Apologies for not graphing these, but there are too many dimensions to make it easy to graph! In any case, looking at the numbers, a few general results are clear.

- There is no difference between float and integer depth buffers in most setups. The arithmetic error swamps the quantization error. In part this is because float32 and int24 have almost the same-sized ulp in [0.5, 1] (because float32 has a 23-bit mantissa), so there actually is almost no additional quantization error over the vast majority of the depth range.
- In many cases, separating the view and projection matrices (following Upchurch and Desbrun’s recommendation) does make some improvement. While it doesn’t lower the overall error rate, it does seem to turn swaps into indistinguishables, which is a step in the right direction.
- An infinite far plane makes only a miniscule difference in error rates. Upchurch and Desbrun predicted a 25% reduction in absolute
*numerical*error, but it doesn’t seem to translate into a reduced rate of*comparison*errors.

The above points are practically irrelevant, though, because the real result that matters here is: the reversed-Z mapping is basically magic. Check it out:

- Reversed-Z with a float depth buffer gives a zero error rate in this test. Now, of course you can make it generate some errors if you keep tightening the spacing of the input depth values. Still, reversed-Z with float is ridiculously more accurate than any of the other options.
- Reversed-Z with an integer depth buffer is as good as any of the other integer options.
- Reversed-Z erases the distinctions between precomposed versus separate view/projection matrices, and finite versus infinite far planes. In other words, with reversed-Z you can compose your projection matrix with other matrices, and you can use whichever far plane you like, without affecting precision at all.

I think the conclusion here is clear. In any perspective projection situation, just use a floating-point depth buffer with reversed-Z! And if you can’t use a floating-point depth buffer, you should still use reversed-Z. It isn’t a panacea for all precision woes, especially if you’re building an open-world environment that contains extreme depth ranges. But it’s a great start.

Source:: NVIDIA