One-way differing landscape costs

Here’s a scenario:

Let’s say I had some hilly terrain.

It takes longer to climb uphill but it’s faster to run downhill.

How can the pathfinding engine be made to understand this subtle difference and use the slope of the terrain in its calculations?

Hi

This is not possible using this package at the moment. All connection costs (except manually added ones) are assumed to be the same in both directions.

It is possible to penalize walking on slopes, though. (see RuleAnglePenalty - A* Pathfinding Project)

1 Like