Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Gnomechomsky]

The init.txt file says that if you put the "restricted" cost too high, that pathfinding will lag.  I've done some A* implementations, so I understand why that is (dwarves will consider lots of long alternative paths before considering the path through the restricted square).  But this is a relative thing, right?  If my numbers were, say, 10:11:50:250, would it lag any more than the default 1:2:5:25?  I'm thinking no, but can anyone confirm?

The reason I ask is that designating the center of my three-wide hallways to cost 10, while the outside "lanes" cost 11 should make my dwarves stick to the middle for long trips, but not bother if they're going fewer than 10 or so tiles.  If it's set at 1 and 2, then essentially no trip is short enough that the dwarves wouldn't hop to the center lane immediately.

Has anyone tried this?

[Skanky]

If you set the costs to 10 and 11, then they will still go to the middle of the 3-tile hallway for trips longer than 2 steps into that hallway. Any way you look at it, 32<33, so it will always be chosen.

Code: [Select]

D...#
#*..#
#.*.#
#*..#
D...#The pathfinder will always return the path marked with * as the shortest route.

[Gnomechomsky]

Ohh...yeah...a diagonal move doesn't cost sqrt(2) times as much as an orthogonal one, huh?  That does put a crimp in that plan.  Oh, well.

[G-Flex]

Actually, I've heard that toady does implement diagonal movement at around 1.4 times the cost. But I'm not sure.