Scene creation and management in Unity - Deep Dive

Overview - Scene creation and management

What is it?

Scene creation and management in Unity means making and controlling different parts of a game or app, called scenes. Each scene holds objects like characters, lights, and cameras that make up a level or menu. Managing scenes lets you switch between these parts smoothly during gameplay or app use. It helps organize your project into smaller, manageable pieces.

Why it matters

Without scene management, a game would be one big messy space, making it hard to load only what is needed and slowing down performance. It would be like having all rooms of a house open at once, making it confusing and inefficient. Scene management helps games run faster, stay organized, and provide smooth transitions, improving player experience.

Where it fits

Before learning scene management, you should understand Unity basics like GameObjects, components, and the Editor interface. After mastering scenes, you can learn advanced topics like asynchronous loading, additive scenes, and scene optimization for bigger projects.

Mental Model

Core Idea

A scene in Unity is like a container holding all the objects and settings for one part of your game, and scene management is the process of loading, unloading, and switching these containers to control what the player sees and interacts with.

Think of it like...

Think of scenes as different rooms in a house. Each room has furniture and decorations (game objects). Scene management is like opening and closing doors to these rooms so you only see and use one room at a time, keeping things neat and easy to navigate.

┌───────────────┐       ┌───────────────┐       ┌───────────────┐
│   Scene 1    │──────▶│   Scene 2    │──────▶│   Scene 3    │
│ (Menu, UI)   │       │ (Level 1)    │       │ (Level 2)    │
└───────────────┘       └───────────────┘       └───────────────┘
       ▲                      ▲                      ▲
       │                      │                      │
   Load/Unload           Load/Unload           Load/Unload
       │                      │                      │
  Player sees only      Player sees only      Player sees only
  one scene at a time   one scene at a time   one scene at a time

Build-Up - 7 Steps

1

Foundation

Understanding What a Scene Is

Concept: Learn what a scene represents in Unity and what it contains.

A scene is a file that holds all the objects, lights, cameras, and settings for one part of your game or app. For example, a main menu or a game level is a scene. You create scenes in the Unity Editor and save them as separate files.

Result

You can create multiple scenes, each representing a different part of your game.

Knowing that scenes are containers for game parts helps you organize your project clearly and plan how your game flows.

2

Foundation

Creating and Saving Scenes

Concept: Learn how to create new scenes and save them properly in Unity.

In Unity Editor, go to File > New Scene to create a new scene. Add objects like cubes or lights. Then save the scene with File > Save As and give it a name. This saves the scene as a file you can open later.

Result

You have a new scene file saved in your project folder, ready to be used or edited.

Creating and saving scenes is the first step to building your game world piece by piece.

3

Intermediate

Loading Scenes with SceneManager

🤔Before reading on: Do you think loading a scene replaces the current scene or adds to it by default? Commit to your answer.

Concept: Learn how to load scenes during gameplay using Unity's SceneManager API.

Unity uses SceneManager.LoadScene("SceneName") to load a scene by name or index. By default, this replaces the current scene. You can also load scenes additively to keep the current scene and add new content.

Result

The game switches to the new scene, showing its objects and hiding the old scene's objects.

Understanding how to load scenes lets you control game flow and transitions between levels or menus.

4

Intermediate

Unloading and Additive Scenes

🤔Before reading on: Do you think additive scene loading automatically unloads previous scenes? Commit to your answer.

Concept: Learn how to load multiple scenes together and unload scenes when no longer needed.

Additive loading lets you load a scene on top of another using SceneManager.LoadScene("SceneName", LoadSceneMode.Additive). To remove a scene, use SceneManager.UnloadSceneAsync("SceneName"). This helps build complex worlds by combining scenes.

Result

Multiple scenes can be active at once, and you can remove scenes to free resources.

Knowing additive loading and unloading helps build flexible and efficient game worlds.

5

Intermediate

Using Build Settings for Scene Management

Concept: Learn how to register scenes in Unity's Build Settings for them to be loadable at runtime.

Open File > Build Settings and add your scenes to the Scenes In Build list. Only scenes listed here can be loaded by name during gameplay. You can reorder scenes to set the default starting scene.

Result

Your scenes are ready to be loaded during the game, and the build knows which scenes to include.

Registering scenes in Build Settings is essential for runtime scene loading to work correctly.

6

Advanced

Asynchronous Scene Loading

🤔Before reading on: Do you think loading scenes asynchronously pauses the game or keeps it running smoothly? Commit to your answer.

Concept: Learn how to load scenes in the background without freezing the game using async loading.

Use SceneManager.LoadSceneAsync("SceneName") to load scenes without stopping the game. This lets you show loading screens or animations while the new scene loads. You can check progress and activate the scene when ready.

Result

Scenes load smoothly in the background, improving player experience during transitions.

Async loading prevents game freezes and allows better control over scene transitions.

7

Expert

Managing Scene Dependencies and Memory

🤔Before reading on: Do you think unloading a scene automatically frees all its memory immediately? Commit to your answer.

Concept: Understand how Unity handles scene memory and dependencies, and how to optimize scene management.

Unloading a scene removes its objects but some assets may stay in memory if referenced elsewhere. Use Resources.UnloadUnusedAssets() to free unused memory. Plan scene dependencies carefully to avoid memory leaks and long load times.

Result

Efficient memory use and smooth gameplay by properly managing scene assets and unloading.

