Sample questions
Game Rendering PipelineDifficulty 1
Which sequence best describes the conceptual stages a game frame goes through, from scene data to a finished pixel?
- aPixel shading, geometry submission, scene traversal, rasterization
- bScene submission, transformation, rasterization, pixel processing✓
- cRasterization, scene loading, geometry culling, texture upload
- dPixel processing, scene traversal, geometry batching, transformation
Explanation:The conceptual rendering pipeline moves from scene/geometry data, through transformation into screen space, then rasterization converts shapes into candidate pixels, and finally per-pixel processing determines the final color. The other orderings put a later stage before its input exists.
Game Rendering PipelineDifficulty 1
In the rendering pipeline, what does the rasterization stage fundamentally do?
- aIt loads texture data from disk into memory
- bIt decides which objects are inside the camera's view volume
- cIt calculates the final lighting equation for each object
- dIt converts geometric shapes into candidate screen pixels✓
Explanation:Rasterization takes geometric primitives (already transformed into screen space) and determines which pixels they cover, producing fragments that later stages can shade. Texture loading, visibility decisions, and full lighting are separate concerns.
Game Rendering PipelineDifficulty 2
Why does the rendering pipeline transform objects before rasterizing them, instead of rasterizing raw scene coordinates directly?
- aRasterization operates on screen-space coordinates, requiring transformation from world space first✓
- bBecause transformation is what loads the object's texture into memory
- cBecause rasterization can only process one triangle per frame otherwise
- dBecause the pipeline always renders objects in the order they were created, and transformation enforces that order
Explanation:Rasterization needs to know where a shape lands on the 2D screen grid, which requires converting world-space geometry through view and projection transforms into screen space first. Texture loading and creation-order sequencing are unrelated to this requirement.
Game Rendering PipelineDifficulty 1
What is a draw call, at a conceptual level?
- aA function that calculates how many frames per second the game is running at
- bA request sent from the player's input device to move the camera
- cA command telling rendering hardware to draw geometry with given settings✓
- dA background thread that loads level data from disk
Explanation:A draw call is the instruction that tells the rendering hardware 'draw this geometry now, with this current configuration.' It is not related to frame-rate measurement, input handling, or disk streaming, which are separate systems.
Game Rendering PipelineDifficulty 2
Why is issuing a large number of draw calls per frame considered expensive?
- aBecause each draw call permanently deletes the geometry it drew afterward
- bBecause draw calls can only be issued once per second by design
- cDraw-call overhead adds up beyond the drawing itself as count grows✓
- dBecause the game must pause the simulation while every draw call executes
Explanation:Beyond the actual drawing work, each draw call incurs fixed overhead for setting up state and submitting the command. With thousands of small draw calls, this per-call overhead can dominate total frame cost even if the geometry itself is simple.
Game Rendering PipelineDifficulty 2
A scene renders 5,000 small props, each issued as its own separate draw call, and the frame rate is low even though the total polygon count is modest. What is the most likely conceptual cause?
- aThe GPU cannot store more than 5,000 polygons in memory at once
- bHigh draw call count creates overhead dominating the frame✓
- cThe scene has too many light sources for the camera to process
- dThe props are using too many input controller bindings
Explanation:Low polygon count but low frame rate with thousands of separate draw calls is a classic symptom of draw-call overhead: the cost is in the number of submissions, not the geometric complexity. Memory capacity, lighting count, and input bindings are unrelated symptoms.