5.6. Is "Move To" in a State Tree Broken

Development Programming & Scripting Blueprint
1

Hi All

Just toying around with building a simple state tree. I just want to get my character to move using the basic inbuilt “Move to” functionality.

I’ve got it all setup correctly as an AI and hooked up to a state tree.

I have one task that fires and gets a random location, which is then fed into the build in Move To, however my AI does not move. Instead it constantly tries to get new potential location with no movement at all.

It is constantly triggering ‘State Failed’. At first i thought it was just my scene, but i built another from scratch and have the same problem.

I’m hoping i’m just an idiot and missed a step, rather than it being broken, but thought I’d check first.

Thanks

2

Check NavMesh

Check that your AI is set to Auto Possess AI “Placed in World or Spawned“

Check that the random point is reachable

Also, you can debug AI using Show>Developer>AI Debug

3

Nothing unusual appearing in any of these.

Nav Mesh exists and is in the whole radius

Ai possesses correctly

The location is reachable

Nothing strange in the debug.

Its just a constant return of state failed

Unreal State Tree 1
Unreal State Tree 11915×1035 109 KB

Unreal State Tree 2.PNG
Unreal State Tree 2.PNG1833×885 100 KB

4

Is this box your AI? Does it have collision and check if it’s affect navigation set to false

5

It is a temporary one I am using as it wasn’t working on my main AI either.

Collision is on, Affect nav is off

6

image
image1921×925 87.9 KB

7

You are right, it is broken. And personally, I think it’s been broken for a long time. I had a similar problem with the built-in Move To in Behavior Tree. Use custom Task with Move To Location or Actor.

8

Turns out I’m broken.

I added a static mesh of a cube to my character to see what it was doing. For whatever reason this prevents it moving.

Removing the mesh solved the problem

1 Like
9

Also in case Someone is having same issue, just by disabling collision and uncheck “Fill Collision Underneath for Navmesh” on the static mesh componenent because the static mesh will interfere with the navmesh generation.
Actually that was what worked for me.