Checking the output log, I see I’m getting a lot of errors like this:
Destination (XYZ) is outside world bounds. Please clamp your destination within the navigable world or expand world size under settings if necessary.
That sounds bad. Something to do with the World Dimensions of the Don Navigation Manager, maybe?
As for your other points: FlightLocationKey is being set at the beginning of the tree in a service:
Every tick we check to see if some variables have changed, including the player’s position, which is saved as Target Location, which is later used by the Fly To node. I know that part is working because I can see the vector updating at runtime, the Fly To node just doesn’t seem to recognize it.
The Dummy State seems to be working fine too – as soon as the player’s spotted it switches from Patrol to Combat, and it sticks there. (According to the behavior tree panel and a print string.)