(svn r18044) -Change: mention (one of the) bug report(s) for the known-but-will-not-or-cannot-fix bugs and order them by FS ID
This commit is contained in:
		@@ -62,7 +62,7 @@ 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
 | 
					minor improvements that reduce the scope of these bugs, but we will not
 | 
				
			||||||
be able to completely fix them.
 | 
					be able to completely fix them.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
Clipping problems
 | 
					Clipping problems [FS#119]
 | 
				
			||||||
	In some cases sprites are not drawn as one would expect. Examples of
 | 
						In some cases sprites are not drawn as one would expect. Examples of
 | 
				
			||||||
	this are aircraft that might be hidden below the runway or trees that
 | 
						this are aircraft that might be hidden below the runway or trees that
 | 
				
			||||||
	in some cases are rendered over vehicles.
 | 
						in some cases are rendered over vehicles.
 | 
				
			||||||
@@ -80,7 +80,34 @@ Clipping problems
 | 
				
			|||||||
	leave the Transport Tycoon graphics, which in effect means OpenTTD
 | 
						leave the Transport Tycoon graphics, which in effect means OpenTTD
 | 
				
			||||||
	will not be a Transport Tycoon clone anymore.
 | 
						will not be a Transport Tycoon clone anymore.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
Duplicate (station) names after renaming
 | 
					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
 | 
				
			||||||
 | 
						means adding quite a bit of data to the savegame for solving an issue
 | 
				
			||||||
 | 
						that is basically an user error. We think it is not worth the effort.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					Duplicate (station) names after renaming [FS#3204]
 | 
				
			||||||
	After renaming stations one can create duplicate station names. This
 | 
						After renaming stations one can create duplicate station names. This
 | 
				
			||||||
	is done giving a station the same custom name as another station with
 | 
						is done giving a station the same custom name as another station with
 | 
				
			||||||
	an automatically generated name.
 | 
						an automatically generated name.
 | 
				
			||||||
@@ -96,34 +123,7 @@ Duplicate (station) names after renaming
 | 
				
			|||||||
	compared to the other custom names in the same class and not compared
 | 
						compared to the other custom names in the same class and not compared
 | 
				
			||||||
	to the automatically generated names.
 | 
						to the automatically generated names.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
Forbid 90 degree turns does not work for crossing PBS paths
 | 
					Extreme CPU usage/hangs when using SDL and PulseAudio [FS#3294]
 | 
				
			||||||
	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
 | 
					 | 
				
			||||||
	means adding quite a bit of data to the savegame for solving an issue
 | 
					 | 
				
			||||||
	that is basically an user error. We think it is not worth the effort.
 | 
					 | 
				
			||||||
 | 
					 | 
				
			||||||
Lost trains ignore (block) exit signals
 | 
					 | 
				
			||||||
	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.
 | 
					 | 
				
			||||||
 | 
					 | 
				
			||||||
Extreme CPU usage/hangs on exiting game when using SDL and PulseAudio
 | 
					 | 
				
			||||||
	OpenTTD can be extremely slow/use a lot of CPU when the sound is
 | 
						OpenTTD can be extremely slow/use a lot of CPU when the sound is
 | 
				
			||||||
	played via SDL and then through PulseAudio's ALSA wrapper. Under the
 | 
						played via SDL and then through PulseAudio's ALSA wrapper. Under the
 | 
				
			||||||
	same configuration OpenTTD, or rather SDL, might hang when exiting
 | 
						same configuration OpenTTD, or rather SDL, might hang when exiting
 | 
				
			||||||
@@ -133,7 +133,7 @@ Extreme CPU usage/hangs on exiting game when using SDL and PulseAudio
 | 
				
			|||||||
	Universe repository. For other distributions a similar package needs
 | 
						Universe repository. For other distributions a similar package needs
 | 
				
			||||||
	to be installed.
 | 
						to be installed.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
OpenTTD not properly resizing with SDL on X
 | 
					OpenTTD not properly resizing with SDL on X [FS#3305]
 | 
				
			||||||
	Under some X window managers OpenTTD's window does not properly
 | 
						Under some X window managers OpenTTD's window does not properly
 | 
				
			||||||
	resize. You will either end up with a black bar at the right/bottom
 | 
						resize. You will either end up with a black bar at the right/bottom
 | 
				
			||||||
	side of the window or you cannot see the right/bottom of the window,
 | 
						side of the window or you cannot see the right/bottom of the window,
 | 
				
			||||||
 
 | 
				
			|||||||
		Reference in New Issue
	
	Block a user