Hi

Im using an A-star algorithm for pathfinding for my units in my rts game. I didnt make the a-star code myself but rather a wrapper around some code i found. I want to add a cost for turning (changing direction between to nodes) so the pather will prefer to make straighter paths instead of zigzagging.

Example:
Units can move in 8 directions between the tiles. When moving NNW (direction 1/16th or 1.30 a'clock) it prefers to go up, up-right, up, up-right (turning 1/8th each tile) instead of going all up it needs, turn once, and then go the rest up-right.

Best way to solve this?

Thanks

Erik

Alvaro has the right of it for true turning costs, though I think he may just want to prevent zigzagging, so you could alter the F cost to make it more expensive to move to a node if it involves moving in a different direction than the last move. Maybe store the dx/dy for each move, then compare it to the new potential, and roll it into the F cost?

(Also, if you haven't done so already, you may be able to fix your problem by just making diagonal moves more expensive that straight moves, check this thread for more info)

my diagonal cost is quareroot of 2 already. tried to put this to 1.5 to see what happens but it doesnt change the zigzagging. I dont need true turn-cost, just avoid the worst zigzagging.

Ill look into your suggestions! Any good examples of this would be most appreciated!

Thanks
Erik

but cannot you use adjacent cost? I mean the cost to move from a node to all 8 around it?

I think my a-star works like that. (since it knows that diagonal is more expensive this is a relationship, no single node is "diagonal" in itself, its diagonal in relation to which node is investigating it)

Alvaro has the right of it for true turning costs, though I think he may just want to prevent zigzagging, so you could alter the F cost to make it more expensive to move to a node if it involves moving in a different direction than the last move. Maybe store the dx/dy for each move, then compare it to the new potential, and roll it into the F cost?

No, if nodes represent locations they "forget" the direction of the last move. The cost of leaving the node is the same for every path through it. Only nodes representing position and direction can distinguish turning from straight movement.

In my data representation, each potential move keeps a link to the previous move, so it's just a matter of looking at the previous move, look at it's dy/dx compared to the current tile, compare it to the new potential move's dy/dx from the current tile. It would basically mean that the search would tend to favor tiles "in front" over tiles to the side.

You're right in that it's just altering search order though, so I'm not sure how helpful it would be to implement it that way.