NavMesh Agent component in Unity - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to get the NavMeshAgent component from the GameObject.

Unity

NavMeshAgent agent = gameObject.GetComponent<[1]>();

Drag options to blanks, or click blank then click option'

ANavMeshAgent

BRigidbody

CCollider

DAnimator

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong component type like Rigidbody or Collider.

Forgetting the generic type syntax with angle brackets.

The NavMeshAgent component is accessed using GetComponent<NavMeshAgent>().

2fill in blank

medium

Complete the code to set the destination of the NavMeshAgent to a Vector3 position.

Unity

agent.[1](targetPosition);

Drag options to blanks, or click blank then click option'

AGoTo

BMove

CSetDestination

DNavigate

Attempts:

3 left

💡 Hint

Common Mistakes

Using non-existent methods like Move or GoTo.

Trying to assign destination directly instead of using a method.

The method to set the destination for a NavMeshAgent is SetDestination(Vector3).

3fill in blank

hard

Fix the error in the code to check if the NavMeshAgent has reached its destination.

Unity

if (agent.remainingDistance [1] agent.stoppingDistance && !agent.pathPending) {
    // Reached destination
}

Drag options to blanks, or click blank then click option'

A>=

B<=

C==

D!=

Attempts:

3 left

💡 Hint

Common Mistakes

Using greater than comparison which is incorrect.

Checking equality which may fail due to floating point precision.

To check if the agent reached the destination, remainingDistance should be less than or equal to stoppingDistance.

4fill in blank

hard

Fill both blanks to create a dictionary of agent speeds for agents with speed greater than 3.

Unity

var fastAgents = agents.ToDictionary(agent => agent.[1], agent => agent.[2]).Where(kv => kv.Value > 3);

Drag options to blanks, or click blank then click option'

Aname

Bspeed

Cdestination

DremainingDistance

Attempts:

3 left

💡 Hint

Common Mistakes

Using destination or remainingDistance as dictionary keys or values.

Mixing up key and value properties.

Use 'name' as the key and 'speed' as the value to create a dictionary of agent speeds.

5fill in blank

hard

Fill all three blanks to filter agents moving faster than 5 and create a dictionary with agent names in uppercase as keys.

Unity

var fastAgents = agents.Where(agent => agent.[1] [2] 5).ToDictionary(agent => agent.[3]);

Drag options to blanks, or click blank then click option'

Aspeed

B>

Cname.ToUpper()

DremainingDistance

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect comparison operators.

Using remainingDistance instead of speed.

Not converting names to uppercase.

Filter agents with speed > 5 and use their uppercase names as dictionary keys.

Practice

1. What is the primary purpose of the NavMeshAgent component in Unity?

easy

A. To handle user input for character movement

B. To create 3D models for characters

C. To move characters smoothly using pathfinding on a navigation mesh

D. To play animations on characters

Solution

1. Step 1: Understand NavMeshAgent role

   The NavMeshAgent component is designed to move objects smoothly on a navigation mesh, handling pathfinding and obstacle avoidance.

2. Step 2: Compare options

   Options B, C, and D describe unrelated functions like modeling, input, and animation, which are not NavMeshAgent's job.

3. Final Answer:

   To move characters smoothly using pathfinding on a navigation mesh -> Option C

4. Quick Check:

   NavMeshAgent moves objects on NavMesh = A [OK]

Hint: NavMeshAgent moves objects using pathfinding on NavMesh [OK]

Common Mistakes:

• Confusing NavMeshAgent with animation or input components
• Thinking NavMeshAgent creates models
• Assuming NavMeshAgent handles user controls

2. Which of the following is the correct way to set a destination for a NavMeshAgent named agent in C#?

easy

A. agent.MoveTo(new Vector3(10, 0, 5));

B. agent.Navigate(new Vector3(10, 0, 5));

C. agent.GoTo(new Vector3(10, 0, 5));

D. agent.SetDestination(new Vector3(10, 0, 5));

Solution

1. Step 1: Recall NavMeshAgent method for destination

   The correct method to set a destination is SetDestination, which takes a Vector3 position.

2. Step 2: Check method names

   Methods like MoveTo, GoTo, and Navigate do not exist on NavMeshAgent.

