| Age | Commit message (Collapse) | Author |
|---|
|
|
|
performance significantly (about 15%)
|
|
yapf_node_ship.hpp
|
|
|
|
|
|
|
|
be lost
|
|
one-way path signals so those aren't preferred over other possibilities
|
|
|
|
provide "lost" notices; it would even get lost while following it's own path
|
|
|
|
due to bouncing around in an "one way" trap; two one ways pointing towards eachother making it impossible to leave
|
|
up as lost, even when it would eventually find a path. Now also the distance from the "end" of the pathfinding run to the destination is compared to the current distance to the destination; if the distance to the destination at the end of the pathfinder run is less than the current distance from the destination the ship won't be marked as lost. This means that the ships with the old pathfinder will less likely get marked as lost, but due to the design of the old ship pathfinder there "lostness" is merely a best guess. When you still get a lost message
|
|
|
|
|
|
penalty when the signal is a path signal.
|
|
road vehicles and trains.
|
|
|
|
|
|
|
|
parameter to "path_found" and remove the ! where the variables are set / read
|
|
|
|
|
|
making sure other waypoint entries are evaluated as well when they are occupied, e.g. when there are no signals before the waypoint but a train just beyond the waypoint is stopped (like for stations)
|
|
depot in some (corner) cases
|
|
penalties for road vehicles.
|
|
vehicle speed is meant.
|
|
|
|
|
|
|
|
OpenListHash data protected, and rename for coding style.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
