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

[unity_CD7CA852FABD8AADF1FB]

@Aashishsinng

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.

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

[unity_v1SbKQhi831A8A]

What the PlayerManager do???

[adaimmohassine]

i have this problem

[Ayz8]

@br222

Bu hatayı bende de alıyorum. Saatlerce uğraştıktan sonra nihayet ne olduğunu öğrendim.
Bu, düşmanımın devlet makinesi. Düşmanım devriye durumundayken ve etrafta dolaşırken ve oyuncumla buluşup kovalama durumuna geçtiğinde, her şey yolunda. Ancak düşman bir devriye ile diğeri arasında kısa bir mola verdiğinde (ve ajan.enabled = false) ve tam o sırada oyuncum yanından geçiyor, takip durumuna geçiyor ve bu hata oluşuyor.
Ne olduğunu öğrendikten sonra düzeltmek oldukça kolaydır. Düşmanın kovalamaca durumunun ilk satırına agent.enabled = true ekledim ve şimdi her şey yolunda.
İşin zor kısmı, bu hatayı gördüğümde, bunun bir navmesh ajanı ayar hatası olduğunu düşündüm ve hatanın yalnızca oyuncu düşmanın görünüm Yarıçapındayken ve hareket etmiyorken meydana geldiğini fark edene kadar bunun bir durum makinesi hatası olabileceğini hiç düşünmedim. . Bu yüzden, benzer bir durumla karşılaşan insanlara yardımcı olabilir umuduyla yazıyorum.

Thank you my friend

[oscsr]

@Kiwasi

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.

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

[jongning]

@Aashishsinng

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.

Thx That help me alot

[Krugmeisteren]

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

[redders2312]

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.

[Esteban-Gallardo]

@aceghost360

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!!

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

[michelle_sunshine]

@Tornado77

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

solved

[bearcrowstudios]

In my case, I was instantiating a prefab that already had a NavMeshAgent component on it and getting the error even though I was spawning the prefab in the right place. This must have been causing something to initialize in the NavMeshAgent before it was actually placed in the scene, because removing the NavMeshAgent component from my prefab and instead creating the NavMeshAgent in the Start() method of the game object resolved the error for me.

[New_10]

@Aashishsinng

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.

Thankyou broo soo much it finally worked

[YektaOz]

@suleymanbucuk

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.

oh you’re a savior. thank you <3

[Munerato]

I used this code in void update and it worked
if (nav.isActiveAndEnabled)

[Axekick87]

@redders2312

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.

you could try
navMeshAgent.isStopped = true;
i did the same course and this is how i did it

[Mwmny]

I think you haven’t added navmeshagent to your game object or maybe you haven’t enabled this component