SetDestination can only be called on an active agent that is on a NavMesh

Hello, im trying to make that the enemy is following the player with a script and a Nav mesh agent but its not working i got this error:
SetDestination" can only be called on an active agent that has been placed on a NavMesh.
UnityEngine.AI.NavMeshAgent:SetDestination(Vector3)
EnnemyController:Update() (at Assets/Script/EnnemyController.cs:23)

My script:

Code (CSharp):

1. using System.Collections;
2. using System.Collections.Generic;
3. using UnityEngine;
4. using UnityEngine.AI;
5.  
6. public class EnnemyController : MonoBehaviour {
7.  
8.     public float lookRadius = 10f;
9.  
10.     Transform target;
11.     NavMeshAgent agent;
12.  
13.     void Start () {
14.         target = PlayerManager.instance.player.transform;
15.         agent = GetComponent<NavMeshAgent>();
16.     }
17.  
18.     void Update () {
19.         float distance = Vector3.Distance(target.position, transform.position);
20.  
21.         if (distance <= lookRadius)
22.         {
23.             agent.SetDestination(target.position);
24.         }
25.     }
26.  
27.     void OnDrawGizmosSelected ()
28.     {
29.         Gizmos.color = Color.red;
30.         Gizmos.DrawWireSphere(transform.position, lookRadius);
31.  
32.     }
33. }
34.  

 

Try moving the agent up or down a bit in the scene. Sometimes it doesn't register as on the nav mesh if the position isn't quite right.

 

Im gonna try

 

Not working

 

I found a solution, Window, AI, Navigation, bake, select the floor and then click on bake

 

You told us you already have a NavMesh...

 

Ah yes, not having a nav mesh at all will cause the same issue. I should have mentioned that.

 

Not baking means there is no navmesh. So your problem was actually that you were calling set destination with no navmesh present in the scene

 

I'm still new to Unity, what else can I do to solve these kinds of problem? I tried doing the Window, AI,... solution but it did nothing. I also tried moving the NavMeshAgent up/down in the inspector menu but it shows a window that says 'Cannot restructure prefab instance' : "Children of Prefab instance cannot be..." When I clicked Open Prefab, The inspector only showed the Transform and Animator. It did not show the NavMeshAgent nor the Script. Please help me

 

You must edit the prefab in order to make those changes, Click on the prefab and edit it.

 

For me, it solved by this:
Maybe the person is a prefab and you are instantiating at runtime. This way, **Reset the Transform** of the prefab in such a way that he is touching the ground. Whether or not a person is a prefab, His **X,Y,Z of transform should be in such a way that his feet touching the ground**.

 

Another solution for this problem,

Your object's capsule collider's radius / height and the navmesh agent's collider's radius / height has to match.

For example my enemy' s capsule collider's radius was 39 and height was 223. Nav Mesh Agent's radius was 0,5 and height was 2,0 so always got an error such as SetDestination" can only be called on an active agent that has been placed on a NavMesh. After i changed nav mesh agent's radius and height to my enemy object' s collider values, everything worked perfectly.

 

This will also happen if the agent is placed on a navmesh that has a different agent type than the agent itself

 

Thanks for the fix. I started with a modular scene and the instantiate to spawn points worked fine.(2018.4.13f1) Once I changed to a terrain, the spawn still worked but the enemies could not see the player and did not move. The fix was to add the prefabs back to the new terrain and create new prefabs (deleted the original prefabs). Of course I had to attach the new prefabs to the object references in the inspector since using [serialized fields].

 

That was our problem.
Any specific steps to take to fix this?
I haven't been able to figure out how to create separate NavMesh in one scene? That was our original goal. It used to be done using the "NavMeshSurface" component on an Empty GameObject. You could have two or three of these in your scene.

Now though, it is a Navigation panel that seems to be one single NavMesh for the entire scene. Yet that means only one type of enemy can use the NavMesh and the others say there is no NavMesh at all.

 

problem fixed here :

 

I have done everything listed above but it still does not work, I have the same script as Tornado77, I have a NavMesh set on the floor of my scene, my character is touching the ground, my capsule collider's radius is the same as the height of my navmesh agent's collider's radius. What can Id do to fix this? (I also have the error: "Failed to create agent because it is not close enough to the NavMesh")

 

It worked!

 

You watched the brackeys video didn't you. I did as well and am having the same problem. Maybe that was only for an old version of unity.

 

to anyone coming here in the future make the platform static and then bake the navmesh, you should be able to see bluish path in the scene.

 

it worked when i click on bake.
thanks

 

None of these have worked for me. I've baked the navmesh multiple times and it's always clearly visible. My character is definitely intersecting with the navmesh. I've gone through all my Agent Types. Radius is at 0.5. Strange thing is that it was working 24 hours ago for me.

 

Worked...

 

i checked static and worked for me

 

For those who watched Brackeys tutorial and still struggle: The first comment under the video rescued me!

it says the following:

For anyone that doesn't have "NavMeshSurface": A) don't download the script from github, that's just nasty. B) Assuming you have all the right components (NavMeshAgent, Walls and something to walk on). Next, in the toolbar, click on Window > AI > Navigation. this will open up a new tool. Click on Object (in the new tool window) and select the surface in the scene. Check Navigation static and make sure "Walkable" is selected for the 'Navigation Area' drop-down. Now click on the walls in your scene, check static and change to Not Walkable. Now go to the "Bake" tab, on the left of 'Object' and click bake. If your Agent is clipping through the walls, you can always increase "Agent Radius" in the Bake Tab.

 

