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

     5

The first thing you need to do is to get the error message. You can access OSX's build-in log by double-clicking Crash_Log_Opener. OTTD will do that if that file is present in the same folder as OTTD and is not renamed. However, major crashes can prevent the autoopen feature and you have to do it manually then 

     6

If Crash_Log_Opener doesn't work you can view the log by opening Console inside Applications/utilities.

     7

     8

If you use the Console app, you should look at the buttom of the console.log window

     9

    10

The problems are as follows:

    11

NOTE: build from source means to download the source and compile 

    12

yourself. If you get one of the build from source error with the version 

    13

that is downloaded on a dmg file, you should make a bug report

    14

    15

--Didn't find a needed file:

    16

	you just give it the file it asks for. It even tells you what 

    17

folder it wants it in

    18

	most common version of this problem is "Error: Cannot open file 

    19

'data/sample.cat'"

    20

	if you get that one, that means that you haven't got all the 

    21

needed files from the WINDOWS version of TTD

    22

	or if you build from source, 

    23

    24

--Error: No available language packs

    25

	you need at least one .lng file in your lang folder. This applies 

    26

only to people who build from source

    27

    28

--spritecache.c:237: failed assertion `b'

    29

	you got an outdated grf file. Update from the data folder in the 

    30

source. This applies only to people, who build from 	source

    31

    32

--assertion error that are not triggered by one of the errors listed in 

    33

this file:

    34

	you most likely found a bug. Write down the assertion and try to 

    35

see if you can reproduce it. If you can, make a

    36

	savegame from just before it happens (autosaves are useful here) 

    37

and post a bugreport with it on sourceforge

    38

	Write what you did to trigger the bug and what assertion it made