| Age | Commit message (Collapse) | Author |
|---|
|
instead.
|
|
validness.
|
|
returning D0xx texts.
|
|
auto-refitting.
|
|
related variables
|
|
functions if they return the Z in pixels (like TilePixelHeight)
|
|
draw different sprites on the map and in various GUIs.
|
|
Vehicle to simplify code.
|
|
|
|
|
|
DecreaseGroupNumVehicle() with GroupStatistics::CountVehicle().
|
|
|
|
|
|
|
|
order index in case of a goto-nearest-depot order and no depot could be found.
|
|
as no real order influencing path finding is added
|
|
of automatic orders until the next real order is reached.
|
|
invalidations themself (from autoreplace and refitting).
|
|
"center" (for movement) of vehicles is (currently still) always at 4/8th original vehicle length from the front, so trains should stop at the same location regardless of the length of the front engine
|
|
|
|
|
|
|
|
process these events asynchronously before the next redraw. Calling window code directly from command scope uses wrong _current_company and might issue nested DoCommands() which interfer with the running command.
|
|
is flipped in the depot
|
|
flipped in the depot
|
|
actually try to do so (Rubidium)
|
|
|
|
|
|
engines/wagons in the depot by default for NewGRFs
|
|
|
|
tiles in the depot
-Fix [FS#4461]: don't count the number of vehicles but the length of vehicles to (configurably) limit train length
|
|
and cur_real_order_index to keep track of the current real order in an unambiguous way.
-Fix [FS#4440]: Automatic orders behave now stable wrt. service orders and are not added or removed depending on the need of servicing.
-Fix: Various other issues with automatic orders, e.g. vehicles getting stuck with "no orders" when there are automatic orders at the end of the order list.
|
|
a function in GroundVehicle
|
|
make SetLastSpeed a function of GroundVehicle
|
|
length, not for each its wagon with invalid length
|
|
bridge ramp and directed outside the bridge, it could still have track set to TRACK_BIT_WORMHOLE
|
|
|
|
|
|
slope, its GOINGUP/DOWN weren't swapped
|
|
speed by 10%, but also when you're just 1% too fast, so limit the slowdown till the new maximum speed
|
|
it wouldn't have (re)set the GOINGUP/DOWN bits after leaving the tunnel/bridge
|
|
same code three times
|
|
competitor's train; take the lazy non-future proof version of the fix from the 1.0 branch as fixing the real bug is significantly more complex and might even break some backwards compatability if not done perfectly
|
|
|
|
road vehicles and trains.
|
|
|
|
parameter to "path_found" and remove the ! where the variables are set / read
|
|
found" status to a separate function
|
|
be more generic
|
|
lost_vehicle_warning
|
