| Age | Commit message (Collapse) | Author |
|---|
|
path finder costs with tile distances, thus vehicles went to depots which were factor 100 too far away. (juanjo)
|
|
segments with different railtype in the YAPF cache. (JGR)
|
|
codestyle of derived structs.
|
|
static cast type, operator methods.
|
|
|
|
depots when the following tile has the right type to run on, but could not be entered; e.g. facing toward a depot with the entry facing the wrong way failed to reverse whereas facing towards an empty tile allowed the vehicle to reverse (estys)
|
|
"unsafe" functions to prevent them from being used, and thus having to care about certain aspects of their return values
|
|
|
|
|
|
|
|
|
|
would make the end-of-line-is-red setting ineffective
|
|
|
|
direction; now favour docking in the direction you approached
|
|
|
|
Eagle_rainbow)
|
|
railroad checks. (Juanjo)
|
|
|
|
shall leave depots towards north or south.
|
|
|
|
|
|
others were still regular inline), but make sure inline is always a 'forced' inline (I am looking at you MSVC)
|
|
partially reserved rail station could fail.
|
|
comments in the code. It was silly to name me like that to begin with ;) (based on patch by HackaLittleBit)
|
|
use it
|
|
functions if they return the Z in pixels (like TilePixelHeight)
|
|
|
|
overflow of the argument to malloc. (monoid)
|
|
account.
|
|
|
|
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
|
