Difference between revisions of "Category:Rendering"

From polycount
Jump to: navigation, search
(more terms, offline rendering)
Line 25: Line 25:
 
* [http://boards.polycount.net/showthread.php?t=72921 How many textures per model is too many?]
 
* [http://boards.polycount.net/showthread.php?t=72921 How many textures per model is too many?]
 
* ["Polygon Count"]
 
* ["Polygon Count"]
 +
* [http://www.devmaster.net/wiki/Main_Page#Graphics DevMaster wiki Graphics topics]
  
 
== Offline Rendering vs. Real-Time Rendering ==
 
== Offline Rendering vs. Real-Time Rendering ==

Revision as of 18:44, 20 May 2010

Category: Rendering

This page is to help game artists understand how a game engine renders their artwork.

Game Rendering Terms

It helps to understand the terms a graphics programmer uses, so you can talk the talk.

Terms to define:

  • Draw call
  • Texture fetch (see )
  • Fill rate
  • Transform cost
  • Frame rate
  • Frame buffer
  • VRAM, video memory
  • vertex shader
  • pixel shader
  • culling
    If the view camera (the viewer's eye) can't see it, don't bother processing it and only worry about what the view camera can see. # Trivial Accept/Reject Culling, Back-Face Culling, Occlusion Culling, Clipping.
  • z-buffer, Depth Buffer

Threads to distill:

Offline Rendering vs. Real-Time Rendering

  • "Offline rendering systems, such as those used in CAD applications, stress accuracy over frame rate... each frame of animation might take hours to render. Real-time renderers, like game engines and simulators, tend to emphasize constant frame rate to keep animations smooth and fluid, and are willing to sacrifice both geometric and texture detail in order to do this." - from the ExtremeTech 3D Pipeline Tutorial by Dave Salvator

Game Rendering Primers

These articles help artists understand how game engines work, so they can learn how to build art that performs better.


Personal tools
Namespaces

Variants
Actions
Navigation
Tools