NavMesh baking in Unity - Step-by-Step Execution

Concept Flow - NavMesh baking

Scene Setup with Geometry

↓

Mark Walkable Surfaces

↓

Open Navigation Window

↓

Configure Bake Settings

↓

Click Bake Button

↓

NavMesh Data Generated

↓

NavMesh Ready for Agent Pathfinding

NavMesh baking creates a navigation mesh from scene geometry so agents can find paths on walkable surfaces.

Execution Sample

Unity

using UnityEngine;
using UnityEngine.AI;

public class BakeNavMesh : MonoBehaviour {
    void Start() {
        NavMeshSurface surface = GetComponent<NavMeshSurface>();
        surface.BuildNavMesh();
    }
}

This script triggers NavMesh baking at runtime on the attached NavMeshSurface component.

Execution Table

Step	Action	Input/State	Output/Result
1	Scene loaded	Scene with floors and obstacles	Geometry ready for NavMesh
2	Mark surfaces	Floors marked as walkable	Walkable areas identified
3	Open Navigation window	User opens NavMesh settings	Settings panel visible
4	Configure bake settings	Agent radius, height, slope set	Bake parameters set
5	Click Bake	User clicks bake button	NavMesh baking starts
6	Bake process	Geometry and settings input	NavMesh polygons generated
7	Bake complete	NavMesh data created	NavMesh ready for pathfinding
8	Use NavMesh	Agent requests path	Agent navigates on NavMesh
9	Exit	NavMesh baked and usable	Process ends

💡 NavMesh baking ends after generating navigation data for agent pathfinding.

Variable Tracker

Variable	Start	After Step 2	After Step 5	After Step 7	Final
Scene Geometry	Loaded	Loaded	Loaded	Loaded	Loaded
Walkable Surfaces	None	Marked	Marked	Marked	Marked
Bake Settings	Default	Default	Configured	Configured	Configured
NavMesh Data	None	None	None	Generated	Generated

Key Moments - 3 Insights

Why do we need to mark surfaces as walkable before baking?

Marking walkable surfaces tells the NavMesh baker which areas agents can walk on, as shown in step 2 of the execution table.

What happens if bake settings like agent radius are incorrect?

Incorrect settings cause the NavMesh to not fit the agent properly, leading to navigation errors, as configured in step 4 and affecting step 6.

Can NavMesh baking be done at runtime?

Yes, as shown in the code sample, calling BuildNavMesh() on a NavMeshSurface bakes the NavMesh during runtime.

Visual Quiz - 3 Questions

Look at the execution table, at which step is the NavMesh data generated?

A Step 5

B Step 7

C Step 6

D Step 8

💡 Hint

Check the 'Output/Result' column for when NavMesh polygons are created.

According to the variable tracker, when does the NavMesh Data change from None to Generated?

A After Step 7

B After Step 5

C After Step 2

D At Start

💡 Hint

Look at the 'NavMesh Data' row and see when it changes.

If the walkable surfaces are not marked, what will happen during baking?

A NavMesh will bake normally with all surfaces walkable

B Bake settings will override walkable surfaces

C NavMesh will not generate any walkable areas

D Bake will fail with an error

💡 Hint

Refer to step 2 and 6 in the execution table about walkable surfaces.

Concept Snapshot

NavMesh baking creates a navigation mesh from scene geometry.
Mark walkable surfaces before baking.
Configure agent settings (radius, height, slope).
Click Bake to generate NavMesh data.
Agents use NavMesh for pathfinding.

Full Transcript

NavMesh baking in Unity involves preparing your scene by marking which surfaces agents can walk on. You open the Navigation window, set bake parameters like agent size, and then click the Bake button. The system processes the geometry and settings to create a navigation mesh. This mesh allows agents to find paths and move around obstacles. You can also bake NavMesh at runtime by calling BuildNavMesh() on a NavMeshSurface component. Key steps include marking walkable surfaces, configuring settings, and baking to generate usable navigation data.