Apparently Bort is on top of it:
Originally posted by Bort
Good news is that somebody made an actual good suggestion on a fix for running pathfinding. I'm working with it right now in testing.
It's basically a double pass on the "best path" algorithm: one with a long vision distance for a general "avoidance vector" and one with a short, 3-5 yard distance for a "juke vector." Add 'em together, with the juke vector at a stronger strength than the avoidance vector, and it seems to get a pretty good path that really takes the runner's vision into account quite well.
Awesome!
Originally posted by Bort
Good news is that somebody made an actual good suggestion on a fix for running pathfinding. I'm working with it right now in testing.
It's basically a double pass on the "best path" algorithm: one with a long vision distance for a general "avoidance vector" and one with a short, 3-5 yard distance for a "juke vector." Add 'em together, with the juke vector at a stronger strength than the avoidance vector, and it seems to get a pretty good path that really takes the runner's vision into account quite well.
Awesome!






























