File diff r16304:63adae3094ef → r16305:56f2fdacb296
known-bugs.txt
Show inline comments
 
@@ -223,40 +223,50 @@ OpenTTD not properly resizing with SDL o
 
	window will solve the problem.
 
	Window managers that are known to exhibit this behaviour are KDE's
 
	and GNOME's. With the XFCE's and LXDE's window managers the resize
 
	event is sent when the user releases the mouse.
 

	
 
Train crashes entering same junction from block and path signals [FS#3928]
 
	When a train has reserved a path from a path signal to a two way
 
	block signal and the reservation passes a path signal through the
 
	back another train can enter the reserved path (only) via that same
 
	two way block signal.
 
	The reason for this has to do with optimisation; to fix this issue
 
	the signal update has to pass all path signals until it finds either
 
	a train or a backwards facing signal. This is a very expensive task.
 
	The (signal) setups that allow these crashes can furthermore be
 
	considered incorrectly signalled; one extra safe waiting point for
 
	the train entering from path signal just after the backwards facing
 
	signal (from the path signal train) resolves the issue.
 

	
 
Crashes when playing music [FS#3941]
 
	Mac OS X's QuickTime (default music driver) and Windows' MCI (win32
 
	music driver) crash on some songs from OpenMSX. OpenTTD cannot do
 
	anything about this. Please report these crashes to the authors of
 
	OpenMSX so the crash causing songs can be removed or fixed.
 

	
 
Crashes when run in a VM using Parallels Desktop [FS#4003]
 
	When the Windows version of OpenTTD is executed in a VM under
 
	Parallels Desktop a privileged instruction exception may be thrown.
 
	As OpenTTD works natively on OSX as well as natively on	Windows and
 
	these native builds both don't exhibit this behaviour this crash is
 
	most likely due to a bug in the virtual machine, something out of
 
	the scope of OpenTTD. Most likely this is due to Parallels Desktop
 
	lacking support for RDTSC calls. The problem can be avoided by using
 
	other VM-software, Wine, or running natively on OSX.
 

	
 
OpenTTD hangs when started on 32 bits Windows [FS#4083]
 
	Under some circumstances OpenTTD might hang for hours on the
 
	initialisation of the music driver. The exact circumstances are
 
	unknown except that it is the "dmusic" music driver that has the
 
	problem and that the "win32" music driver does not.
 
	As a result using the "win32" music driver will work around this
 
	issue.
 

	
 
	As the exact circumstances are unknown, and the obvious
 
	configuration settings related to the music driver are at their
 
	default we are not able to detect this failure, except when Windows'
 
	music initialisation function returns after several hours and then
 
	there is no point in switching the music driver anymore.
 
	The reason we do not use the "win32" music driver as default are
 
	described in the "Long delay between switching music/song" section
 
	of this document.