| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
penalties differ.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Road vehicles shouldn't reverse all of a sudden.
|
|
the cost of a path exceeds max. penalty.
|
|
when the cost of a path exceeds max. penalty.
|
|
reverse.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
function.
|
|
|
|
|
|
Given any speed issue cannot be attributed to checking for _debug_NNN_level, removing this is a safe action
This fixes #6652.
|
|
when trying to find any safe position.
|
|
bug about never used NPF_FLAG_IGNORE_RESERVED flag
|
|
|
|
|
|
meant the same thing, but only one was used. Keep PATH_TOO_LONG since it has the better documentation.
|
|
waiting position from a waypoint.
|
|
finding code and remove need to return fake path distance. (juanjo)
|
|
too long condition, as destination should not be considered in the former case.
|
|
path and applying penalty.
|
|
integers.
|
|
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
|
