summaryrefslogtreecommitdiff
path: root/src/pathfinder/yapf/yapf_costrail.hpp
AgeCommit message (Collapse)Author
2021-04-30Remove: performance measurements in YAPFPatric Stout
YAPF was constantly measuring its performance, but only at certain debug-levels this information was shown. Now after years, I sincerely wonder if anyone still knows about this feature and who still use it. Especially with the new framerate window, this detailed performance is not as meaningful anymore as it once was.
2021-04-04Codechange: Replace CBlobT usage with std::vectorCharles Pigott
2021-02-22Change: Make pathfinder account for maximum order speed, if setCharles Pigott
2019-11-10Cleanup: Removed SVN headersS. D. Cloudt
2019-09-30Fix: GCC9's warnings about deprecated implicit assignment operatorsCharles Pigott
2019-05-01Feature: Add NotRoadTypes (NRT)peter1138
2019-04-10Codechange: Use null pointer literal instead of the NULL macroHenry Wilson
2018-06-27Codechange: Use HasTrack(dir) to improve code readability.J0anJosep
2018-06-27Codechange: Increase readability of track functions and pathfinders.J0anJosep
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 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.
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.
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
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-05-02(svn r22410) -Document: some more bits ;)rubidium
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
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-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-07(svn r21107) -Fix: Don't use the maximum track speed where the maximum ↵michi_cc
vehicle speed is meant.
2010-08-01(svn r20286) -Codechange: Unify end of doxygen comments.frosch
2010-08-01(svn r20283) -Codechange: Unify start of doygen comments.frosch
2010-05-26(svn r19896) -Fix [FS#3803] (r18648): [YAPP] Inform the pathfinder as well ↵michi_cc
about the fact that the backside of an one-way path signal can be a safe waiting point.
2010-04-18(svn r19670) -Codechange: Add CeilDiv() and RoundDiv() to simplify integer ↵frosch
divisions with rounding.
2010-02-15(svn r19141) -Fix [FS#3619] (r18421): look-ahead for multitile waypoints ↵rubidium
'made up' data that shouldn't go into the cache, causing desyncs in MP
2009-12-19(svn r18535) -Fix [FS#2722]: don't account for path reservation costs when ↵rubidium
entering a signal block via a 'block' signal. This way you won't get double penalties, both red signals and reservation costs, for the block signalled tracks
2009-12-07(svn r18421) -Fix [FS#3244]: pathfinders wouldn't consider the 'other' ↵rubidium
reachable waypoint tile if the closest one is free but there is no safe waiting point directly after it. Now check for a free safe waiting point beyond the waypoint unless there are junctions before the first safe waiting point.
2009-12-02(svn r18372) -Codechange: push some extra type safety into YAPFrubidium
2009-12-01(svn r18364) -Codechange: move the pathfinders and their related files into ↵rubidium
a separate directory