3. Final Answer:

   agent.SetDestination(new Vector3(10, 0, 5)); -> Option D

4. Quick Check:

   SetDestination sets target position = B [OK]

Hint: Use SetDestination with Vector3 to move NavMeshAgent [OK]

Common Mistakes:

• Using non-existent methods like MoveTo or GoTo
• Forgetting to use Vector3 as parameter
• Confusing SetDestination with transform.position

3. Given the code below, what will be the output in the Unity Console?

using UnityEngine;
using UnityEngine.AI;

public class MoveAgent : MonoBehaviour
{
    public NavMeshAgent agent;

    void Start()
    {
        agent = GetComponent<NavMeshAgent>();
        Vector3 target = new Vector3(5, 0, 5);
        bool result = agent.SetDestination(target);
        Debug.Log(result);
    }
}

medium

A. True

B. False

C. NullReferenceException error

D. No output

Solution

1. Step 1: Understand SetDestination return value

   The SetDestination method returns true if the destination is valid and reachable on the NavMesh.

2. Step 2: Analyze given target and agent

   The target (5,0,5) is a valid position assuming the NavMesh covers it, so SetDestination returns true and logs it.

3. Final Answer:

   True -> Option A

4. Quick Check:

   SetDestination success returns true = C [OK]

Hint: SetDestination returns true if path is valid [OK]

Common Mistakes:

• Assuming SetDestination returns void
• Expecting false without checking NavMesh coverage
• Ignoring possible NullReference if agent not assigned

4. What is wrong with the following code snippet that tries to move a NavMeshAgent?

public NavMeshAgent agent;

void Update() {
    Vector3 destination = new Vector3(10, 0, 10);
    agent.SetDestination(destination);
}

medium

A. SetDestination requires a NavMeshPath parameter

B. Calling SetDestination every frame can cause performance issues

C. NavMeshAgent must be moved using transform.position

D. The destination vector is invalid

Solution

1. Step 1: Review usage of SetDestination in Update

   Calling SetDestination every frame is unnecessary and can cause performance overhead because the agent recalculates path repeatedly.

2. Step 2: Check other options

   The destination vector is valid, NavMeshAgent should not be moved by transform.position, and SetDestination takes a Vector3, not NavMeshPath.

3. Final Answer:

   Calling SetDestination every frame can cause performance issues -> Option B

4. Quick Check:

   SetDestination in Update causes overhead = D [OK]

Hint: Avoid calling SetDestination every frame; call only on target change [OK]

Common Mistakes:

• Moving agent by changing transform.position directly
• Passing wrong parameter types to SetDestination
• Ignoring performance impact of repeated calls

5. You want a NavMeshAgent to move to a target only if the path is valid and complete. Which code snippet correctly checks this before moving the agent?

NavMeshPath path = new NavMeshPath();
Vector3 target = new Vector3(7, 0, 7);

// Which code is correct?

hard

A. if (agent.CalculatePath(target, path) && path.status == NavMeshPathStatus.PathComplete) {
agent.SetDestination(target);
}

B. if (agent.SetDestination(target)) {
agent.CalculatePath(target, path);
}

C. agent.SetDestination(target);
if (path.status == NavMeshPathStatus.PathComplete) {
// do nothing
}

D. if (path.status == NavMeshPathStatus.PathPartial) {
agent.SetDestination(target);
}

Solution

1. Step 1: Understand path calculation and status check

   Use CalculatePath to check if a path to the target exists and is complete before setting destination.

2. Step 2: Analyze each option

   if (agent.CalculatePath(target, path) && path.status == NavMeshPathStatus.PathComplete) { agent.SetDestination(target); } correctly calls CalculatePath and checks path.status before SetDestination. Others either call methods in wrong order or check wrong status.

3. Final Answer:

   if (agent.CalculatePath(target, path) && path.status == NavMeshPathStatus.PathComplete) { agent.SetDestination(target); } -> Option A

4. Quick Check:

   CalculatePath + PathComplete check before SetDestination = A [OK]

Hint: CalculatePath and check PathComplete before SetDestination [OK]

Common Mistakes:

• Calling SetDestination before checking path validity
• Ignoring path.status or checking wrong status
• Confusing CalculatePath and SetDestination roles