OpenTTD's known bugs

------------------------------------------------------------------------

Table of Contents:

------------------

1) About

2) Known bugs in the this stable release

3) Known bugs that will not be solved

1) About:

-- ------

fixing them would cause further problems. Those bugs can be found

in the "Known bugs that will not be solved" section.

The bugs in this section all refer to a ticket in our bug tracking system

that you can find at: http://bugs.openttd.org

If the bugs are closed but still listed here it means that the bug is fixed

and that the nightlies and next major release will not have that bug.

- 3198	[OSX] "Could not get system colour space" error on some Mac OS X 10.6

- 3194	[OSX] Full screen 'strobing' on some Mac OS X 10.6

- 3190	[OSX] Compiling fails on some Mac OS X 10.6

- 3159	[NewGRF] Autoreplace resets (or does not keep) value of variable F2

- 2955	With path signals depots are less likely to be visited

- 2891	Ignore signal does not keep the train running when in path signalled block till the next signal

- 2616	[NewGRF] Cloning creates vehicles with invalid subcargos

- 2613	[NewGRF] House property 15 does not work

- 2585	[OSX] OS' mouse pointer showing

- 2484	[OSX] Cannot enter CJK characters

- 1762	Strange Autoreplace behaviour

- 1140	[OSX] Not smooth moving map with touchpad

3) Known bugs that will not be solved:

-- -----------------------------------

This section lists all known bugs that we do not intend to fix and the

reasons why we think that fixing them is infeasible. We might make some

minor improvements that reduce the scope of these bugs, but we will not

be able to completely fix them.

No suitable AI can be found

	If you have no AIs and an AI is started the so-called 'dummy' AI will

	be loaded. This AI does nothing but writing a message on the AI debug

Lost trains ignore (block) exit signals [FS#1473]

	If trains are lost they ignore block exit signals, blocking junctions

	with presignals. This is caused because the path finders cannot tell

	where the train needs to go. As such a random direction is chosen at

	each junction. This causes the trains to occasionally to make choices

	that are unwanted from a player's point of view.

	This will not be fixed because lost trains are in almost all cases a

	network problem, e.g. a train can never reach a specific place. This

	makes the impact of fixing the bug enormously small against the

	amount of work needed to write a system that prevents the lost trains

	from taking the wrong direction.

Forbid 90 degree turns does not work for crossing PBS paths [FS#2737]

	When you run a train through itself on a X junction with PBS turned on

	the train will not obey the 'forbid 90 degree turns' setting. This is

	due to the fact that we can not be sure that the setting was turned

	off when the track was reserved, which means that we assume it was

	turned on and that the setting does not hold at the time. We made it

	this way to allow one to change the setting in-game, but it breaks

	slightly when you are running your train through itself. Running a

	train through means that your network is broken and is thus a user

	error which OpenTTD tries to graciously handle.

	Fixing this bug means that we need to record whether this particular

	setting was turned on or off at the time the reservation was made. This