Gcp 2 Final

Front 1

What are the 3 categories for simulation frame rates as measured in frames per second?

Back 1

cad (computer aided design), interactive sim and realtime

Front 2

What is the target frame rate?

Back 2

60 fps, anything greater is a waste

Front 3

the gathering of performance data in a realtime engine

Back 3

metrics

Front 4

the realtime engine is divided up into three main parts..

Back 4

app, cull and draw

Front 5

when one part of the realtime engine takes much longer to complete than the others

Back 5

performance bottleneck

Front 6

when the computer takes longer to figure out which polys to draw than to actually draw them

Back 6

cull bottleneck

Front 7

This will switch out polygons that are far aways and thus less important. less polys = less cull

Back 7

level of detail

Front 8

when all the video card memory is used up. symptoms: periodic frame rate "hiccup"

Back 8

memory bottlenecks

Front 9

what are some memory bottleneck solutions?

Back 9

use less textures, use smaller res screen (smaller frame buffer), use smaller textures, turn off mipmapping, use smaller bit depth, use texture compression

Front 10

when the poly count limit of the graphics card is reached. symptoms: gradual slowdown of frame rate.

Back 10

transform bottleneck

Front 11

what are some transform bottleneck solutions?

Back 11

use less animations, use less polygons, use less particles

Front 12

the more realtime lights, the slower the system runs

Back 12

lighting bottlenecks

Front 13

what are some lighting bottleneck solutions?

Back 13

use less lights, instead you can use colored textures, colored vertexes, light maps

Front 14

Can replace lighting calculations, thus increasing performance

Back 14

lightmaps - downside is more memory but they're static

Front 15

difference between polys can slow down the system.

Back 15

state change bottlenecks

Front 16

each polygon has certain attributes associated with them..

Back 16

geometry (size & shape) and state (colors, textures, materials, normals and uvs)

Front 17

when triangles are identical in state, they can be rendered very efficiently

Back 17

tristeps

Front 18

what are some state change bottleneck solutions?

Back 18

combine objects together when possible and minimize the number of textures used by collaging the textures together

Front 19

too many overlapping polygons on screen

Back 19

fill rate bottlenecks

Front 20

each level of depth in a scene can cause a pixel to be drawn more than once

Back 20

depth complexity

Front 21

what are some fill rate bottleneck solutions?

Back 21

use a smaller res screen, use lod, try to reduce the amount of alpha textured pixels, remove unseen polys and occlusion culling