6 exercises — vertex/fragment shaders, PBR materials (roughness, metallic), frustum and occlusion culling, LOD transitions, depth buffer, and UV mapping.
0 / 6 completed
1 / 6
Which pair correctly describes the two programmable shader stages that run for nearly every rendered triangle?
The vertex shader runs once per vertex and is responsible for transforming vertex positions through the model-view-projection pipeline (object space → world space → view space → clip space), plus passing along data like normals and UVs to the next stage.
The fragment shader (called "pixel shader" in DirectX/HLSL terminology) runs once per rasterized pixel (fragment) and computes the final output colour — this is where texture sampling, lighting calculations, and material effects happen.
Between these two stages, rasterization converts the vertex-shader output (triangles in clip space) into a set of fragments (candidate pixels) to be shaded.
2 / 6
Read: "The scene uses forward rendering with 4x MSAA anti-aliasing and a diffuse + specular PBR material model." What does "PBR" mean, and what do "roughness" and "metallic" describe?
PBR (Physically Based Rendering) is a family of shading models designed so that materials behave consistently under any lighting condition, based on approximating real physical light transport rather than ad-hoc artist tricks.
The two signature PBR parameters: • Roughness (0 = mirror-smooth, 1 = fully matte) controls how tightly or broadly specular highlights spread — a rough surface (concrete) scatters reflections widely; a smooth surface (polished chrome) reflects sharply. • Metallic (0 = dielectric like plastic/wood/skin, 1 = metal like steel/gold) controls whether reflections are tinted by the base colour (metals) or stay white/neutral (dielectrics), and whether there is a visible diffuse (non-reflective) colour component at all — pure metals have none.
3 / 6
What is the difference between "frustum culling" and "occlusion culling"?
Frustum culling tests each object's bounding volume against the camera's view frustum — the pyramid-shaped (or truncated-pyramid, hence "frustum") volume defined by the field of view angle and the near plane / far plane clip distances. Anything entirely outside this volume is skipped before rendering — cheap and effective for large open scenes.
Occlusion culling goes further: even an object inside the frustum can be completely hidden behind a closer, opaque object (e.g. a chair behind a wall) — occlusion culling detects and skips these too, typically using techniques like hardware occlusion queries, hierarchical Z-buffering, or precomputed potentially-visible-sets (PVS).
Both are essential vocabulary in performance discussions: "we're not frustum-culling correctly — off-screen particle systems are still ticking" is a common bug report phrasing.
4 / 6
A profiler shows: "LOD1 mesh popped in abruptly at 40 meters, causing a visible pop." What is being described, and what is a common fix?
LOD (Level of Detail) systems swap a high-polygon mesh (LOD0, used up close) for progressively simpler meshes (LOD1, LOD2, etc.) as the camera distance increases, reducing GPU vertex/triangle load for distant objects the player can barely see in detail anyway.
A "LOD pop" is the visible artifact of an abrupt swap between LOD levels — noticeable especially if the meshes differ significantly in silhouette. Fixes include dithered cross-fade transitions (briefly blending both LODs), choosing distance thresholds where the swap is less noticeable, or moving distant objects to a billboard LOD — a flat, camera-facing quad with a baked texture, used for objects (like trees) so far away that full 3D geometry is wasted detail.
5 / 6
Which term describes a buffer that stores, for each pixel, the distance from the camera to the nearest rendered surface — used so that closer objects correctly draw in front of farther ones?
The depth buffer (also called the Z-buffer) stores one depth value per pixel, representing how far the nearest surface drawn at that pixel is from the camera. Before writing a new fragment's colour, the GPU compares its depth to the value already in the depth buffer — the fragment is only drawn (and the buffer updated) if it is closer, which correctly handles overlapping geometry without manual sorting.
The stencil buffer is a related but different per-pixel buffer, storing an integer mask used for effects like portal rendering, outline effects, or mirror reflections — pixels are selectively drawn based on stencil test rules, independent of depth.
Vocabulary distinction: "depth testing" governs draw order by distance; "stencil testing" governs draw order by an arbitrary per-pixel mask value.
6 / 6
Which vocabulary correctly describes texture mapping and UV coordinates?
UV mapping assigns each vertex of a 3D mesh a 2D coordinate — conventionally named u (horizontal) and v (vertical), each typically normalised to the 0–1 range — that specifies where on a flat 2D texture image that part of the mesh should sample its colour and other surface data (normal maps, roughness maps, etc.) from. This process of "unwrapping" a 3D surface into a 2D layout is often called UV unwrapping.
A material combines one or more textures (the image data) with a shader (the code that decides how to use that data) to determine a surface's final appearance — e.g. a PBR material might sample a base-colour texture, a normal-map texture, and a roughness/metallic texture, then combine them in the fragment shader using the UV coordinates baked into the mesh.
What does the "Graphics & Rendering Vocabulary — Game Engine Language Exercises" exercise cover?
Practise 3D graphics and rendering pipeline vocabulary in English: vertex/fragment shaders, PBR materials, frustum/occlusion culling, LOD, depth buffer, and UV mapping.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
How many questions are in "Graphics & Rendering Vocabulary — Game Engine Language Exercises"?
This exercise has 6 questions. Each one gives instant feedback with an explanation, so you can see exactly why an answer is right or wrong.
Do I need to create an account to save my progress?
No account is required. The progress bar and score are tracked in your browser for the current session -- the exercise is designed to be a quick, repeatable drill rather than something you resume later.
What happens if I get an answer wrong?
You'll see the correct answer highlighted immediately, along with a short explanation of why it's correct. Wrong answers aren't penalized beyond your score, and you can keep going through every question.
How is this exercise different from reading an article?
Articles explain vocabulary and concepts through prose, while exercises like this one are interactive drills -- multiple-choice questions -- that test and reinforce your recall of specific terms and phrasing.
Can I retry this exercise?
Yes -- use the "Try again" button on the results screen to reset your score and go through all the questions again from the start.
Where can I find more Game Engine Language exercises?
Browse the full Game Engine Language hub for related drills, or check the site-wide exercises index for other IT English topics.
Is this exercise suitable for beginners?
This exercise assumes basic familiarity with IT terminology. If a term feels unfamiliar, check the site Glossary for a plain-English definition before attempting the questions.
How often is new content like this published?
New exercises are added regularly across all categories, alongside new vocabulary sets and articles. Check back on the exercises hub to see what's new.