"Move To" not moving my AI Character to target location.
Hello all. I've spent quite a bit of time here on the forums looking for some assistance and generally I have found what I have needed (thanks for that!). Alas, I seem to be stuck now and have bit the bullet to ask for some help.
I have been following Newton's AI Behaviour and NavMesh tutorial steadily but my AI bot is stubbornly standing still. I have my suspicions of where the problem may be so please bear with me as I try and illustrate my own troubleshooting progress.
To illustrate my problem, here is a screen shot of my BotAITree as it get stucks on the "Move To" instruction:
As you can see, it does hit the "Move To" command but it doesn't have any effect. The update Route also fires, incrementing through the waypoint indices. It then obviously starts again through setting walk speed, finding the route and then attempting a "Move To" again.
I suspect the issue may be caused by UpdateRoute, where I had to override the PerformConditionCheckAI function. Here is a screenshot of my attempt (noting the checked return value):
Here is the event graph of my UpdateRoute. Notice that that I have not connected the node result to the connection. If I do, the return value is never true and so the Move To command is never executed. To get it working, I set the value to succeeded:
Otherwise, I'm fairly sure the rest of my blueprints are correct. I've tried to debug with breakpoints and I'm stuck on the Move To. I would appreciate any help you could offer, as I'm sure there is a little something silly that I've missed (speaking of which, I have check that I have a NavMesh and my target waypoints are in the map). Thanks!
asked Aug 19 '15 at 12:09 AM in Blueprint Scripting
I'm embarrassed to admit that I've woken up this morning and solved the problem. So, it turns out that the placement of the waypoints is extremely important for the bot's navigation. I had them placed above the ground by perhaps 30 or 40 units but still within the navmesh bound box. All I did was move the waypoints down in Z value and now the bot has sprung to life.
I've seen plenty of people on here run into this problem and attempt extremely complicated fixes. Try moving your waypoints down first... just in case :)
answered Aug 19 '15 at 07:57 AM
Follow this question
Once you sign in you will be able to subscribe for any updates here