yesss it worked !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

 

Yup it works

 

About this problem, this is not exactly the topic, but I think it is worth mentioning, I had the same error message, but I was instantiating an enemy with the NavMeshAgent already set, and it caused this error, I just had to enable the component by the inspector that already corrected, but I needed to solve it without doing this way, so the viable solution was to check if you have the NavMeshAgent on the enemy, destroy it, Create another identity at runtime, but Disabled, make an Invoke of 1s more or less to enable the NavMeshAgent again and setting the DESTINATION of the component, this solves the problem and without errors.

I hope I helped someone.

 

Another thing that can mess it up, is you're testing something with dynamic nav meshes instead of the baked ones... make sure you're always accounting for the fact that generating that mesh takes a tiny bit of time at start up so don't be running any agents commands before it's ready.

 

I have this error as well. After hours of struggling I finally found out what happened.
It's my enemy's state machine. When my enemy is in patrol state and moving around, and he meets my player and change into chase state, everything's fine. But when the enemy is taking a short break between one patrol and another (and he's agent.enabled = false) and just at that time my player passing by, he changes into the chase state and this error occurs.
After finding out what happened, it's quite easy to fix. I added agent.enabled = true in the first line of the enemy's chase state, and everything is fine now.
The tricky part is when I saw this error, I thought it's a navmesh agent setting error and never thought it might be a state machine bug until I happened to notice that the error only occurs when the player is in the enemy's lookRadius and he's not moving. So I write it down hoping can help people who meet a similar situation.

 

Okay guys... Figured it Out!!!!
I used a script to instantiate the navMesh agent and thet is how i got the error

"SetDestination" can only be called on an active agent that has been placed on a NavMesh."

The whole problem was not in the navMeshAgent Component but was actually in the Instantiate component.
The reason the error occurred was since the Instantiate method i used was

"public static Object Instantiate(Object original, Transform parent);"

Since I just entered a transform component as a parameter it didn't do anything to the spawn position.

So use this Instantiate Method when spawning a navMeshAgent:

"public static Object Instantiate(Object original, Vector3 position, Quaternion rotation);"

Hope You Found This Helpful!!

 

THANK YOU!!!!!!!!

 

I have the most simple code and it does not work, no matter what I try... why does life hate me so much? Everything is setup, I have a blue navmesh, everything static, a navmeshagent, touching the navmesh.....

Code (CSharp):

1. using System.Collections;
2. using System.Collections.Generic;
3. using UnityEngine;
4. using UnityEngine.AI;
5.  
6. public class EnemyManager : MonoBehaviour
7. {
8.     [SerializeField] NavMeshAgent agent;
9.     [SerializeField] GameObject target;
10.  
11.     private void Update()
12.     {
13.         agent.SetDestination(target.transform.position);
14.     }
15. }

 

My problem was that I was instantiating a prefab and then referencing the prefab instead of the instantiated object.

You can save the reference to the cloned instantiated object like so:

subjectObject = Instantiate(currentSubject, new Vector3(-0.18f, 0f, -1.01f), Quaternion.identity);

and use it later.

 

For me https://answers.unity.com/questions/507534/setdestination-can-only-be-called-on-an-active-age-1.html this asnwer helped me.

Code (CSharp):

1.  
2. if (MyNavMeshAgent.isOnNavMesh == false)
3. {                  
4.        MyNavMeshAgent.Warp(NavMeshDestinationTarget.position);
5. }
6.  
7. MyTargetNavMeshAgent.SetDestination(NavMeshDestinationTarget.position);
8.  

 

Thankie

 

Just to reiterate to any future people needing help because I missed this and wasted an extra 15 minutes:

The "Bake" fix works, but you need to make sure your ground mesh has the "Static" box ticked ON before baking it. If you try to bake the ground and no blue overlay displays, it's probably because the "Static" box is not ticked. Tick that on, bake the mesh, and your error should be solved.

 

Hi do you know how to do it if it is for a generic agent instead of humanoid?

 

if u use a humanoid navmesh agent, this means that your agent's shape is like a cylinder. then u should use capsule collider instead of box collider etc. In addition to that, you should be careful about the size of your collider and agent.

 

For me, it's select the corresponding AgentType for NavmeshAgent and NavMeshSurface.
eg. Dont select AgentType Humanoid on NavmeshAgent, and select some other AgentType of NavMeshSurface.

 

YOU ARE ACTUALLY THE MESSIAH! I'VE BEEN SPENDING SO LONG TRYING TO DO THIS AND YOU FIXED IT

 

What the PlayerManager do???

 

i have this problem

 

Thank you my friend

 

although this wasnt the issue that OP was having, it helped me so thank you.

 

Thx That help me alot

 

I had a similar problem and also solved it by updating the NavMesh agent type area masks.

 

Hi, i've had similar problems after doing the zombie FPS course from gamedevtv on Udemy. Similar issue I think to br222. When my last shot that killed the zombie happens, the game broke with the same error. The navMeshAgent.enabled is set to = false which is good to stop the zombie continuing to move but there were other calls continuing in EngageTarget() then ChaseTarget() and that kind of thing. Was actually a really easy fix and all i had to do was add a line to say isProvoked = false as then EngageTarget() stops being called.

 

This one worked for me in Unity 2022.3.2f1 LTS. Thank you!!

 

solved