| Age | Commit message (Collapse) | Author |
|---|
|
path finder costs with tile distances, thus vehicles went to depots which were factor 100 too far away. (juanjo)
|
|
codestyle of derived structs.
|
|
static cast type, operator methods.
|
|
|
|
"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)
|
|
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.
|
|
use it
|
|
functions if they return the Z in pixels (like TilePixelHeight)
|
|
account.
|
|
|
|
performance significantly (about 15%)
|
|
yapf_node_ship.hpp
|
|
|
|
|
|
be lost
|
|
one-way path signals so those aren't preferred over other possibilities
|
|
|
|
|
|
due to bouncing around in an "one way" trap; two one ways pointing towards eachother making it impossible to leave
|
|
|
|
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)
|
|
penalties for road vehicles.
|
|
vehicle speed is meant.
|
|
|
|
some headers
|
|
|
|
|
|
|
|
|
|
|
|
about the fact that the backside of an one-way path signal can be a safe waiting point.
|
|
road stop wasn't a road stop but was a T-junction or turn, the road vehicles would jump around in circles
|
|
|
|
divisions with rounding.
|
|
and DECLARE_ENUM_AS_BIT_SET
|
