Mercurial > hg > openttd
annotate known-bugs.txt @ 14522:6db23c86f0a9 draft
(svn r19093) -Codechange: do not prefix console debug output with 'condbg', [console] is enough
author | smatz <smatz@openttd.org> |
---|---|
date | Wed, 10 Feb 2010 23:38:43 +0000 |
parents | fd371dc2957b |
children | dd5dce187c8a |
rev | line source |
---|---|
13056
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
1 OpenTTD's known bugs |
14450
94d7ee68af4e
(svn r19007) -Prepare: 1.0.0-beta4
rubidium <rubidium@openttd.org>
parents:
14318
diff
changeset
|
2 Last updated: 2010-02-04 |
94d7ee68af4e
(svn r19007) -Prepare: 1.0.0-beta4
rubidium <rubidium@openttd.org>
parents:
14318
diff
changeset
|
3 Release version: 1.0.0-beta4 |
801
ecb5021a7ec4
(svn r1271) -Fix: set eol-style to native on missing files
darkvater <darkvater@openttd.org>
parents:
diff
changeset
|
4 ------------------------------------------------------------------------ |
13056
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
5 |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
6 |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
7 Table of Contents: |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
8 ------------------ |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
9 1) About |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
10 2) Known bugs in the this stable release |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
11 3) Known bugs that will not be solved |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
12 |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
13 |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
14 1) About: |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
15 -- ------ |
1821
e87620b119bd
(svn r2325) - Update OpenTTD for 0.4.0 release
Darkvater <Darkvater@openttd.org>
parents:
1153
diff
changeset
|
16 All bugs listed below are marked as known. Please do not submit any bugs |
7908
7519c50587e5
(svn r11460) -Documentation: update some documentation to better match the current state and the state in the nearby future of OpenTTD.
rubidium <rubidium@openttd.org>
parents:
7588
diff
changeset
|
17 that are the same as these. If you do, do not act surprised, because |
801
ecb5021a7ec4
(svn r1271) -Fix: set eol-style to native on missing files
darkvater <darkvater@openttd.org>
parents:
diff
changeset
|
18 we WILL flame you!! |
ecb5021a7ec4
(svn r1271) -Fix: set eol-style to native on missing files
darkvater <darkvater@openttd.org>
parents:
diff
changeset
|
19 |
ecb5021a7ec4
(svn r1271) -Fix: set eol-style to native on missing files
darkvater <darkvater@openttd.org>
parents:
diff
changeset
|
20 Of course if you have more knowledge about any of these bugs, have more |
ecb5021a7ec4
(svn r1271) -Fix: set eol-style to native on missing files
darkvater <darkvater@openttd.org>
parents:
diff
changeset
|
21 specifics, we welcome you to report them. React to the given bug indicated |
7106
33296909b1b1
(svn r10378) -Merge: release changes from 0.5.
rubidium <rubidium@openttd.org>
parents:
6744
diff
changeset
|
22 by the number below on http://bugs.openttd.org. |
7908
7519c50587e5
(svn r11460) -Documentation: update some documentation to better match the current state and the state in the nearby future of OpenTTD.
rubidium <rubidium@openttd.org>
parents:
7588
diff
changeset
|
23 |
801
ecb5021a7ec4
(svn r1271) -Fix: set eol-style to native on missing files
darkvater <darkvater@openttd.org>
parents:
diff
changeset
|
24 |
13056
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
25 2) Known bugs in the this stable release: |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
26 -- -------------------------------------- |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
27 The following bugs are known to exist in this stable release and |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
28 we intend to fix them. Some bugs are known but are not fixable or |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
29 fixing them would cause further problems. Those bugs can be found |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
30 in the "Known bugs that will not be solved" section. |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
31 |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
32 The bugs in this section all refer to a ticket in our bug tracking system |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
33 that you can find at: http://bugs.openttd.org |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
34 If the bugs are closed but still listed here it means that the bug is fixed |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
35 and that the nightlies and next major release will not have that bug. |
2947
f172ff485fb3
(svn r3505) - Update known-bugs and delete scenarios from SVN.
Darkvater <Darkvater@openttd.org>
parents:
1918
diff
changeset
|
36 |
14186
7213f12941ea
(svn r18734) -Prepare: for 1.0.0-beta2
rubidium <rubidium@openttd.org>
parents:
14157
diff
changeset
|
37 - 3447 [OSX] SDL port is unuseable |
14077
b3d14eab7992
(svn r18622) -Merge: release changes
rubidium <rubidium@openttd.org>
parents:
13921
diff
changeset
|
38 - 2782 [OSX] Port hopelessly outdated |
11154
7244386c689f
(svn r15501) -Document: the changes made over the last months
rubidium <rubidium@openttd.org>
parents:
10399
diff
changeset
|
39 - 2585 [OSX] OS' mouse pointer showing |
12125
dd5b77965bb5
(svn r16541) -Merge: changelog etc. changes from 0.7 branch
rubidium <rubidium@openttd.org>
parents:
11311
diff
changeset
|
40 - 2484 [OSX] Cannot enter CJK characters |
13056
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
41 |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
42 |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
43 3) Known bugs that will not be solved: |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
44 -- ----------------------------------- |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
45 This section lists all known bugs that we do not intend to fix and the |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
46 reasons why we think that fixing them is infeasible. We might make some |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
47 minor improvements that reduce the scope of these bugs, but we will not |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
48 be able to completely fix them. |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
49 |
13773
955e98a9a36e
(svn r18298) -Document: that the dummy AI message is because 'you' don't have an AI... and how to 'solve' the issue; way too many people are ignorant
rubidium <rubidium@openttd.org>
parents:
13525
diff
changeset
|
50 No suitable AI can be found |
955e98a9a36e
(svn r18298) -Document: that the dummy AI message is because 'you' don't have an AI... and how to 'solve' the issue; way too many people are ignorant
rubidium <rubidium@openttd.org>
parents:
13525
diff
changeset
|
51 If you have no AIs and an AI is started the so-called 'dummy' AI will |
955e98a9a36e
(svn r18298) -Document: that the dummy AI message is because 'you' don't have an AI... and how to 'solve' the issue; way too many people are ignorant
rubidium <rubidium@openttd.org>
parents:
13525
diff
changeset
|
52 be loaded. This AI does nothing but writing a message on the AI debug |
955e98a9a36e
(svn r18298) -Document: that the dummy AI message is because 'you' don't have an AI... and how to 'solve' the issue; way too many people are ignorant
rubidium <rubidium@openttd.org>
parents:
13525
diff
changeset
|
53 window and showing a red warning. There are basically two solutions |
955e98a9a36e
(svn r18298) -Document: that the dummy AI message is because 'you' don't have an AI... and how to 'solve' the issue; way too many people are ignorant
rubidium <rubidium@openttd.org>
parents:
13525
diff
changeset
|
54 for this problem: you must change the settings so no AI is started, |
955e98a9a36e
(svn r18298) -Document: that the dummy AI message is because 'you' don't have an AI... and how to 'solve' the issue; way too many people are ignorant
rubidium <rubidium@openttd.org>
parents:
13525
diff
changeset
|
55 this is done in the difficulty settings window. The other solution is |
955e98a9a36e
(svn r18298) -Document: that the dummy AI message is because 'you' don't have an AI... and how to 'solve' the issue; way too many people are ignorant
rubidium <rubidium@openttd.org>
parents:
13525
diff
changeset
|
56 acquiring (downloading) some AI. The easiest way to do this is via |
955e98a9a36e
(svn r18298) -Document: that the dummy AI message is because 'you' don't have an AI... and how to 'solve' the issue; way too many people are ignorant
rubidium <rubidium@openttd.org>
parents:
13525
diff
changeset
|
57 the "Check Online Content" button in the main (intro) menu or via |
955e98a9a36e
(svn r18298) -Document: that the dummy AI message is because 'you' don't have an AI... and how to 'solve' the issue; way too many people are ignorant
rubidium <rubidium@openttd.org>
parents:
13525
diff
changeset
|
58 "AI Settings" -> "Select AI" -> "Check Online Content" which is also |
955e98a9a36e
(svn r18298) -Document: that the dummy AI message is because 'you' don't have an AI... and how to 'solve' the issue; way too many people are ignorant
rubidium <rubidium@openttd.org>
parents:
13525
diff
changeset
|
59 accessed via the main menu. |
955e98a9a36e
(svn r18298) -Document: that the dummy AI message is because 'you' don't have an AI... and how to 'solve' the issue; way too many people are ignorant
rubidium <rubidium@openttd.org>
parents:
13525
diff
changeset
|
60 |
13525
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
61 Clipping problems [FS#119] |
13056
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
62 In some cases sprites are not drawn as one would expect. Examples of |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
63 this are aircraft that might be hidden below the runway or trees that |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
64 in some cases are rendered over vehicles. |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
65 The primary cause of this problem is that OpenTTD does not have enough |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
66 data (like a 3D model) to properly determine what needs to be drawn in |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
67 front of what. OpenTTD has bounding boxes but in lots of cases they |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
68 are either too big or too small and then cause problems with what |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
69 needs to be drawn in front of what. Also some visual tricks are used. |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
70 For example trains at 8 pixels high, the catenary needs to be drawn |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
71 above that. When you want to draw bridges on top of that, which are |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
72 only one height level (= 8 pixels) higher, you are getting into some |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
73 big problems. |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
74 We can not change the height levels; it would require us to either |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
75 redraw all vehicle or all landscape graphics. Doing so would mean we |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
76 leave the Transport Tycoon graphics, which in effect means OpenTTD |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
77 will not be a Transport Tycoon clone anymore. |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
78 |
13525
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
79 Lost trains ignore (block) exit signals [FS#1473] |
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
80 If trains are lost they ignore block exit signals, blocking junctions |
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
81 with presignals. This is caused because the path finders cannot tell |
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
82 where the train needs to go. As such a random direction is chosen at |
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
83 each junction. This causes the trains to occasionally to make choices |
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
84 that are unwanted from a player's point of view. |
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
85 This will not be fixed because lost trains are in almost all cases a |
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
86 network problem, e.g. a train can never reach a specific place. This |
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
87 makes the impact of fixing the bug enormously small against the |
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
88 amount of work needed to write a system that prevents the lost trains |
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
89 from taking the wrong direction. |
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
90 |
13921
067f6dfa097e
(svn r18452) -Document: update the known-bugs a bit; quite a few bugs in there are fixing in trunk already.
rubidium <rubidium@openttd.org>
parents:
13828
diff
changeset
|
91 Vehicle owner of last transfer leg gets paid for all [FS#2427] |
067f6dfa097e
(svn r18452) -Document: update the known-bugs a bit; quite a few bugs in there are fixing in trunk already.
rubidium <rubidium@openttd.org>
parents:
13828
diff
changeset
|
92 When you make a transfer system that switches vehicle owners. This |
067f6dfa097e
(svn r18452) -Document: update the known-bugs a bit; quite a few bugs in there are fixing in trunk already.
rubidium <rubidium@openttd.org>
parents:
13828
diff
changeset
|
93 is only possible with 'industry stations', e.g. the oil rig station |
067f6dfa097e
(svn r18452) -Document: update the known-bugs a bit; quite a few bugs in there are fixing in trunk already.
rubidium <rubidium@openttd.org>
parents:
13828
diff
changeset
|
94 the owner of the vehicle that does the final delivery gets paid for |
067f6dfa097e
(svn r18452) -Document: update the known-bugs a bit; quite a few bugs in there are fixing in trunk already.
rubidium <rubidium@openttd.org>
parents:
13828
diff
changeset
|
95 the whole trip. It is not shared amongst the different vehicle |
067f6dfa097e
(svn r18452) -Document: update the known-bugs a bit; quite a few bugs in there are fixing in trunk already.
rubidium <rubidium@openttd.org>
parents:
13828
diff
changeset
|
96 owners that have participated in transporting the cargo. |
067f6dfa097e
(svn r18452) -Document: update the known-bugs a bit; quite a few bugs in there are fixing in trunk already.
rubidium <rubidium@openttd.org>
parents:
13828
diff
changeset
|
97 This sharing is not done because it would enormously increase the |
067f6dfa097e
(svn r18452) -Document: update the known-bugs a bit; quite a few bugs in there are fixing in trunk already.
rubidium <rubidium@openttd.org>
parents:
13828
diff
changeset
|
98 memory and CPU usage in big games for something that is happening |
067f6dfa097e
(svn r18452) -Document: update the known-bugs a bit; quite a few bugs in there are fixing in trunk already.
rubidium <rubidium@openttd.org>
parents:
13828
diff
changeset
|
99 in only one corner case. We think it is not worth the effort until |
067f6dfa097e
(svn r18452) -Document: update the known-bugs a bit; quite a few bugs in there are fixing in trunk already.
rubidium <rubidium@openttd.org>
parents:
13828
diff
changeset
|
100 sharing of stations is an official feature. |
067f6dfa097e
(svn r18452) -Document: update the known-bugs a bit; quite a few bugs in there are fixing in trunk already.
rubidium <rubidium@openttd.org>
parents:
13828
diff
changeset
|
101 |
13525
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
102 Forbid 90 degree turns does not work for crossing PBS paths [FS#2737] |
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
103 When you run a train through itself on a X junction with PBS turned on |
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
104 the train will not obey the 'forbid 90 degree turns' setting. This is |
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
105 due to the fact that we can not be sure that the setting was turned |
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
106 off when the track was reserved, which means that we assume it was |
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
107 turned on and that the setting does not hold at the time. We made it |
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
108 this way to allow one to change the setting in-game, but it breaks |
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
109 slightly when you are running your train through itself. Running a |
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
110 train through means that your network is broken and is thus a user |
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
111 error which OpenTTD tries to graciously handle. |
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
112 Fixing this bug means that we need to record whether this particular |
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
113 setting was turned on or off at the time the reservation was made. This |
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
114 means adding quite a bit of data to the savegame for solving an issue |
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
115 that is basically an user error. We think it is not worth the effort. |
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
116 |
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
117 Duplicate (station) names after renaming [FS#3204] |
13056
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
118 After renaming stations one can create duplicate station names. This |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
119 is done giving a station the same custom name as another station with |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
120 an automatically generated name. |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
121 The major part of this problem is that station names are translatable. |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
122 Meaning that a station is called e.g. '<TOWN> Central' in English and |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
123 '<TOWN> Centraal' in Dutch. This means that in network games the |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
124 renaming of a town could cause the rename to succeed on some clients |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
125 and fail at others. This creates an inconsistent game state that will |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
126 be seen as a 'desync'. Secondly the custom names are intended to fall |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
127 completely outside of the '<TOWN> <name>' naming of stations, so when |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
128 you rename a town all station names are updated accordingly. |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
129 As a result the decision has been made that all custom names are only |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
130 compared to the other custom names in the same class and not compared |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
131 to the automatically generated names. |
f512ef96e101
(svn r17554) -Update: documentation about bug reporting and known bugs
rubidium <rubidium@openttd.org>
parents:
12716
diff
changeset
|
132 |
13525
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
133 Extreme CPU usage/hangs when using SDL and PulseAudio [FS#3294] |
13447
6da28bcbe3b2
(svn r17956) -Document: CPU usage issues with SDL-ALSA-PulseAudo
rubidium <rubidium@openttd.org>
parents:
13172
diff
changeset
|
134 OpenTTD can be extremely slow/use a lot of CPU when the sound is |
13452
3873d8ca4550
(svn r17961) -Document: also document the hanging of SDL on quiting if it 'talks' to PulseAudio via its virtual ALSA device
rubidium <rubidium@openttd.org>
parents:
13447
diff
changeset
|
135 played via SDL and then through PulseAudio's ALSA wrapper. Under the |
3873d8ca4550
(svn r17961) -Document: also document the hanging of SDL on quiting if it 'talks' to PulseAudio via its virtual ALSA device
rubidium <rubidium@openttd.org>
parents:
13447
diff
changeset
|
136 same configuration OpenTTD, or rather SDL, might hang when exiting |
14157
e2ce35943a54
(svn r18705) -Update: the known bugs document about the PulseAudio issue based on mgmuscari's solution/workaround
rubidium <rubidium@openttd.org>
parents:
14077
diff
changeset
|
137 the game. This problem is seen most in Ubuntu 9.04 and higher. |
e2ce35943a54
(svn r18705) -Update: the known bugs document about the PulseAudio issue based on mgmuscari's solution/workaround
rubidium <rubidium@openttd.org>
parents:
14077
diff
changeset
|
138 |
e2ce35943a54
(svn r18705) -Update: the known bugs document about the PulseAudio issue based on mgmuscari's solution/workaround
rubidium <rubidium@openttd.org>
parents:
14077
diff
changeset
|
139 This is because recent versions of the PulseAudio sound server are |
e2ce35943a54
(svn r18705) -Update: the known bugs document about the PulseAudio issue based on mgmuscari's solution/workaround
rubidium <rubidium@openttd.org>
parents:
14077
diff
changeset
|
140 configured to use timer-based audio scheduling rather than |
e2ce35943a54
(svn r18705) -Update: the known bugs document about the PulseAudio issue based on mgmuscari's solution/workaround
rubidium <rubidium@openttd.org>
parents:
14077
diff
changeset
|
141 interrupt-based audio scheduling. Configuring PulseAudio to force |
e2ce35943a54
(svn r18705) -Update: the known bugs document about the PulseAudio issue based on mgmuscari's solution/workaround
rubidium <rubidium@openttd.org>
parents:
14077
diff
changeset
|
142 use of interrupt-based scheduling may resolve sound problems for |
e2ce35943a54
(svn r18705) -Update: the known bugs document about the PulseAudio issue based on mgmuscari's solution/workaround
rubidium <rubidium@openttd.org>
parents:
14077
diff
changeset
|
143 some users. Under recent versions of Ubuntu Linux (9.04 and higher) |
e2ce35943a54
(svn r18705) -Update: the known bugs document about the PulseAudio issue based on mgmuscari's solution/workaround
rubidium <rubidium@openttd.org>
parents:
14077
diff
changeset
|
144 this can be accomplished by changing the following line in the |
14498
fd371dc2957b
(svn r19069) -Fix: typo in known-bugs.txt
glx <glx@openttd.org>
parents:
14450
diff
changeset
|
145 /etc/pulse/default.pa file: |
14157
e2ce35943a54
(svn r18705) -Update: the known bugs document about the PulseAudio issue based on mgmuscari's solution/workaround
rubidium <rubidium@openttd.org>
parents:
14077
diff
changeset
|
146 load-module module-udev-detect |
e2ce35943a54
(svn r18705) -Update: the known bugs document about the PulseAudio issue based on mgmuscari's solution/workaround
rubidium <rubidium@openttd.org>
parents:
14077
diff
changeset
|
147 to |
e2ce35943a54
(svn r18705) -Update: the known bugs document about the PulseAudio issue based on mgmuscari's solution/workaround
rubidium <rubidium@openttd.org>
parents:
14077
diff
changeset
|
148 load-module module-udev-detect tsched=0 |
e2ce35943a54
(svn r18705) -Update: the known bugs document about the PulseAudio issue based on mgmuscari's solution/workaround
rubidium <rubidium@openttd.org>
parents:
14077
diff
changeset
|
149 Note that PulseAudio must be restarted for changes to take effect. |
e2ce35943a54
(svn r18705) -Update: the known bugs document about the PulseAudio issue based on mgmuscari's solution/workaround
rubidium <rubidium@openttd.org>
parents:
14077
diff
changeset
|
150 Older versions of PulseAudio may use the module-hal-detect module |
e2ce35943a54
(svn r18705) -Update: the known bugs document about the PulseAudio issue based on mgmuscari's solution/workaround
rubidium <rubidium@openttd.org>
parents:
14077
diff
changeset
|
151 instead. Adding tsched=0 to the end of that line will have a similar |
e2ce35943a54
(svn r18705) -Update: the known bugs document about the PulseAudio issue based on mgmuscari's solution/workaround
rubidium <rubidium@openttd.org>
parents:
14077
diff
changeset
|
152 effect. |
e2ce35943a54
(svn r18705) -Update: the known bugs document about the PulseAudio issue based on mgmuscari's solution/workaround
rubidium <rubidium@openttd.org>
parents:
14077
diff
changeset
|
153 |
e2ce35943a54
(svn r18705) -Update: the known bugs document about the PulseAudio issue based on mgmuscari's solution/workaround
rubidium <rubidium@openttd.org>
parents:
14077
diff
changeset
|
154 Another possible solution is selecting the "pulse" backend of SDL |
e2ce35943a54
(svn r18705) -Update: the known bugs document about the PulseAudio issue based on mgmuscari's solution/workaround
rubidium <rubidium@openttd.org>
parents:
14077
diff
changeset
|
155 by either using "SDL_AUDIODRIVER=pulse openttd" at the command |
e2ce35943a54
(svn r18705) -Update: the known bugs document about the PulseAudio issue based on mgmuscari's solution/workaround
rubidium <rubidium@openttd.org>
parents:
14077
diff
changeset
|
156 prompt or installing the 'libsdl1.2debian-pulseaudio' package from |
e2ce35943a54
(svn r18705) -Update: the known bugs document about the PulseAudio issue based on mgmuscari's solution/workaround
rubidium <rubidium@openttd.org>
parents:
14077
diff
changeset
|
157 Ubuntu's Universe repository. For other distributions a similar |
e2ce35943a54
(svn r18705) -Update: the known bugs document about the PulseAudio issue based on mgmuscari's solution/workaround
rubidium <rubidium@openttd.org>
parents:
14077
diff
changeset
|
158 package needs to be installed. |
13524
726fda0da73c
(svn r18043) -Document: the resizing issue with SDL and OpenTTD
rubidium <rubidium@openttd.org>
parents:
13453
diff
changeset
|
159 |
13525
9f69a2dddd00
(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
rubidium <rubidium@openttd.org>
parents:
13524
diff
changeset
|
160 OpenTTD not properly resizing with SDL on X [FS#3305] |
13524
726fda0da73c
(svn r18043) -Document: the resizing issue with SDL and OpenTTD
rubidium <rubidium@openttd.org>
parents:
13453
diff
changeset
|
161 Under some X window managers OpenTTD's window does not properly |
726fda0da73c
(svn r18043) -Document: the resizing issue with SDL and OpenTTD
rubidium <rubidium@openttd.org>
parents:
13453
diff
changeset
|
162 resize. You will either end up with a black bar at the right/bottom |
726fda0da73c
(svn r18043) -Document: the resizing issue with SDL and OpenTTD
rubidium <rubidium@openttd.org>
parents:
13453
diff
changeset
|
163 side of the window or you cannot see the right/bottom of the window, |
726fda0da73c
(svn r18043) -Document: the resizing issue with SDL and OpenTTD
rubidium <rubidium@openttd.org>
parents:
13453
diff
changeset
|
164 e.g you cannot see the status bar. The problem is that OpenTTD does |
726fda0da73c
(svn r18043) -Document: the resizing issue with SDL and OpenTTD
rubidium <rubidium@openttd.org>
parents:
13453
diff
changeset
|
165 not always receive a resize event from SDL making it impossible for |
726fda0da73c
(svn r18043) -Document: the resizing issue with SDL and OpenTTD
rubidium <rubidium@openttd.org>
parents:
13453
diff
changeset
|
166 OpenTTD to know that the window was resized; sometimes moving the |
726fda0da73c
(svn r18043) -Document: the resizing issue with SDL and OpenTTD
rubidium <rubidium@openttd.org>
parents:
13453
diff
changeset
|
167 window will solve the problem. |
726fda0da73c
(svn r18043) -Document: the resizing issue with SDL and OpenTTD
rubidium <rubidium@openttd.org>
parents:
13453
diff
changeset
|
168 Window managers that are known to exhibit this behaviour are KDE's |
726fda0da73c
(svn r18043) -Document: the resizing issue with SDL and OpenTTD
rubidium <rubidium@openttd.org>
parents:
13453
diff
changeset
|
169 and GNOME's. With the XFCE's and LXDE's window managers the resize |
726fda0da73c
(svn r18043) -Document: the resizing issue with SDL and OpenTTD
rubidium <rubidium@openttd.org>
parents:
13453
diff
changeset
|
170 event is sent when the user releases the mouse. |