Practice game engine scene management vocabulary: scene graph, level loading, scene transitions, performance problems, asset streaming, and scene serialization.
0 / 5 completed
1 / 5
The engine organises all game objects in a ___ graph that determines rendering order and transform inheritance.
A scene graph is a hierarchical data structure (usually a tree) that organises all objects in a scene. Child nodes inherit transforms from their parents, making it easy to move a character and have all attached objects move with it.
2 / 5
A game designer says: 'We're ___ the next level while the player reads the story text.' What technique is this?
'Loading the next level' means reading all the assets (models, textures, audio, level data) required for the upcoming scene into memory. Doing it asynchronously during a cutscene or loading screen hides the wait from the player.
3 / 5
The team needs a smooth ___ transition between the menu scene and the first level.
A scene transition is the in-engine process of moving from one scene to another — unloading current objects, loading new ones, and typically playing a visual effect (fade to black, wipe) to mask the loading time.
4 / 5
A programmer reports: 'The scene is too ___ — we're getting frame drops.' What is the root cause?
'The scene is too heavy' means the scene contains more geometry, draw calls, scripts, or physics objects than the hardware can process within a frame budget (e.g., 16 ms for 60 fps), resulting in dropped frames.
5 / 5
The open-world game uses ___ streaming to load terrain and objects as the player moves.
Asset streaming loads game assets (terrain chunks, buildings, NPCs) into memory as the player approaches them and unloads distant assets to free memory. This allows large open worlds without requiring everything in RAM at once.