summaryrefslogtreecommitdiff
path: root/known-bugs.txt
diff options
context:
space:
mode:
authorrubidium <rubidium@openttd.org>2009-11-26 16:29:19 +0000
committerrubidium <rubidium@openttd.org>2009-11-26 16:29:19 +0000
commit25a15c79ae081a19e47a53dab765082c5fe0ada5 (patch)
treec2005749a51c49ff227ce9a0ecd98a378646fcae /known-bugs.txt
parentf97daed5eff9412117c173d67fbae08d4e90c057 (diff)
downloadopenttd-25a15c79ae081a19e47a53dab765082c5fe0ada5.tar.xz
(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
Diffstat (limited to 'known-bugs.txt')
-rw-r--r--known-bugs.txt11
1 files changed, 11 insertions, 0 deletions
diff --git a/known-bugs.txt b/known-bugs.txt
index 2e180c880..b9461c6d8 100644
--- a/known-bugs.txt
+++ b/known-bugs.txt
@@ -62,6 +62,17 @@ 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
+ window and showing a red warning. There are basically two solutions
+ for this problem: you must change the settings so no AI is started,
+ this is done in the difficulty settings window. The other solution is
+ acquiring (downloading) some AI. The easiest way to do this is via
+ the "Check Online Content" button in the main (intro) menu or via
+ "AI Settings" -> "Select AI" -> "Check Online Content" which is also
+ accessed via the main menu.
+
Clipping problems [FS#119]
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