Age | Commit message (Collapse) | Author |
|
useless includes.
|
|
|
|
map.h).
|
|
logical place and remove about 50% of the includes of 'functions.h'
|
|
it is really needed.
|
|
|
|
single file and do not include gfx.h everywhere to get a Point type.
|
|
|
|
their respective places.
|
|
|
|
|
|
"rail.h" that includes way more than only "rail_type.h") includes at some places.
|
|
remove useless checks
|
|
|
|
|
|
GetVehicleTunnelBridge
|
|
|
|
order.h too
|
|
cause they depend on Random()
-Codechange: Convert the CHANCE macros to functions and rename them fitting to the naming style
|
|
others to scroll to that location.
|
|
remaining to fit with the naming style
|
|
style
|
|
unneeded define
|
|
with the coding style
|
|
last seen while been center-followed
|
|
it needs the cargo types to be the same.
|
|
sub-cargotypes (i.e. livery refits) failed.
|
|
|
|
instead calling it every time the vehicle is drawn
|
|
sell/destroyed it.
|
|
used to check whether there was no vehicle on the ground, except that the former didn't take care of aircraft shadows. So now we only use EnsureNoVehicleOnGround.
|
|
ground when removing owned land, furthermore do not check for shadows (of aircraft).
|
|
all vehicles, instead of not allowing trains to use it (enforced by an assert), but actually using it for trains. Patch by SmatZ.
|
|
|
|
subsystem. Patch by Progman.
|
|
the vehicle anymore (because the player cannot build the engine), the aging warnings as if autorenew is not enabled are shown.
|
|
|
|
part of a dualheaded train engine
|
|
|
|
service a little more.
|
|
a consist.
|
|
state while being marked const.
-Codechange: do not brute force determine the first vehicle in the chain or previous vehicle, but do it by properly accounting the previous and first pointers when updating the next pointer. This gives a performance increase of about 15% when there are a lot of vehicles in the game.
|
|
to save and load private and protected variables in the vehicle struct.
|
|
Vehicle->SetNext() so we can trap instances that change a next pointer and (in the future) update the first/previous pointers based on that.
|
|
a depot.
|
|
|
|
|
|
building menus.
|
|
cleanups might cause memory leaks due to the way C++ works.
|
|
|