Difference between revisions of "GameRenderingTerminology"
From polycount
(Talk) |
EricChadwick (Talk | contribs) (→Glossary) |
||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | <!-- ## page was renamed from Game Rendering Terminology --> | |
| − | + | ||
| − | + | ||
= Game Rendering Terminology = | = Game Rendering Terminology = | ||
| − | + | These are terms every tech-savvy game artist should know. | |
| + | |||
| + | |||
| + | |||
| + | === Batching === | ||
| + | |||
| + | [http://www.polycount.com/forum/showthread.php?t=155560 On Draw Calls & Batching] | ||
| + | |||
| + | [http://docs.unity3d.com/Manual/DrawCallBatching.html Unity - Manual: Draw Call Batching] | ||
| + | |||
| + | |||
| + | === Culling === | ||
| + | (definition needed) 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 | ||
| + | |||
| + | === Draw Call === | ||
| + | [http://www.polycount.com/forum/showthread.php?t=155560 On Draw Calls & Batching] | ||
| + | |||
| + | [http://docs.unity3d.com/Manual/DrawCallBatching.html Unity - Manual: Draw Call Batching] | ||
| + | |||
| + | [http://www.polycount.com/forum/showthread.php?t=64325 Render Pass vs. Draw Call] | ||
| + | |||
| + | [http://www.polycount.com/forum/showthread.php?t=126571 Pasting into alpha channel photoshop] | ||
| + | |||
| + | === Fill Rate === | ||
| + | (definition needed) Long thin triangles can [http://boards.polycount.net/showthread.php?p=886302#post886302 cause slower rendering]. | ||
| + | |||
| + | === Frame Buffer === | ||
| + | (definition needed) | ||
| + | |||
| + | === Frame Rate === | ||
| + | (definition needed) | ||
| + | |||
| + | === GPU === | ||
| + | The Graphics Processing Unit is a parallel processor for floating point operations; it's the heart & soul of your graphics card. It's mostly used for rendering calculations, but it can also be tricked into doing physics, particle systems, vertex skinning, real-time texture compression, etc. It frees the CPU (Central Processing Unit) to handle the rest of the processing tasks in the game like transforms, AI, sound, etc. | ||
| + | |||
| + | === Pixel Shader === | ||
| + | (definition needed) | ||
| + | |||
| + | === T-Vertex === | ||
| + | (definition needed) T-vertices can cause gaps or seams. | ||
| + | |||
| + | === Texture Fetch === | ||
| + | (definition needed) | ||
| + | |||
| + | === Transform Cost === | ||
| + | (definition needed) | ||
| + | |||
| + | === Vertex Cache === | ||
| + | (definition needed) | ||
| + | |||
| + | === Vertex Shader === | ||
| + | (definition needed) | ||
| + | |||
| + | === Vertex Splits === | ||
| + | A ton of vertex splits can cause vertex cache misses. | ||
| + | |||
| + | * [http://boards.polycount.net/showthread.php?p=767368#post767368 FAQ: Game art optimisation (do polygon counts really matter?)] on the Polycount forum | ||
| + | * [http://www.ericchadwick.com/examples/provost/byf2.html#wts Welcome to Splitsville] from the article "Beautiful Yet Friendly" by Guillaume Provost | ||
| + | * [[Category:Whitepapers]]#Game_Renderer_Articles | ||
| + | * [http://www.polycount.com/forum/showthread.php?t=62562 What is UV count?] on the Polycount forum | ||
| + | |||
| + | === VRAM === | ||
| + | (definition needed) Video memory | ||
| − | + | === Z-Buffer === | |
| − | + | (definition needed) Also known as the Depth Buffer. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | These are generally 16-bit buffers that store the depth of a pixel (in relation to it's distance from the camera) as a black & white value. See Wikipedia's [http://en.wikipedia.org/wiki/Z-buffering Z-buffering] page. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ---- | |
| − | + | [[Category:Rendering]] | |
Latest revision as of 21:31, 26 July 2015
Contents
Game Rendering Terminology
These are terms every tech-savvy game artist should know.
Batching
Unity - Manual: Draw Call Batching
Culling
(definition needed) 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
Draw Call
Unity - Manual: Draw Call Batching
Pasting into alpha channel photoshop
Fill Rate
(definition needed) Long thin triangles can cause slower rendering.
Frame Buffer
(definition needed)
Frame Rate
(definition needed)
GPU
The Graphics Processing Unit is a parallel processor for floating point operations; it's the heart & soul of your graphics card. It's mostly used for rendering calculations, but it can also be tricked into doing physics, particle systems, vertex skinning, real-time texture compression, etc. It frees the CPU (Central Processing Unit) to handle the rest of the processing tasks in the game like transforms, AI, sound, etc.
Pixel Shader
(definition needed)
T-Vertex
(definition needed) T-vertices can cause gaps or seams.
Texture Fetch
(definition needed)
Transform Cost
(definition needed)
Vertex Cache
(definition needed)
Vertex Shader
(definition needed)
Vertex Splits
A ton of vertex splits can cause vertex cache misses.
- FAQ: Game art optimisation (do polygon counts really matter?) on the Polycount forum
- Welcome to Splitsville from the article "Beautiful Yet Friendly" by Guillaume Provost
- Game_Renderer_Articles
- What is UV count? on the Polycount forum
VRAM
(definition needed) Video memory
Z-Buffer
(definition needed) Also known as the Depth Buffer.
These are generally 16-bit buffers that store the depth of a pixel (in relation to it's distance from the camera) as a black & white value. See Wikipedia's Z-buffering page.