Knowing how Unity manages memory helps prevent performance issues in large projects.

Under the Hood

Unity stores each scene as a separate file containing serialized data of all GameObjects and components. When a scene loads, Unity reads this data, creates the objects in memory, and sets up the rendering and physics systems. SceneManager controls which scenes are active, loading new scenes by replacing or adding to the current ones. Async loading uses background threads to read scene data without blocking the main game thread. Unloading scenes removes objects from memory but asset references can persist until explicitly freed.

Why designed this way?

Unity's scene system was designed to keep projects modular and manageable, allowing developers to work on parts independently. Loading scenes additively supports complex worlds and streaming content. Async loading was added to improve user experience by preventing freezes during heavy loads. The design balances ease of use with flexibility for different game types and sizes.

┌───────────────┐       ┌───────────────┐       ┌───────────────┐
│ Scene File    │──────▶│ SceneManager  │──────▶│ Game Objects  │
│ (Serialized)  │       │ (Load/Unload) │       │ (In Memory)   │
└───────────────┘       └───────────────┘       └───────────────┘
         │                      │                      │
         ▼                      ▼                      ▼
  Disk Storage          Active Scene List       Rendering & Physics
  (Project Folder)      (Current Scenes)        (Visible & Interactive)

Myth Busters - 4 Common Misconceptions

Quick: Does loading a scene add to the current scene by default? Commit yes or no.

Common Belief: Loading a scene always adds it on top of the current scene.

Reality: By default, loading a scene replaces the current scene unless you specify additive loading.

Why it matters: Assuming additive loading by default can cause unexpected scene replacements and lost game state.

Quick: Does unloading a scene immediately free all memory it used? Commit yes or no.

Common Belief: Unloading a scene instantly frees all its memory and assets.

Reality: Unloading removes scene objects but some assets remain in memory if referenced elsewhere until manually freed.

Why it matters: Believing memory is freed immediately can lead to memory leaks and performance problems.

Quick: Can you load scenes by name without adding them to Build Settings? Commit yes or no.

Common Belief: You can load any scene by name at runtime without registering it in Build Settings.

Reality: Only scenes listed in Build Settings can be loaded by name during gameplay.

Why it matters: Not adding scenes to Build Settings causes runtime errors and broken scene loading.

Quick: Does asynchronous scene loading pause the game? Commit yes or no.

Common Belief: Async scene loading pauses the game until loading finishes.

Reality: Async loading runs in the background, keeping the game responsive during loading.

Why it matters: Misunderstanding async loading can lead to poor user experience and missed opportunities for smooth transitions.

Expert Zone

1

Additive scenes share the same lighting and physics settings, so managing these requires careful planning to avoid conflicts.

2

Scene activation after async loading can be delayed to control exactly when the new scene appears, allowing for custom loading screens.

3

Unloading scenes does not guarantee immediate garbage collection; manual calls and asset management are needed for optimal memory use.

When NOT to use

Scene management is not suitable for very small projects where everything fits in one scene. For dynamic content, consider using object pooling or procedural generation instead of many small scenes. Also, avoid additive scenes if your game logic depends on strict scene isolation.

Production Patterns

In real games, scenes are used for menus, levels, cutscenes, and overlays. Developers often load a persistent scene with core systems and add levels additively. Async loading with progress bars is common for smooth player experience. Memory management patterns include unloading unused scenes and assets during gameplay to keep performance stable.

Connections

Modular Programming

Scene management builds on modular programming by dividing a game into independent parts.

Understanding modular programming helps grasp why scenes keep game parts separate and manageable.

Operating System Process Management

Scene loading and unloading is similar to how an OS loads and unloads processes or applications.

Knowing OS process management clarifies how Unity handles memory and resource allocation for scenes.

Theater Stage Management

Scene management in Unity parallels how stage managers control set changes and lighting between acts.

This connection shows how controlling what the audience sees at the right time is key in both theater and game design.

Common Pitfalls

#1 Trying to load a scene by name without adding it to Build Settings.

Wrong approach:

SceneManager.LoadScene("Level2"); // Level2 not in Build Settings

Correct approach:

Add Level2 scene to Build Settings, then call SceneManager.LoadScene("Level2");

Root cause:

Not understanding that Unity requires scenes to be registered in Build Settings for runtime loading.

#2 Loading scenes synchronously causing game freeze during load.

Wrong approach:

SceneManager.LoadScene("Level1"); // freezes game while loading

Correct approach:

StartCoroutine(LoadSceneAsync("Level1")); // loads scene in background

Root cause:

Not using asynchronous loading to keep the game responsive during heavy scene loads.

#3 Unloading a scene but forgetting to unload unused assets, causing memory bloat.

Wrong approach:

SceneManager.UnloadSceneAsync("Level1"); // memory still high

Correct approach:

SceneManager.UnloadSceneAsync("Level1"); Resources.UnloadUnusedAssets();

Root cause:

Misunderstanding that unloading scenes does not automatically free all memory.

Key Takeaways

Scenes in Unity are containers for game parts like levels or menus, helping organize your project.

You must add scenes to Build Settings to load them by name during gameplay.

SceneManager controls loading and unloading scenes, with options for replacing or adding scenes.

Asynchronous scene loading keeps the game smooth by loading in the background.

Proper unloading and asset management prevent memory leaks and keep your game running well.