| Age | Commit message (Collapse) | Author |
|---|
|
(michi_cc)
|
|
|
|
railtype info of the vehicle. (michi_cc)
|
|
(michi_cc)
|
|
|
|
|
|
settings stored in the savegame so there is no need to have a duplicate copy of it for new games.
|
|
-Codechange: move all Settings into substructs of _settings in a way that they are logically grouped.
|
|
DiagDirection to Track and Trackbits
|
|
something more than whitespace as description of files that don't have a description.
|
|
|
|
depot_base.h and remove quite a lot of unneeded (before this) includes of depot.h.
|
|
function can be used
|
|
|
|
|
|
|
|
station_func.h.
|
|
|
|
|
|
description title bar.
|
|
steep slopes.
|
|
michi_cc).
-Fixed by removing FollowTrack_t structure and all related functions. Their purpose was to allow to call track followers from C code. They were:
1. never used
2. obsoleted by switching to C++
|
|
GetTileTrackStatus().
|
|
for debug level 2 (patch by IguannaB)
|
|
IsRoadDepot[Tile]() and HasTileRoadType(); and use them.
|
|
-Codechange: Remove direct access to the _bridge table in favor of the above mentioned GetBridgeSpec
-Codechange: Rationalize the use of Bridge type pointer
|
|
|
|
|
|
GetTunnelBridgeLength() and/or GetOtherTunnelEnd() instead
|
|
|
|
YAPF failed for steep slopes.
Trolly failed for a lot.
|
|
some type safety.
|
|
needed.
|
|
useless includes.
|
|
|
|
map.h).
|
|
|
|
|
|
bridge_map.h into tunnelbridge_map.h
|
|
style
|
|
Rubidium and skidd13)
|
|
"road" everywhere except in the tile type.
|
|
non-diagonal straight move. (JazzyJaffa)
-The fix in cost calculation uncovered bug in estimate calculation. Ships now use the same estimate algorithm as trains.
|
|
|
|
electric engine and it ended with non-electric rail it was incorrectly cached with the end reason ESRB_DEAD_END instead of ESRB_RAIL_TYPE. (Eddi)
- It caused YAPF to end prematurely there when it was searching for another path (for non-electric engine).
- It can lead to sub-optimal path taken or 'train is lost' message.
- In MP game it can also cause desync.
- Uses changes made in r10489.
|
|
m_err. It indicates the reason why the given track/trackdir can't be followed when method CFollowTrackT<>::Follow() returned false.
|
|
leading to desync in MP game (many thanks Rubidium)
|
|
warnings
|
|
penalties applied when cached segment was reused. Players that connected more recently (didn't have these segments cached yet) calculated those penalties correctly. This caused different YAPF results.
|
|
segment key didn't use the highest trackdir bit. It could confuse YAPF on bi-directional track segments.
|
