summaryrefslogtreecommitdiff
path: root/src/pathfinder/yapf
AgeCommit message (Collapse)Author
2018-10-31Fix: Protect against a few out of bounds or uninitialised usage errorsCharles Pigott
2018-10-31Doc: Lots and lots of doxymentation fixesCharles Pigott
2018-06-27Codechange: Use HasTrack(dir) to improve code readability.J0anJosep
2018-06-27Codechange: Increase readability of track functions and pathfinders.J0anJosep
2018-04-30Codechange: Use TileAddBy(Diag)Dir when possible.J0anJosep
2018-04-11Remove: NO_DEBUG_MESSAGES was only read and setting it broke compilation (#6703)Patric Stout
Given any speed issue cannot be attributed to checking for _debug_NNN_level, removing this is a safe action This fixes #6652.
2017-08-13(svn r27893) -Codechange: Use fallthrough attribute. (LordAro)frosch
2017-06-22(svn r27885) -Cleanup (r27844): ESR_MAX_COST_EXCEEDED and ESR_PATH_TOO_LONG ↵frosch
meant the same thing, but only one was used. Keep PATH_TOO_LONG since it has the better documentation.
2017-04-04(svn r27846) -Fix [FS#5926]: Infinite loop in pathfinder when checking safe ↵peter1138
waiting position from a waypoint.
2017-04-03(svn r27845) -Change: (Yapf) Use FindDepotData struct to simplify depot ↵peter1138
finding code and remove need to return fake path distance. (juanjo)
2017-04-03(svn r27844) -Change: (Yapf) Treat max cost exceeded separately from path ↵peter1138
too long condition, as destination should not be considered in the former case.
2017-04-03(svn r27843) -Change: (Yapf) Consider depot as destination before reversing ↵peter1138
path and applying penalty.
2016-05-29(svn r27586) -Fix [FS#6410]: Automatic servicing of road vehicles compared ↵frosch
path finder costs with tile distances, thus vehicles went to depots which were factor 100 too far away. (juanjo)
2015-08-08(svn r27363) -Codechange: Fix codestyle of one-line methods and header ↵alberth
codestyle of derived structs.
2015-08-08(svn r27362) -Codechange: Codestyle fixes for reference var declarations, ↵alberth
static cast type, operator methods.
2015-07-12(svn r27332) -Change: Enable YAPF cache debugging with desync debug level 2.frosch
2014-04-23(svn r26482) -Codechange: add an include that allows us to undefine/redefine ↵rubidium
"unsafe" functions to prevent them from being used, and thus having to care about certain aspects of their return values
2013-11-26(svn r26117) -Cleanup: unneeded NULL checkrubidium
2013-11-23(svn r26058) -Fix: handle the return value of a number of functions betterrubidium
2013-07-14(svn r25609) -Fix [FS#5216]: under certain circumstances a track type change ↵rubidium
would make the end-of-line-is-red setting ineffective
2013-07-14(svn r25608) -Codechange: make EndSegmentReasonBits available in yapf_base.hpprubidium
2013-02-03(svn r24964) -Fix [FS#5416]: With YAPF the docking behaviour differed per ↵rubidium
direction; now favour docking in the direction you approached
2013-01-11(svn r24905) -Feature(ish): Implement station randomisation triggers.peter1138
2013-01-08(svn r24900) -Fix [FS#5389]: Comments with typos (most fixes supplied by ↵planetmaker
Eagle_rainbow)
2012-08-18(svn r24481) -Feature [FS#5127]: Make the pathfinder decide whether ships ↵frosch
shall leave depots towards north or south.
2011-12-20(svn r23640) -Fix: stop using FORCEINLINE (1/3rd of the instances were, the ↵truebrain
others were still regular inline), but make sure inline is always a 'forced' inline (I am looking at you MSVC)
2011-12-17(svn r23564) -Fix [FS#4888]: Extending a path reservation starting at a ↵michi_cc
partially reserved rail station could fail.
2011-11-04(svn r23093) -Codechange: add a default NULL for the Z of GetTileSlope and ↵rubidium
use it
2011-11-04(svn r23091) -Codechange: rename some Get*Z functions to Get*PixelZ ↵rubidium
functions if they return the Z in pixels (like TilePixelHeight)
2011-08-21(svn r22801) -Feature: [YAPF] Take canal/ocean speed fraction of ships into ↵michi_cc
account.
2011-05-02(svn r22410) -Document: some more bits ;)rubidium
2011-04-19(svn r22350) -Change: make YAPF hash tables much smaller, it should improve ↵smatz
performance significantly (about 15%)
2011-04-19(svn r22348) -Codechange: split ship-specific part of yapf_node.hpp to ↵smatz
yapf_node_ship.hpp
2011-02-25(svn r22144) -Codechange: Unify 'while (true)' to 'for (;;)'alberth
2011-02-07(svn r22017) -Codechange: move MarkTileDirtyByTile to viewport_func.hrubidium
2011-02-06(svn r21996) -Fix [FS#4472]: [YAPF] Under some circumstances vehicles could ↵rubidium
be lost
2011-01-15(svn r21815) -Fix [FS#3908]: [YAPF] Apply a pathfinder penalty for back of ↵rubidium
one-way path signals so those aren't preferred over other possibilities
2011-01-15(svn r21803) -Cleanup: Remove unnecessary semicolons.terkhen
2010-12-28(svn r21652) -Cleanup: one semicolon is enoughsmatz
2010-12-27(svn r21651) -Fix [FS#4338] (r21229): infinite loop in the road pathfinder ↵rubidium
due to bouncing around in an "one way" trap; two one ways pointing towards eachother making it impossible to leave
2010-12-22(svn r21594) -Codechange: Whitespace fixes in ifndef/define lines.alberth
2010-12-15(svn r21524) -Fix [FS#4302]: Do not apply the last signal red pathfinder ↵michi_cc
penalty when the signal is a path signal.
2010-12-14(svn r21521) -Codechange: Unify some cached values that were present in both ↵terkhen
road vehicles and trains.
2010-12-13(svn r21511) -Feature: vehicle lost message for shipsrubidium
2010-12-13(svn r21510) -Feature [FS#1956]: vehicle lost message for road vehiclesrubidium
2010-12-13(svn r21509) -Codechange: rename the rail pathfinders "path_not_found" ↵rubidium
parameter to "path_found" and remove the ! where the variables are set / read
2010-11-20(svn r21273) -Codechange: Return values should start at the same line.alberth
2010-11-20(svn r21271) -Change: use the last red instead of last red exit penalty for ↵rubidium
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)
2010-11-09(svn r21121) -Fix (r21100): Use the cached max speed when calculating YAPF ↵terkhen
penalties for road vehicles.
2010-11-07(svn r21107) -Fix: Don't use the maximum track speed where the maximum ↵michi_cc
vehicle speed is meant.