Asset bundles and optimization in Unity - Step-by-Step Execution

Concept Flow - Asset bundles and optimization

Create Assets

↓

Build Asset Bundles

↓

Load Asset Bundles at Runtime

↓

Use Assets in Game

↓

Unload Asset Bundles to Free Memory

↓

Optimize by Compressing and Caching

This flow shows how assets are grouped into bundles, loaded when needed, used in the game, then unloaded to save memory, with optimization steps like compression and caching.

Execution Sample

Unity

using UnityEngine;

public class AssetBundleExample : MonoBehaviour {
    void Start() {
        var bundle = AssetBundle.LoadFromFile("path/to/bundle");
        if (bundle == null) {
            Debug.LogError("Failed to load AssetBundle!");
            return;
        }
        var prefab = bundle.LoadAsset<GameObject>("MyPrefab");
        Instantiate(prefab);
        bundle.Unload(false);
    }
}

This code loads an asset bundle from a file, loads a prefab from it, creates an instance in the scene, then unloads the bundle but keeps the prefab in memory.

Execution Table

Step	Action	AssetBundle State	Loaded Asset	Memory Usage	Output
1	Call LoadFromFile	Bundle loaded in memory	None	Increased	Bundle ready
2	Call LoadAsset("MyPrefab")	Bundle loaded	Prefab loaded	Increased	Prefab ready
3	Call Instantiate(prefab)	Bundle loaded	Prefab instance created	Increased	Prefab appears in scene
4	Call bundle.Unload(false)	Bundle unloaded, prefab kept	Prefab instance alive	Reduced (bundle data freed)	Bundle data freed
5	End of execution	Bundle unloaded	Prefab instance alive	Stable	Game runs with prefab

💡 Execution stops after unloading the bundle but keeping the prefab instance active in memory.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
bundle	null	Loaded	Loaded	Loaded	Unloaded	Unloaded
prefab	null	null	Loaded	Loaded	Loaded	Loaded
prefab instance	null	null	null	Created	Created	Created

Key Moments - 3 Insights

Why does the prefab instance stay alive after unloading the bundle?

Because bundle.Unload(false) unloads the bundle data but keeps loaded assets like the prefab in memory, as shown in step 4 of the execution_table.

What happens if we call bundle.Unload(true) instead?

Calling bundle.Unload(true) unloads the bundle and all loaded assets, so the prefab instance would be destroyed, unlike in step 4 where false is used.

Why do we load asset bundles instead of loading assets directly?

Asset bundles let us group assets and load them only when needed, saving memory and improving performance, as shown by the memory usage changes in the execution_table.

Visual Quiz - 3 Questions

Look at the execution_table, what is the state of 'bundle' after step 4?

A Loaded

B Unloaded

C Null

D Destroyed

💡 Hint

Check the 'AssetBundle State' column at step 4 in the execution_table.

At which step does the prefab instance get created?

A Step 1

B Step 2

C Step 3

D Step 4

💡 Hint

Look at the 'Output' column for when the prefab appears in the scene in the execution_table.

If we changed bundle.Unload(false) to bundle.Unload(true), what would happen to the prefab instance?

A It would be destroyed

B It would stay alive

C It would duplicate

D No change

💡 Hint

Refer to key_moments about the difference between Unload(false) and Unload(true).

Concept Snapshot

Asset bundles group assets for loading on demand.
Load bundles with LoadFromFile, then load assets inside.
Instantiate assets to use in scenes.
Unload bundles with Unload(false) to free bundle data but keep assets.
Use Unload(true) to free everything.
Optimize by compressing bundles and caching them.

Full Transcript

This visual execution shows how Unity asset bundles work step-by-step. First, assets are grouped into bundles. Then the bundle is loaded from a file into memory. Next, an asset like a prefab is loaded from the bundle. The prefab is instantiated in the scene, creating a visible object. After use, the bundle is unloaded with Unload(false), which frees the bundle data but keeps the prefab instance alive. This saves memory while keeping the asset usable. The process helps optimize game memory and loading times by loading only needed assets and unloading bundles when done. Key points include understanding how Unload(false) differs from Unload(true) and how asset bundles improve performance by grouping and compressing assets.

Practice

1. What is the main benefit of using Asset Bundles in Unity?

easy

A. Automatically generate game scripts

B. Create UI elements faster

C. Improve physics calculations

D. Load game assets only when needed to save memory and download size

Solution

1. Step 1: Understand what Asset Bundles do

   Asset Bundles allow loading assets like textures, models, or sounds only when the game needs them, not all at once.

2. Step 2: Identify the main benefit

   This selective loading saves memory and reduces the initial download size of the game.

3. Final Answer:

   Load game assets only when needed to save memory and download size -> Option D

4. Quick Check:

   Asset Bundles optimize memory and size = B [OK]

Hint: Asset Bundles help load assets on demand, saving resources [OK]

