Pro version 3.2 vs earlier non-pro (3.1.1)

General
1

I’ve been trying to switch over to the pro version, but I’m getting all kinds of weird behaviour now.

In the earlier version, I had a character that would move towards a waypoint, and when she got near, the waypoint would move, so she’d have to keep going. In this version, the character would never stop when planning the next one, just keep going. And if she needed to go back the way she came, she’d sort of do a u-turn - therefore always moving forward even while turning.

In the pro version, this character has become super jerky with her movements. Throughout the whole path towards a waypoint, she keeps flipping back and forth and can’t seem to smooth out her walk. Then, when she hits the end reach distance, she stops and waits for a new path. And if the new path needs her to go back the way she came, she rotates on the spot instead of moving forward.

I really like the old behaviour much better - it looks a lot more natural, as the character is running and unlikely to stop to turn. But, I can’t figure out what has changed between the two that is causing the new behaviour. It seems like it should still be the same as the old.

2

Hi

First, make sure you are using AIPath instead of AIFollow.
Also, make sure the Next Waypoint Distance is correctly set.

3

I’ve checked those. I’m using the exact same set of values in both scenes, just getting extremely different behaviour. I’ve also tried using the RVO vs the character controller, and both produce bad behaviour.

However, it’s definitely worse using the RVO. When the character has the RVO on, when walking a relatively straight path, she look side to side constantly, so that she ends up more on a zig-zag path. With the character controller, she at least moves mostly straight, but still stops when she hits the end.

4

Maybe you should lower the endReachedDistance value? That might get the behavior you are looking for.

5

Hmm… I really can’t figure out what’s going on, but I’ve “solved” it for now by changing a little bit of the code in AIPath. Specifically, in CalculateVelocity:

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

//Send a move request, this ensures gravity is applied
if (!tagPlayer) 
	return Vector3.zero;

}`

So, for now, the player keeps moving on the original path, but the target gets moved and they replan to the new target without stopping.