NavMesh baking in Unity - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this NavMesh baking status check?

Consider this Unity C# script snippet that checks the NavMesh baking status. What will be printed in the console?

Unity

using UnityEngine;
using UnityEngine.AI;

public class NavMeshStatusCheck : MonoBehaviour
{
    void Start()
    {
        var buildSettings = NavMesh.GetSettingsByID(0);
        Debug.Log($"Agent Type ID: {buildSettings.agentTypeID}");
        Debug.Log($"Voxel Size: {buildSettings.voxelSize}");
    }
}

A Agent Type ID: 1\nVoxel Size: 0.15

B Agent Type ID: 0\nVoxel Size: 0.3

C Agent Type ID: 1\nVoxel Size: 0.3

D Agent Type ID: 0\nVoxel Size: 0.15

💡 Hint

The default agent type ID for the first NavMesh agent is 0, and the default voxel size is 0.3.

The NavMesh.GetSettingsByID(0) returns the default agent settings. By default, agentTypeID is 0 and voxelSize is 0.3 in Unity's NavMesh baking settings.

🧠 Conceptual

intermediate

Which component is essential for NavMesh baking in Unity scenes?

In Unity, to bake a NavMesh for AI navigation, which component must be present on the GameObjects that define walkable surfaces?

A NavMeshSurface

B NavMeshLink

C NavMeshObstacle

D NavMeshAgent

💡 Hint

This component defines the area where the NavMesh is generated.

NavMeshSurface is the component that marks the geometry to be included in the NavMesh baking process. NavMeshAgent is for moving agents, NavMeshObstacle blocks paths, and NavMeshLink connects separate NavMeshes.

🔧 Debug

advanced

Why does this NavMesh baking code fail to update the NavMesh?

This Unity C# code attempts to bake a NavMesh at runtime but does not update the navigation mesh as expected. What is the cause?

Unity

using UnityEngine;
using UnityEngine.AI;

public class RuntimeNavMeshBake : MonoBehaviour
{
    public NavMeshSurface surface;

    void Start()
    {
        surface.BuildNavMeshAsync();
        Debug.Log("NavMesh baking started.");
    }
}

A NavMeshSurface requires Bake() instead of BuildNavMeshAsync() for runtime baking.

B BuildNavMeshAsync is deprecated and does not work at runtime.

C NavMeshSurface must be disabled before baking.

D BuildNavMeshAsync returns a JobHandle that must be completed to finish baking.

💡 Hint

Async baking returns a handle that controls job completion.

BuildNavMeshAsync starts an asynchronous job and returns a JobHandle. Without completing this job, the NavMesh is not fully baked. You must call Complete() on the JobHandle to finish baking.

📝 Syntax

advanced

Identify the syntax error in this NavMesh baking code snippet.

Which option contains the correct syntax to bake a NavMesh using NavMeshSurface in Unity?

Unity

public class BakeNavMeshExample : MonoBehaviour
{
    public NavMeshSurface surface;

    void Bake()
    {
        // Bake the NavMesh here
    }
}

A surface.BuildNavMesh();

B surface.BuildNavMeshAsync();

C surface.BakeNavMesh();

D surface.BuildNavMeshAsync

💡 Hint

Check the exact method name and usage.

The correct method to bake the NavMesh synchronously is BuildNavMesh(). BuildNavMeshAsync() requires parentheses and returns a JobHandle. BakeNavMesh() does not exist. Missing parentheses cause syntax errors.

🚀 Application

expert

How many NavMesh areas are created after this baking setup?

You have a Unity scene with two NavMeshSurface components. One is set to include only the "Walkable" layer, and the other includes only the "Jump" layer. After baking both surfaces, how many distinct NavMesh areas will exist?

A No NavMesh areas because layers cannot be baked separately

B One combined NavMesh area including both layers

C Two distinct NavMesh areas, one for each layer

D Multiple areas merged into a single NavMeshSurface automatically

💡 Hint

Each NavMeshSurface bakes its own area based on included layers.

Each NavMeshSurface bakes a separate NavMesh area based on its included layers. Having two surfaces with different layers results in two distinct NavMesh areas in the scene.