Introduction
After our coverage of ray tracing a little while back, let’s continue our overview of the rendering techniques that could replace, or at the very least, complement triangle rasterization as we know it today.
As those who read our previous article already know, we aren’t really convinced of the viability of ray tracing in real time (Ed.: this would seem to be backed up by Intel's recent demonstration of Larrabee ray tracing Enemy Territory at mediocre frame rates). That opinion would also seem to be held by most developers of video games, including one of the celebrities of the gaming world, John Carmack. Here’s what he told our colleagues at PC Perspective:
“I think that ray tracing in the classical sense, of analytically intersecting rays with conventionally defined geometry, whether they be triangle meshes or higher order primitives, I’m not really bullish on that taking over for primary rendering tasks, which is essentially what Intel is pushing. There are large advantages to rasterization from a performance standpoint and many of the things that they argue as far as using efficient culling technologies to be able to avoid referencing a lot of geometry, those are really bogus arguments because you could do similar things with occlusion queries and conditional renders with rasterization. Head to head rasterization is just a vastly more efficient use of whatever transistors you have available.”
If John Carmack doesn’t seem all that excited about ray tracing, it’s not because he’s unusually conservative and wants to see triangle rasterization remain the unchallenged rendering technique. As reported here a year ago, John Carmack has his own idea of the future of real-time rendering, and it involves voxel ray casting. Since then, we’ve seen Jon Olick’s presentation at SIGGRAPH, and many details have been leaked. So it’s time to take a closer look at what id Software has in store for us.
