Move To Location or Actor Bug
|
Move to Location or Actor fails when the Goal Location is outside the nav mesh, but Use Pathfinding is set to False. The documentation indicates that when Use Pathfinding is False, the AI agent will move in a straight line towards the goal irrespective of the nav mesh. However it is not doing this when the Goal Location is outside the nav mesh. Instead the entire request fails and the agent does not move at all. If the Goal Location is inside the nav mesh, then it works. This contradicts the documentation and the very purpose of Use Pathfinding, which leads me to believe it is a bug. The expected behaviour when Use Pathfinding is set to False is that the AI agent should move in a straight line towards the Goal Location regardless of where said location is, whether it is in the nav mesh or not shouldn't matter.
(comments are locked)
|
|
Thanks for your patience on this one. I was able to reproduce the issue and have entered a bug report. You can track its status using the link below: https://issues.unrealengine.com/issue/UE-51364 Have a great day Awesome! I also met the problem : https://forums.unrealengine.com/development-discussion/content-creation/1420219-moving-ai-to-location-outside-of-navmesh I am glad it will be addressed soon. Moreover... Use Continuous Goal Tracking doesn't seem to do anything, in any context. Is it also bugged? It doesn't work for Locations, yet Actors track continuously anyway. It seems to me like this node, and all Move To nodes are bugged. Both Actor and Location goals should be able to evaluate both as Once or Continuously.
(comments are locked)
|
Follow this question
Once you sign in you will be able to subscribe for any updates here
This problem isn't directly related to 4.18, it is present in all versions from what I can tell.
Hey wilberolive,
Could you provide screenshots of any Behavior Trees, Blueprints, and other assets that are related to this so I can get an idea of what your setup looks like?
Do you have Project Goal Location enabled by chance, or Project Point to Navigation?
Thanks!
Hi Sean, just checking if you've had a chance to see my screen shots yet?
Hi wilberolive,
I've been having a conversation with one of our developers regarding this, and I plan on taking a closer look at it early this week. Thanks for your patience. I'll respond as soon as I have new information.
Thanks Sean. Sorry about the double post. Here is that sample project, just to keep everything together.
Hi Sean,
I'm trying to use the Move To Location or Actor blueprint node, which provides both an On Request Failed and On Move Finished output pin. I need to use this one so that I know when the move is complete.
Here is how I have it set up. There are no options for Project Goal Location or Project Point to Navigation. That is probably what this node needs to fix the problem as it is probably doing that by default even when Use Pathfinding is disabled like I have it.
To get around the issue for now, I've resorted to using the Move to Location node. Unfortunately, this node doesn't tell you when the move is finished so I've had to rely on a hack delay node until this gets fixed.
To fix the problem, the Move To Location or Actor node either needs to ignore the nav mesh when Use Pathfinding is disabled (as indicated by the docs) or it needs a Project Destination to Navigation option like Move to Location does.
I got stuck on this very same bug too. Unfortunately as of today (27 nov 2018) it's still open, there's a pull request pending here: https://github.com/EpicGames/UnrealEngine/pull/5293