Can I get back to you later about that poly?
Our man Dissonance wrote up a nice explanation of the Kyro's "what you see is what you draw" approach to 3D rendering. This approach is known as deferred rendering, and it's quite different from the more common method, immediate mode rendering. I suggest you see Dissonance's write-up for a visual representation of the differences between the two approaches, but I will make a clumsy attempt to sum them up.
Immediate mode renderers, including nearly every other 3D graphics card you can buy, draw three-dimensional scenes like the Pentagon processes its budget. They chew through oodles of bandwidth and processing power to get where they're going, then throw out the extra stuff at the end. Immediate mode chips process all the polygons in a scene, apply shading and textures, then send the pixel hurtling down the pipeline with a Z value, or depth information, attached to it. This depth information can use nearly as much bandwidth as the color information for the pixel. Generally these days, a pixel will have 24 bits for Z data and 32 bits for color and transparency info. At the end of this process, the graphics chip starts drawing the scene. Only then does it use the Z information, stored in a Z-buffer, to determine whether one pixel overlaps with another.
Take, for instance, the fundamental object that defines all 3D game scenes: crates. (This I learned from Old Man Murray.) Odds are, any 3D scene will have a number of crates, and probably some barrels, too. Some of those crates and barrels will be behind others, so that crate A obstructs our view of barrel B. An immediate mode renderer processes things in whatever order they come down the pipe. It may draw barrel B in its entirety, then draw crate A in front of it. Only when it comes time to draw the actual pixels for crate A will the chip determine that barrel B shouldn't be visible in the sceneand by then, it's already done all the work to draw barrel B. Only the completed scene is sent to the display, so all you'll ever see is crate A.
In other words, sending a polygon to an immediate mode renderer is like handing Rosie O'Donnell a gift certificate to Luby's.
This process of drawing pixels that will be obscured by others is known as overdraw. Overdraw is the scourge of efficiency in real-time 3D graphics, and it feeds the number-one performance problem for graphics cards these days: memory bandwidth bottlenecks. Memory bandwidth limitations are the reason many newer 3D graphics cards aren't much faster than their predecessors. An old GeForce DDR, for instance, will outrun a brand-new GeForce2 MX 400, because the older card's 128-bit DDR memory interface gives it the edge.
To avoid overdraw and better use resources, the Kyro II chip takes things in a different order than immediate mode renderers. Heck, it takes a very different approach altogether. The Kyro uses tile-based rendering, segmenting the display into small sections and processing each portion in turn. Busting the screen into tiles gives the Kyro several advantages. Among them:
|MSI bringing one of everything to Computex||12|
|First GeForce GTX 1080 driver out with new VRWorks features in tow||9|
|AOC set to release quantum-dot-flavored monitor||14|
|Thermaltake's Level 10 M Advanced mouse offers 16000-DPI sensor||15|
|Customer frustration leads to Windows 10 upgrade dialog changes||45|
|HP joins the black and red clan with Omen gaming PCs||15|
|Crytek releases Cryengine source code on Github||30|
|Zotac beefs up lineup of mini-PCs for Computex||23|
|Toshiba releases 8TB X300 HDD||23|