| Age | Commit message (Collapse) | Author |
|---|
|
|
|
MaskWireBits always returns its input unchanged if the input
has only 0 or 1 track bits set.
Having only 0 or 1 track bits sets (i.e. non junction tiles)
is by far the most common case.
Examining the state of neighbouring tiles and the subsequent
masking logic is relatively expensive and can be omitted in this case.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
drawing
Road tunnels and bridges do not have any rail, so do not treat them
as if they had when drawing a catenary. (cirdan)
|
|
unambiguously to either RoadCatenary or RailCatenary.
|
|
data is now always accessible
|
|
"unsafe" functions to prevent them from being used, and thus having to care about certain aspects of their return values
|
|
when they are not supposed to, and truncate cargo appropiately if they are allowed to.
|
|
|
|
Eagle_rainbow)
|
|
wires as non-reachable for masking out unnecessary catenary wires.
|
|
that display neither pylons nor catenary.
|
|
transparent, not if the wire is transparent.
|
|
incorrectly.
|
|
|
|
related variables
|
|
|
|
TILE_HEIGHT
|
|
from the bridge code
|
|
use it
|
|
functions if they return the Z in pixels (like TilePixelHeight)
|
|
with foundations. (same as r3935, but for level crossings)
|
|
|
|
more likely to be updates [d-m].
|
|
|
|
some headers
|
|
an existing define on MinGW).
|
|
|
|
the southern bridgehead as tile.
|
|
|
|
|
|
loading a savegame the railtype of some (high ID) trains could be wrong.
After loading the vehicle data in the trains are updated, but after that the "electrification" checks are done which can change the "global" vehicle data. However, this update is not propagated to the vehicles until the consist is updated, e.g. turning around and going to a depot.
This makes some of the trains of a just joined client run as non-electrified trains which can cause it to take a wrong path or to not (randomly) show the electric sparks.
|
|
on slopes with opposite corners raised.
|
|
RAIL_GROUND_HALF_SNOW. That is, resolve the sprites for upper and lower part of the foundation independently.
|
|
|
|
rail types. (To be documented...)
|
|
|
|
if a header require a header make it include that header
|
|
|
|
|
|
is either a rail station or rail waypoint tile
|
|
all over the place when using the more advanced station types.
-Change: make (rail) waypoints sub classes of 'base stations', make buoys waypoints and unify code between them where possible.
|
|
|
|
for all vehicle types
|
|
from VehicleRail to Train
|
