author | tron |
Sun, 17 Jul 2005 20:14:58 +0000 | |
changeset 2116 | 23031555ff54 |
parent 562 | 66cddf7eeb5f |
permissions | -rw-r--r-- |
0 | 1 |
Since you are reading this, OpenTTD have crashed. This file tells you how |
2 |
to fix the most common problems or make to make a bug report, that the |
|
3 |
developers can use to track down the problem |
|
4 |
||
562
66cddf7eeb5f
(svn r971) Mac: updated text files and added the link files from the releases
bjarni
parents:
0
diff
changeset
|
5 |
If it is an assert, OpenTTD will open the console for you, if it is truly a crash, you have to do it yourself. The Console is located at /Applications/Utilities/Console. |
66cddf7eeb5f
(svn r971) Mac: updated text files and added the link files from the releases
bjarni
parents:
0
diff
changeset
|
6 |
The problem is near the button of the page |
0 | 7 |
|
8 |
The problems are as follows: |
|
9 |
NOTE: build from source means to download the source and compile |
|
10 |
yourself. If you get one of the build from source error with the version |
|
11 |
that is downloaded on a dmg file, you should make a bug report |
|
12 |
||
13 |
--Didn't find a needed file: |
|
14 |
you just give it the file it asks for. It even tells you what |
|
15 |
folder it wants it in |
|
16 |
most common version of this problem is "Error: Cannot open file |
|
17 |
'data/sample.cat'" |
|
18 |
if you get that one, that means that you haven't got all the |
|
19 |
needed files from the WINDOWS version of TTD |
|
20 |
or if you build from source, |
|
21 |
||
22 |
--Error: No available language packs |
|
23 |
you need at least one .lng file in your lang folder. This applies |
|
24 |
only to people who build from source |
|
25 |
||
26 |
--spritecache.c:237: failed assertion `b' |
|
27 |
you got an outdated grf file. Update from the data folder in the |
|
28 |
source. This applies only to people, who build from source |
|
29 |
||
30 |
--assertion error that are not triggered by one of the errors listed in |
|
31 |
this file: |
|
32 |
you most likely found a bug. Write down the assertion and try to |
|
33 |
see if you can reproduce it. If you can, make a |
|
34 |
savegame from just before it happens (autosaves are useful here) |
|
35 |
and post a bugreport with it on sourceforge |
|
36 |
Write what you did to trigger the bug and what assertion it made |