| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
Basically, follow_track.hpp contains a fix for half-tiles, but
this wasn't duplicated for when trying to find a depot and in
a few other places. This makes sure all places act the same.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
reverse.
|
|
|
|
|
|
function.
|
|
|
|
|
|
segments with different railtype in the YAPF cache. (JGR)
|
|
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)
|
|
|
|
|
|
railroad checks. (Juanjo)
|
|
|
|
others were still regular inline), but make sure inline is always a 'forced' inline (I am looking at you MSVC)
|
|
|
|
depot in some (corner) cases
|
|
|
|
|
|
|
|
passed bit variable, i.e. allow expressions as parameter
|
|
pathfinding.
|
|
if a header require a header make it include that header
|
|
|
