When running the beginning tutorial, it doesn't run as expected

Beginner Questions
1

I’m hoping to get some help. I’ve found the tutorial very helpful, but I can’t seem to get the polish on this that I’d like. I believe I’m using the exact code from the example.

  1. My object moves towards the target great, getting around obstacles until it’s almost there. At about the last 10-20% of it’s trip, it begins to really stutter and jump around. As near as I can tell it’s a combination of not being able to find a new path and not knowing that it’s close to reaching the end of it’s path.
  2. I never see the green line as specified in the tutorial. This is despite disabling the 3d Gizmos setting as recommended

My code is below. I’m happy to post any additional details and/or help to get this tutorial more polished! I’m using the latest version of Unity. Thanks!

`
using UnityEngine;
using System.Collections;
//Note this line, if it is left out, the script won’t know that the class ‘Path’ exists and it will throw compiler errors
//This line should always be present at the top of scripts which use pathfinding
using Pathfinding;

public class AstarAI : MonoBehaviour
{
//The point to move to
public Vector3 targetPosition;

private Seeker seeker;
private CharacterController controller;

//The calculated path
public Path path;

//The AI's speed per second
public float speed = 100;

//The max distance from the AI to a waypoint for it to continue to the next waypoint
public float nextWaypointDistance = 3;

//The waypoint we are currently moving towards
private int currentWaypoint = 0;

public float repathRate = 0.5f;
private float lastRepath = -9999;

public void Start()
{
    seeker = GetComponent<Seeker>();
    controller = GetComponent<CharacterController>();
}

public void OnPathComplete(Path p)
{
    p.Claim(this);
    if (!p.error)
    {
        if (path != null) path.Release(this);
        path = p;
        //Reset the waypoint counter
        currentWaypoint = 0;
    }
    else
    {
        p.Release(this);
        Debug.Log("Oh noes, the target was not reachable: " + p.errorLog);
    }
}

public void Update()
{
    if (Time.time - lastRepath > repathRate && seeker.IsDone())
    {
        lastRepath = Time.time + Random.value * repathRate * 0.5f;
        seeker.StartPath(transform.position, targetPosition, OnPathComplete);
    }

    if (path == null)  //We have no path to move after yet
    {          
        return;
    }

    if (currentWaypoint > path.vectorPath.Count)
    {
        return;
    }
    if (currentWaypoint == path.vectorPath.Count)
    {
        Debug.Log("End Of Path Reached");
        currentWaypoint++;
        return;
    }

    //Direction to the next waypoint
    Vector3 dir = (path.vectorPath[currentWaypoint] - transform.position).normalized;
    dir *= speed;
    controller.SimpleMove(dir);

    if ((transform.position - path.vectorPath[currentWaypoint]).sqrMagnitude < nextWaypointDistance * nextWaypointDistance)
    {
        currentWaypoint++;
        return;
    }
}

}`

2

Hi

Due to the high speed of your agent (at least with the default settings).
This is a combination of

  1. You are doing the check for if the next target point is close enough after the movement code. Preferably, it should be placed before it and also do a while loop instead of a for loop (maybe this is not the same as in the get started tut. I will have to update it then).
  2. The movement direction could be much larger than the actual distance it needs to cover. Consider using Vector3.ClampMagniture (…, 1) instead of using .normalized. This will give it a nice slowdown at the end of the path.
3

I’ve solved this problem by expanded in the on target reached conditions in AIPath.

`
if (currentWaypointIndex == vPath.Count-1 && (targetDist <= endReachedDistance || (oldTDist != -1 && oldTDist < targetDist))) {
if (!targetReached) {
targetReached = true;
oldTDist = -1;
OnTargetReached ();
}

    //Send a move request, this ensures gravity is applied
    //return Vector3.zero;

    return transform.forward;

} `

Usually once your character starts ‘spinning’ near the target, s/he will end up both closer and farther away from the target during spin. So I’m checking for that. Instead of just the old condition, I’m also making sure that we’re still getting closer to the target the whole time. If we start moving away, I assume I’ve reached it and am going to start spinning, so call target reached.

I set oldTDist after this if-statement to targetDist. I reset oldTDist to -1 each time currentWaypointIndex is incremented (look for currentWaypointIndex++).

Also, if you change return Vector3.zero; to the return transform.forward; line I have there, the character will continue to move forward (which is usually pretty much towards the target, because he hasn’t had a chance to spin much) while it searches for new path. This prevents it from having to wait for the new path to be decided before moving.

4

Sorry for the delay, but thanks for the feedback. Akajb: I don’t quite understand how your code fits into the sample I have above. Can you please provide a little extra context? Does it replace the “if (currentWaypoint == path.vectorPath.Count)” line?