1. Help us improve the editor usability and artist workflows. Join our discussion to provide your feedback.
    Dismiss Notice
  2. We're looking for feedback on Unity Starter Kits! Let us know what you’d like.
    Dismiss Notice
  3. We’re giving 2017.1 beta testers a chance to win t-shirts and a Nintendo Switch. Read more on the blog.
    Dismiss Notice
  4. We want to know how you learned Unity! Help us by taking this quick survey and have a chance at a $25 gift card
    Dismiss Notice
  5. Are you an artist or level designer going to Unite Europe? Join our roundtables there to discuss artist features.
    Dismiss Notice
  6. Unity 5.6 is now released.
    Dismiss Notice
  7. Check out all the fixes for 5.6 on the patch releases page.
    Dismiss Notice

Calling NavMeshAgent.SetDestination in Update() stops stoppingDistance working?

Discussion in 'Scripting' started by yezzer, Apr 28, 2012.

  1. yezzer

    yezzer

    Joined:
    Oct 30, 2009
    Posts:
    132
    Simple example:
    Works correctly:
    - User clicks, agent.SetDestination(somePosition) is called.
    - Agent navigates to destination, and stoppingDistance is used.

    Does not work correctly:
    - on Update(), agent.SetDestination(somePosition) is called.
    - Agent navigates to destination, stoppingDistance is disregarded.

    Is this in fact the correct behaviour, or should I file a bug report? If it's the correct behaviour, I think it should be noted in the docs.

    It's sort of mentioned here, and AngryAnt responds with:

    FWIW, I'll do some variation of this. I was aware what I was doing was inefficient, but intended to deal with that later.