1. We've introduced thread tags, search within a thread and similar thread search. Read more here.
    Dismiss Notice
  2. We've released our first Timeline Experimental Preview, our new tool for creating cutscenes and more! To check it out click here.
    Dismiss Notice
  3. All Unity Pro perpetual license customers: your special offer to subscribe is ready! Click here.
    Dismiss Notice
  4. Unity 5.5 is now released.
    Dismiss Notice
  5. Check out all the fixes for 5.5 in patch releases 1 & 2.
    Dismiss Notice
  6. Unity 5.6 beta is now available for download.
    Dismiss Notice
  7. Get prepared for the Tizen Mobile App Incentive Program! Read more about the upcoming program here.
    Dismiss Notice
  8. Enter the Microsoft Developer Challenge for a chance to win prizes. Read more about it here.
    Dismiss Notice

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

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

  1. yezzer


    Oct 30, 2009
    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.