Erich/openttd - Unnamed repository; edit this file 'description' to name the repository.

Age	Commit message (Collapse)	Author
2008-03-28	(svn r12467) -Codechange: move DepotID to a more logical location.	rubidium

2008-03-22	(svn r12392) -Fix (r12391): Remove yapf/follow_track.cpp again.	maedhros

2008-03-22	(svn r12391) -Feature: Show whether a town is a "city" in the town ↵	maedhros
	description title bar.
2008-02-28	(svn r12313) -Fix: YAPF and NTP did not apply penalty for uphill tracks on ↵	frosch
	steep slopes.
2008-02-25	(svn r12252) -Fix [FS#1801]: Broken FollowTrack_t related functions (thanks ↵	KUDr
	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++
2008-02-20	(svn r12199) -Codechange: Remove magic around the results of ↵	frosch
	GetTileTrackStatus().
2008-02-20	(svn r12190) -Fix [FS#1786](r8080): YAPF always shows 0ms PF time in debug ↵	smatz
	for debug level 2 (patch by IguannaB)
2008-02-14	(svn r12141) -Codechange: Introduce IsNormalRoad[Tile](), ↵	frosch
	IsRoadDepot[Tile]() and HasTileRoadType(); and use them.
2008-02-05	(svn r12066) -Codechange: Rename GetBridge for the more common GetBridgeSpec	belugas
	-Codechange: Remove direct access to the _bridge table in favor of the above mentioned GetBridgeSpec -Codechange: Rationalize the use of Bridge type pointer
2008-02-04	(svn r12056) -Fix [FS#1704]: Enable YAPF to start searching inside a wormhole.	frosch

2008-02-01	(svn r12035) -Fix [FS#1702]: Teach YAPF where trams can reverse, and where not.	frosch

2008-01-23	(svn r11968) -Codechange: remove redundant FindLengthOfTunnel(), use ↵	smatz
	GetTunnelBridgeLength() and/or GetOtherTunnelEnd() instead
2008-01-23	(svn r11960) -Cleanup: simplify some IsTunnel(Tile) / IsBridge(Tile) conditions	smatz

2008-01-22	(svn r11946) -Fix: slope detection of bridge ramps.	frosch
	YAPF failed for steep slopes. Trolly failed for a lot.
2008-01-09	(svn r11800) -Codechange: move some functions to a more logical location + ↵	rubidium
	some type safety.
2008-01-07	(svn r11774) -Change: do not include variables.h in a header when it is not ↵	rubidium
	needed.
2007-12-27	(svn r11706) -Codechange: split vehicle.h and remove another bunch of ↵	rubidium
	useless includes.
2007-12-26	(svn r11702) -Codechange: move all date related stuff to date*.	rubidium

2007-12-26	(svn r11701) -Codechange: removal unnecessary inclusions of map.h (and split ↵	rubidium
	map.h).
2007-12-21	(svn r11680) -Codechange: refactor more out of openttd.h and functions.h.	rubidium

2007-12-19	(svn r11669) -Codechange: refactor tile.h -> tile_type.h and tile_map.h	rubidium

2007-12-16	(svn r11644) -Codechange: merge some functions from tunnel_map.h and ↵	smatz
	bridge_map.h into tunnelbridge_map.h
2007-11-19	(svn r11481) -Codechange: Rename the HASBIT function to fit with the naming ↵	skidd13
	style
2007-11-04	(svn r11383) -Codechange: fixed all the mess around KillFirstBit (tnx to ↵	truelight
	Rubidium and skidd13)
2007-07-29	(svn r10733) -Codechange: change MP_STREET into MP_ROAD as we use the word ↵	rubidium
	"road" everywhere except in the tile type.
2007-07-15	(svn r10578) -Fix [YAPF, ships]: Ships received curve penalty for ↵	KUDr
	non-diagonal straight move. (JazzyJaffa) -The fix in cost calculation uncovered bug in estimate calculation. Ships now use the same estimate algorithm as trains.
2007-07-09	(svn r10492) -Fix [YAPF, r10491]: commands with no effect (glx)	KUDr

2007-07-09	(svn r10491) -Fix [FS#988, YAPF]: When rail segment was cached using ↵	KUDr
	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.
2007-07-09	(svn r10489) -Codechange [YAPF]: FollowTrack_t now has new data member - ↵	KUDr
	m_err. It indicates the reason why the given track/trackdir can't be followed when method CFollowTrackT<>::Follow() returned false.
2007-07-04	(svn r10423) -Fix [YAPF, r10301]: INVALID_TRACKDIR causing buffer overrun ↵	KUDr
	leading to desync in MP game (many thanks Rubidium)
2007-06-30	(svn r10395) -Fix [YAPF]: missing include + some signed/unsigned comparison ↵	KUDr
	warnings
2007-06-29	(svn r10394) -Fix [YAPF]: MP desync caused by incorrect last-red-signal ↵	KUDr
	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.
2007-06-29	(svn r10393) -Fix [YAPF]: Trackdir needs 4 bits to store (not 3). The cached ↵	KUDr
	segment key didn't use the highest trackdir bit. It could confuse YAPF on bi-directional track segments.
2007-06-29	(svn r10392) -Add [YAPF]: added structured dump support into some essential ↵	KUDr
	YAPF classes (node-list, nodes, keys, etc.) and CArrayT
2007-06-27	(svn r10366) -Codechange [YAPF]: added DEBUG_YAPF_CACHE macro that (when set ↵	KUDr
	to 1) allows to track YAPF "cache errors". They are probably responsible for current MP desyncs. (thanks Rubidium for this great idea!). I will deal with those errors/desyncs tomorrow.
2007-06-26	(svn r10349) -Fix [FS#941, YAPF, r10301]: tile/trackdir must be used as node ↵	KUDr
	key and also as segment key in the cache (SmatZ). In the past it was possible to use tile/exitdir as the key because segments beginning on the same tile/exitdir were incorrectly considered the same. What I still don't understand is why this bug happened only on 64 bit systems (linux, Win64).
2007-06-24	(svn r10304) -Fix [YAPF](r10301): removed assert which could violate without ↵	KUDr
	danger when searching for the nearest depot. From now on the segment can be closed without reason in that case (peter1138)
2007-06-24	(svn r10303) -Fix [YAPF](r10301): warning: unused variable tile_cost (peter1138)	KUDr

2007-06-24	(svn r10301) -Fix [FS#901, YAPF]: another assert violation in some special ↵	KUDr
	cases (immeR)
2007-06-18	(svn r10199) -Fix [FS#884, YAPF]: 'target_seen' flag that is set prematurely ↵	KUDr
	in some cases (1 tile long cached segment followed by target station) stops on assert (immeR)
2007-05-31	(svn r10006) -Fix (FS#362): allow different signal types on one tile	glx

2007-05-25	(svn r9922) -Fix (r9914): [YAPF] null pointer dereference.	rubidium

2007-05-24	(svn r9914) -Codechange: prepare GTTS and the pathfinders to handle multiple ↵	rubidium
	road types on a single tile.
2007-05-18	(svn r9869) -Codechange: replace some bytes with VehicleType, i.e. more type ↵	rubidium
	strictness.
2007-04-29	(svn r9746) -Codechange [YAPF]: added DEBUGs level 0 if the current train ↵	KUDr
	order is OT_GOTO_WAYPOINT and waypoint is invalid or v->dest_tile is wrong
2007-04-29	(svn r9745) -Codechange [YAPF}: if destination is a waypoint then YAPF gets ↵	KUDr
	destination tile from that waypoint->xy instead of from v->dest_tile
2007-04-20	(svn r9697) -Fix [YAPF](r9694): 'unused variable' warning (glx)	KUDr

2007-04-20	(svn r9694) -Fix [YAPF][FS#736]: the guessed path (when PF stopped on max. # ↵	KUDr
	of nodes passed) was ignored for ships (desolator)
2007-04-20	(svn r9693) -Codechange [YAPF]: GetBestNode() now returns pointer to node ↵	KUDr
	instead of reference
2007-04-18	(svn r9665) -Documentation: Doxygen corrections,errors, corrections of ↵	belugas
	corrections...