v50 Steam/Premium information for editors
- v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
- Use this page to report any issues related to the migration.
This notice may be cached—the current version can be found here.
Editing 23a:Path
Jump to navigation
Jump to search
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
You are editing a page for an older version of Dwarf Fortress ("Main" is the current version, not "23a"). Please make sure you intend to do this. If you are here by mistake, see the current page instead.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 3: | Line 3: | ||
The term '''Path''', or '''Pathing''', is used in Fortress Mode to refer to the game process of determining how and where dwarves and other creatures will get from one place to another, to fulfill their various personal tasks and priorities. The game code attempts to send them on the shortest, quickest route possible, their "path". This may change with every step, and in fact the game checks and rechecks each creature's path many, many times as they proceed. If a dwarf needs to move down a hall, they "path" down that hall. If some other dwarves are coming the other way, each one paths to avoid the other if possible. If the hall is too crowded, a dwarf might decide it's faster (at that moment) to path down a different hall, and take a longer way around. If a large hall is very crowded, each creature in that hall constantly changes their pathing as the others do as well. | The term '''Path''', or '''Pathing''', is used in Fortress Mode to refer to the game process of determining how and where dwarves and other creatures will get from one place to another, to fulfill their various personal tasks and priorities. The game code attempts to send them on the shortest, quickest route possible, their "path". This may change with every step, and in fact the game checks and rechecks each creature's path many, many times as they proceed. If a dwarf needs to move down a hall, they "path" down that hall. If some other dwarves are coming the other way, each one paths to avoid the other if possible. If the hall is too crowded, a dwarf might decide it's faster (at that moment) to path down a different hall, and take a longer way around. If a large hall is very crowded, each creature in that hall constantly changes their pathing as the others do as well. | ||
| − | Pathing | + | Pathing has a serious affect on [[Maximizing framerate|'''framerate''']], or "frames per second" (fps), the speed at which the game advances. The more creatures on the map, the more units that need to figure out how to they'll move around, the slower the framerate goes (though this may not be noticeable or a concern on more powerful computers). |
| − | Both [[flood]]s and anti-floods (triggered when opening or closing [[floodgate]]s next to filled [[channel]]s) perform their own simple pathfinding, and while it is simpler, it is much more resource-intensive as it will recalculate | + | Both [[flood]]s and anti-floods (triggered when opening or closing [[floodgate]]s next to filled [[channel]]s) perform their own simple pathfinding, and while it is simpler, it is much more resource-intensive as it will recalculate pathfinding for the entire map every time the liquids move, causing significant lag until they settle. |
If a dwarf refuses to fulfill a job, simply standing in place, often a lack of path is the problem. Forbidden [[door]]s, [[cave-in]]s, or orders to construct [[bridge]]s that are designated to operate from the ''far'' side of the [[chasm]] are all common pathing deal-breakers. | If a dwarf refuses to fulfill a job, simply standing in place, often a lack of path is the problem. Forbidden [[door]]s, [[cave-in]]s, or orders to construct [[bridge]]s that are designated to operate from the ''far'' side of the [[chasm]] are all common pathing deal-breakers. | ||
Determining the "nearest object" doesn't use the same path finding logic, but simply counts how many steps the dwarf would need to take if there we no walls present. Since creatures do not move diagonally, a stone 3 tiles to the west and 4 tiles to the north would be considered to be 7 blocks away. | Determining the "nearest object" doesn't use the same path finding logic, but simply counts how many steps the dwarf would need to take if there we no walls present. Since creatures do not move diagonally, a stone 3 tiles to the west and 4 tiles to the north would be considered to be 7 blocks away. | ||