I have a behaviour tree for a simple AI that wanders around. The b-tree is attached to an AIController with a PawnSensing Component. When the pawn sees the player, it raises a flag that it has seen the player. From there, the B-Tree takes over. Now, when I set a random wander point in a sequence followed by a MoveTo, it works flawlessly. However, when I seek the player position, and call Move To, it fires each one off right after another (everytime) and does not move the bot. Here are some frames of the tree working (wandering), then not working (seeking player). As well as the Seek Player task (to note: I set the Z because in another question I read, it may be out of bounds, which this was (Z:149 - why, I don’t know, I didn’t make the player scripts).
The z value you’ve done probably won’t work as it is a world value and it needs to be your location, I’ve had problems like this with my characters being taller than the AI enemy characters and somehow effects the navmesh. What I did that worked for me is, my z location -120 (the height difference between characters enemy AI 1.8m my character 3m)
Let me know if this works for you, I’ve asked this question before and nobody else had this problem
Cheers
Just to make sure, You added a navigation mesh to your level right? and when you press “P”, does it appear as green? Also make sure the navigation mesh is tall enough. Make sure you don’t forget to rebuild pathing, this will prevent the character from being able to move
Yes, there is a navigation. And yes, it shows as green when I turn on the navigation mesh view.
Also, when I use move to for the wandering, it works seamlessly.
So rather then getting the player location (in world space), break vector, set world z to 30 (same as find random point in radius for the perfectly working random wandering) I should subtract 120 from the z and make vector again?
In practice you should just use PlayerPawn’s location, without any Z-alteration. You might want to extent default navigation query extent - you can do that via NavigationSystem.SupportedAgents in your project’s setting.
I only resorted to the z-alteration due to this issue, as it was happening before without any alteration. The reason behind this was to maintain bounds in the nav mesh bounding volume. I will look into the navigation query extent to see if that does actually fix the issue.
