Search Unity

  1. Unity 2018.3 is now released.
    Dismiss Notice
  2. The Unity Pro & Visual Studio Professional Bundle gives you the tools you need to develop faster & collaborate more efficiently. Learn more.
    Dismiss Notice
  3. We've updated our Terms of Service. Please read our blog post from Unity CTO and Co-Founder Joachim Ante here
    Dismiss Notice
  4. Want to provide direct feedback to the Unity team? Join the Unity Advisory Panel.
    Dismiss Notice
  5. Improve your Unity skills with a certified instructor in a private, interactive classroom. Watch the overview now.
    Dismiss Notice

Navigation/Navmesh - Failed to create agent because it is not close enough to the Navmesh

Discussion in 'Documentation' started by phxtr, Oct 21, 2017.

  1. phxtr


    Jul 8, 2017
    I had a working project, and made some customization and all of a sudden started getting the above error.

    I lost nearly a whole day troubleshooting this issue, rebaking the navmesh, redoing the agent settings, adding debug code, reading pages and pages of unity docs, as well as google results, etc. etc. Only to find out the error was 'expected'.

    I finally got lucky and found the solution in this thread here:

    The 'problem' was that I had added a new agent type. The procedure/interface was just like adding a new type for everything else (tags, layers, etc), so I never realized additional steps were required to make a new agent type work.

    Nothing in the documentation stated that the standard Navmesh is ONLY for the 'Humanoid' agent, and that adding a new type requires extra procedures.

    Could you modify the Navigation pages to mention this fact? Somewhere in the more general sections that people are more likely to see, and not buried somewhere preferably, 8^).

    Would possibly save a lot of people a lot of headache and lost time troubleshooting something that could be avoided with a quick mention in the documentation.
    Skyho, itsarjunsinh, TobiasW and 3 others like this.
  2. trinistry


    Feb 2, 2014
    The internet needs more heroes like you! Thank you for posting that here. There is no indication what so ever, why the agent would refuse to be on a NavMesh, when it is a custom agent type.
    Berillium and Frable like this.
  3. Frable


    Nov 14, 2014
    @phxtr Huge thank you from my side as well.
    Ran into the exact same issue and of course wasted lot of time to recheck various aspects.
    Never imagined that this might be the root cause for the problem.
    Changing to the default "humanoid" agent type made it work without a hitch.
    Berillium likes this.
  4. Meany747


    Jun 13, 2017
    Massive thank you here as well, this is fairly poorly noted.
  5. GregoryFenn


    Feb 13, 2018
    I have the same problem and I'm using the only "Humaniod" agent :(