Common Mistakes:

• Confusing Asset Bundles with script generation
• Thinking Asset Bundles improve physics
• Assuming Asset Bundles speed up UI creation

2. Which of the following is the correct way to load an Asset Bundle asynchronously in Unity?

easy

A. AssetBundle.LoadFromFileAsync(path)

B. AssetBundle.LoadFromFile(path)

C. AssetBundle.LoadAsync(path)

D. AssetBundle.LoadBundleAsync(path)

Solution

1. Step 1: Recall Unity's async Asset Bundle loading method

   The official method to load an Asset Bundle asynchronously from a file is AssetBundle.LoadFromFileAsync(path).

2. Step 2: Check other options for correctness

   LoadFromFile(path) is synchronous, LoadAsync(path) and LoadBundleAsync(path) do not exist in Unity API.

3. Final Answer:

   AssetBundle.LoadFromFileAsync(path) -> Option A

4. Quick Check:

   Async load method = LoadFromFileAsync [OK]

Hint: Async loading uses LoadFromFileAsync method exactly [OK]

Common Mistakes:

• Using synchronous LoadFromFile instead of async
• Choosing non-existent LoadAsync or LoadBundleAsync methods
• Confusing method names

3. Consider this code snippet in Unity:

var bundleRequest = AssetBundle.LoadFromFileAsync("Assets/Bundles/characters");
yield return bundleRequest;
var bundle = bundleRequest.assetBundle;
var prefab = bundle.LoadAsset<GameObject>("Hero");
Instantiate(prefab);

What happens when this code runs?

medium

A. Throws a compile-time error due to incorrect method usage

B. Loads the asset bundle synchronously and immediately instantiates 'Hero'

C. Loads the asset bundle asynchronously, then loads and instantiates the 'Hero' prefab

D. Loads the asset bundle but does not instantiate any prefab

Solution

1. Step 1: Analyze the async loading call

   AssetBundle.LoadFromFileAsync starts loading the bundle asynchronously, and yield return bundleRequest waits until loading finishes.

2. Step 2: Load asset and instantiate

   After loading, bundle.LoadAsset<GameObject>("Hero") loads the prefab named 'Hero', and Instantiate(prefab) creates it in the scene.

3. Final Answer:

   Loads the asset bundle asynchronously, then loads and instantiates the 'Hero' prefab -> Option C

4. Quick Check:

   Async load + instantiate prefab = C [OK]

Hint: Async load then yield before using asset bundle [OK]

Common Mistakes:

• Confusing async with sync loading
• Forgetting to yield before accessing assetBundle
• Assuming no instantiation happens

4. You wrote this code to unload an Asset Bundle after use:

bundle.Unload(false);

But memory usage stays high. What is the likely problem?

medium

A. Unload(false) unloads everything including assets, so code is correct

B. Unload(false) unloads only the bundle but keeps loaded assets in memory

C. You must call bundle.Dispose() instead of Unload()

D. Unload(false) causes a runtime error and stops unloading

Solution

1. Step 1: Understand Unload parameter meaning

   Unload(false) unloads the Asset Bundle but keeps all loaded assets in memory.

2. Step 2: Identify why memory stays high

   Since assets are still loaded, memory usage remains high until you unload assets or reload scene.

3. Final Answer:

   Unload(false) unloads only the bundle but keeps loaded assets in memory -> Option B

4. Quick Check:

   Unload(false) keeps assets loaded = A [OK]

Hint: Unload(true) frees assets too; false keeps them loaded [OK]

Common Mistakes:

• Assuming Unload(false) frees all memory
• Using Dispose() which doesn't exist for AssetBundle
• Thinking Unload(false) causes errors

5. You want to optimize your Unity game by loading only necessary assets at runtime and unloading them properly. Which approach best achieves this?

hard

A. Build asset bundles for groups of assets, load bundles asynchronously when needed, instantiate assets, then unload bundles with Unload(true) after use

B. Load all assets at game start synchronously, keep bundles loaded throughout gameplay

C. Use Resources.Load for all assets and never unload them

D. Build asset bundles but never unload them to avoid errors

Solution

1. Step 1: Identify best practice for asset loading

   Building asset bundles for logical groups and loading them asynchronously reduces initial load and keeps gameplay smooth.

2. Step 2: Proper unloading to free memory

   Unloading bundles with Unload(true) frees both the bundle and loaded assets, optimizing memory usage.

3. Final Answer:

   Build asset bundles for groups of assets, load bundles asynchronously when needed, instantiate assets, then unload bundles with Unload(true) after use -> Option A

4. Quick Check:

   Async load + proper unload = A [OK]

Hint: Async load bundles, instantiate assets, unload with true to free memory [OK]

Common Mistakes:

• Loading all assets at start wastes memory
• Using Resources.Load without unloading
• Never unloading bundles causes memory leaks