| Age | Commit message (Collapse) | Author |
|---|
|
we had
While at it, replace OTTD_ASSERT with WITH_ASSERT, as this
is always set if assert() is valid. No matter if NDEBUG is set
or not.
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
INVALID_RAILTYPES, if it was accidentally tested, would match any railtype.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Road vehicles shouldn't reverse all of a sudden.
|
|
when the cost of a path exceeds max. penalty.
|
|
|
|
|
|
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
|
|
|
|
integers.
|
|
"unsafe" functions to prevent them from being used, and thus having to care about certain aspects of their return values
|
|
Eagle_rainbow)
|
|
shall leave depots towards north or south.
|
|
|
|
|
|
functions if they return the Z in pixels (like TilePixelHeight)
|
|
|
|
|
|
penalty when the signal is a path signal.
|
|
|
|
|
|
|
|
parameter to "path_found" and remove the ! where the variables are set / read
|
|
|
|
|
|
|
|
|
|
|
|
some headers
|
|
|
|
|
|
|
|
|
