I`m working on some basic pathfinding in 3D space. I`m able to create a navigation graph, using a flood-fill algorithm. I start in one point, and extend it in 4 directions, if there are no colliders in that particular direction. It`s pretty nice until now. Works ok. Creates a nice grid, without the inaccessible nodes or edges. But there`s one more thing i have to do in order to make enemies / NPCs come to the player or go to a certain place.
Use A* to find the shortest path from a node closest to the enemy to a node closest to the target.
I studied A* 1-2 years ago in college, gotta read a bit more about it though, to refresh my memory. But still, which heuristic is the most suitable here?
Is it ok if i use the straight distance between 2 points? And the cost being the number of graph edges traveled until the current position? (since each edge has the same length.)
And is there anything else i should need to know about this? Im gonna look into it today, but a direction, for a head start, would be really, really nice.
What heuristic should i use for A* ?
Yeah... in a grid world, you are pretty well off just using the straight line distance. Also, if you can't move diagonally, you can use the Manhattan distance which is simply delta x + delta y. As long as your heuristic is no greater than the absolute minimum number of moves, you're good.
If I have two admissible heuristics (less than the true cost), does using the more detailed heuristic (absolute distance) provide any benefit over the coarser heuristic (manhattan distance)? The more detailed heuristic returns different results when the coarser heuristic returns the same results.
If I have two admissible heuristics (less than the true cost), does using the more detailed heuristic (absolute distance) provide any benefit over the coarser heuristic (manhattan distance)? The more detailed heuristic returns different results when the coarser heuristic returns the same results.
In a grid world without diagonal move, Manhattan distance is more accurate than Euclidean distance.
The better is your heuristic, the less node you may expect to visit.
An other thing with heuristic is how it breaks tie which can favour some (equivalent) path from other.
Euclidean Distance will favour path along the straight line.
The better is your heuristic, the less node you may expect to visit.
Correct. For grids, Manhattan distance is OK if diagonal moves are not allowed. Otherwise, I'd use Octile Distance.
An other thing with heuristic is how it breaks tie which can favour some (equivalent) path from other.
Euclidean Distance will favour path along the straight line.
[/quote]
I don't see how. Unless you program A* to break ties in favour of the path with the fewest turns? At any rate, this isn't a good approach. Normally ties should be broken in favour of the node with the larger g value. Otherwise A* can expand an awful lot of extra states. See Figure 1 in this article for an example.
If I have two admissible heuristics (less than the true cost), does using the more detailed heuristic (absolute distance) provide any benefit over the coarser heuristic (manhattan distance)? The more detailed heuristic returns different results when the coarser heuristic returns the same results.
The key is to use the best heuristic that doesn't overestimate the actual cost. If your heuristic tends to drastically underestimate you can end up expanding tons of useless nodes, so the closer your heuristic to the actual cost, the faster A* might find your solution.
You can also overestimate on purpose to get a result faster, but once your heuristic overestimates, you might not get the shortest path. That's not always a real problem, because personally, I had 3 options to walk to work every day and no, I never bothered to find out which one might be a few steps longer. So in some cases overestimating a little can even be a good thing.
You can also overestimate on purpose to get a result faster, but once your heuristic overestimates, you might not get the shortest path. That's not always a real problem, because personally, I had 3 options to walk to work every day and no, I never bothered to find out which one might be a few steps longer. So in some cases overestimating a little can even be a good thing.
This is actually a useful point. People rarely bother with climbing that asymptotic curve to perfection. Eventually we get to "good enough". If you overestimate a little and speed up your search, not too many people are going to notice a slightly sub-optimal result.
When I did the overestimating it made things much faster, but while most paths were fine when I had irregular geometry it could do strange things like hug a wall that was curving AROUND the goal.
For heuristing I was wondering if there's something that takes directionality into account more as I still don't always get the most obvious path for straight line.
For heuristing I was wondering if there's something that takes directionality into account more as I still don't always get the most obvious path for straight line.
When I did the overestimating it made things much faster, but while most paths were fine when I had irregular geometry it could do strange things like hug a wall that was curving AROUND the goal.
For heuristing I was wondering if there's something that takes directionality into account more as I still don't always get the most obvious path for straight line.
Directionality is taken into account when you compare the other values of the potential squares you want to search next. If you move away from the goal, your cost goes up. If you move toward, the cost goes down. All the heuristic represents is a starting point from which to compare the total distances of your future selections. And for distance, no direction is needed.
Thanks for the link. Jump point pruning looks like an interesting technique, though I think the article overstates the benefits slightly. I'll have to try it out if I ever need to use A*.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
