Jump to content
  • Advertisement
Sign in to follow this  
BUnzaga

Nearest node to START, but in the direction of GOAL?

This topic is 2029 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I have a grid of nodes, which contain a list of neighbor nodes.  I wanted to create a FindPath function, with a Start position and a Goal position (both 3d Vectors, using X and Z, UP is 0).  I can easily get the nearest node to start, and the nearest node to goal, but I wanted to also make sure these nodes are in the direction the unit would be travelling.

 

For example, I don't want the unit to go AWAY from the goal, and then back track toward the goal, because the 'nearest' node to him was behind him.  I'll supply a picture to make more sense.

 

properPath.png

 

So in this picture, you can see the 'nearest' nodes to start and goal are where the red X's are.  Start is where the spider is located, and goal is where the black arrow is pointing.  You can see, the nearest start node, is actually in the other direction of the goal, where the yellow circled one is in the direction of the goal, even though it is further than the 'nearest' one.  The same goes for the nearest goal node.

 

I may be making this harder than it needs to be, but I can't seem to figure out the proper maths involved to get the nodes circled in yellow as 'start' and 'goal' nodes.

 

Here are the things I know:

 

startVector

goalVector

distanceFromStartToGoal

 

I need to use this information, while iterating throughout the list of nodes to determine:

 

startNode

goalNode

 

While iterating, I can figure out:

 

nodeDistanceToGoal

nodeDistanceToStart

 

So using all this information, I need to determine nearest node to startVector and the nearest node to goalVector, which are also in the direction from start to goal.

 

Any ideas?

Share this post


Link to post
Share on other sites
Advertisement

Don't move towards the nearest node at the beginning. Just start the pathfinding from that node, move towards the next node instead.

 

If the nearest node IS the goal, obviously you have to move there though ;)

Share this post


Link to post
Share on other sites
I deal with a similar case by creating temporary nodes at the start and end positions, linking to all the surrounding nodes, then path-finding as normal.

The direction of the goal isn't necessarily the way you need to travel if an obstacle is in the way.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!