1

OpenTTD README

     2

Last updated:    2008-03-04

     3

Release version: 0.6.0-beta5

     4

------------------------------------------------------------------------

     5

     6

     7

Table of Contents:

     8

------------------

     9

1.0) About

    10

2.0) Contacting

    11

 * 2.1 Reporting Bugs

    12

3.0) Supported Platforms

    13

4.0) Installing and running OpenTTD

    14

 * 4.1 (Required) 3rd party files

    15

 * 4.2 OpenTTD directories

    16

 * 4.3 Portable Installations (External Media)

    17

5.0) OpenTTD features

    18

6.0) Configuration File

    19

7.0) Compiling

    20

8.0) Translating

    21

 * 8.1 Guidelines

    22

 * 8.2 Translation

    23

 * 8.3 Previewing

    24

9.0) Troubleshooting

    25

X.X) Credits

    26

    27

    28

1.0) About:

    29

---- ------

    30

OpenTTD is a clone of Transport Tycoon Deluxe, a popular game originally

    31

written by Chris Sawyer.  It attempts to mimic the original game as closely

    32

as possible while extending it with new features.

    33

    34

OpenTTD is licensed under the GNU General Public License version 2.0. For

    35

more information, see the file 'COPYING'.

    36

    37

2.0) Contacting:

    38

---- ----------

    39

The easiest way to contact the OpenTTD team is by submitting bug reports or

    40

posting comments in our forums. You can also chat with us on IRC (#openttd

    41

on irc.oftc.net).

    42

    43

The OpenTTD homepage is http://www.openttd.org/.

    44

    45

You can also find the OpenTTD forums at

    46

http://forum.openttd.org/

    47

    48

    49

2.1) Reporting Bugs:

    50

---- ---------------

    51

To report a bug, please create a Flyspray account and follow the bugs

    52

link from our homepage. Please make sure the bug is reproducible and

    53

still occurs in the latest daily build or the current SVN version. Also

    54

please look through the existing bug reports briefly to see whether the bug

    55

is not already known.

    56

    57

The Flyspray project page URL is: http://bugs.openttd.org/

    58

    59

Please include the following information in your bug report:

    60

        - OpenTTD version (PLEASE test the latest SVN/nightly build)

    61

        - Bug details, including instructions how to reproduce it

    62

        - Platform and compiler (Win32, Linux, FreeBSD, ...)

    63

        - Attach a saved game *and* a screenshot if possible

    64

        - If this bug only occurred recently please note the last

    65

          version without the bug and the first version including

    66

          the bug. That way we can fix it quicker by looking at the

    67

          changes made.

    68

    69

    70

3.0) Supported Platforms:

    71

---- --------------------

    72

OpenTTD has been ported to several platforms and operating systems. It shouldn't

    73

be very difficult to port it to a new platform. The currently working platforms

    74

are:

    75

    76

  BeOS                 - SDL

    77

  FreeBSD              - SDL

    78

  Linux                - SDL

    79

  MacOS X (universal)  - Cocoa video and sound drivers (SDL works too, but not 100% and not as a universal binary)

    80

  MorphOS              - SDL

    81

  OpenBSD              - SDL

    82

  OS/2                 - SDL

    83

  Windows              - Win32 GDI (faster) or SDL

    84

    85

    86

4.0) Installing and running OpenTTD:

    87

---- -------------------------------

    88

    89

Installing OpenTTD is fairly straightforward. Either you have downloaded an

    90

archive which you have to extract to a directory where you want OpenTTD to

    91

be installed, or you have downloaded an installer, which will automatically

    92

extract OpenTTD in the given directory.

    93

    94

OpenTTD looks in multiple locations to find the required data files (described

    95

in section 4.2). Installing any 3rd party files into a "shared" location has

    96

the advantage that you only need to do this step once, rather than copying the

    97

data files into all OpenTTD versions you have.

    98

Savegames, screenshots, etc are saved relative to the config file (openttd.cfg)

    99

currently being used. This means that if you use a config file in one of the

   100

shared directories, savegames will reside in the save/ directory next to the

   101

openttd.cfg file there.

   102

If you want savegames and screenshots in the directory where the OpenTTD binary

   103

resides, simply have your config file in that location. But if you remove this

   104

config file, savegames will still be in this directory (see notes in section 4.2)

   105

   106

4.1) (Required) 3rd party files:

   107

---- ---------------------------

   108

   109

Before you run OpenTTD, you need to put the game's datafiles into a data/

   110

directory which can be located in various places addressed in the following

   111

section.

   112

As OpenTTD makes use of the original TTD artwork you will need the files listed

   113

below, which you can find on a Transport Tycoon Deluxe CD-ROM.

   114

The Windows installer optionally can copy these files from that CD-ROM.

   115

   116

List of the required files:

   117

	- sample.cat

   118

	- trg1r.grf

   119

	- trgcr.grf

   120

	- trghr.grf

   121

	- trgir.grf

   122

	- trgtr.grf

   123

   124

Alternatively you can use the TTD GRF files from the DOS version:

   125

	- TRG1.GRF

   126

	- TRGC.GRF

   127

	- TRGH.GRF

   128

	- TRGI.GRF

   129

	- TRGT.GRF

   130

   131

If you want the TTD music, copy the gm/ folder from the Windows version

   132

of TTD to your OpenTTD folder (not your data folder - also explained in

   133

the following sections).

   134

   135

Do NOT copy files included with OpenTTD into "shared" directories (explained in

   136

the following sections) as sooner or later you will run into graphical glitches

   137

when using other versions of the game.

   138

   139

4.2) OpenTTD directories

   140

---- -------------------------------

   141

   142

The TTD artwork files listed in the section 4.1 "(Required) 3rd party files"

   143

can be placed in a few different locations:

   144

	1. The current working directory (from where you started OpenTTD)

   145

	2. Your personal directory

   146

		Windows: C:\Documents and Settings\<username>\My Documents\OpenTTD

   147

		Mac OSX: ~/Documents/OpenTTD

   148

		Linux:   ~/.openttd

   149

	3. The shared directory

   150

		Windows: C:\Documents and Settings\All Users\Documents\OpenTTD

   151

		Mac OSX: /Library/Application Support/OpenTTD

   152

		Linux:   not available

   153

	4. The binary directory (where the OpenTTD executable is)

   154

		Windows: C:\Program Files\OpenTTD

   155

		Linux:   /usr/games

   156

	5. The installation directory (Linux only)

   157

		Linux:   /usr/share/games/openttd

   158

	6. The application bundle (Mac OSX only)

   159

		It includes the OTTD files (grf+lng) and it will work as long as they aren't touched

   160

   161

Notes:

   162

	- Linux in the previous list means .deb, but most paths should be similar for others.

   163

	- The previous search order is also used for newgrfs and openttd.cfg.

   164

	- If openttd.cfg is not found, then it will be created using the 2, 4, 1, 3, 5 order.

   165

	- Savegames will be relative to the config file only if there is no save/

   166

	  directory in paths with higher priority than the config file path, but

   167

	  autosaves and screenshots will always be relative to the config file.

   168

   169

The prefered setup:

   170

Place 3rd party files in shared directory (or in personal directory if you don't

   171

have write access on shared directory) and have your openttd.cfg config file in

   172

personal directory (where the game will then also place savegames and screenshots).

   173

   174

   175

4.3) Portable Installations (External Media):

   176

---- ----------------------------------------

   177

   178

You can install OpenTTD on external media so you can take it with you, i.e.

   179

using a USB key, or a USB HDD, etc.

   180

Create a directory where you shall store the game in (i.e. OpenTTD/).

   181

Copy the binary (OpenTTD.exe, OpenTTD.app, openttd, etc), data/ and your

   182

openttd.cfg to this directory.

   183

You can copy binaries for any operating system into this directory, which will

   184

allow you to play the game on nearly any computer you can attach the external

   185

media to.

   186

As always - additional grf files are stored in the data/ dir (for details,

   187

again, see section 4.1).

   188

   189

   190

5.0) OpenTTD features:

   191

---- -----------------

   192

   193

OpenTTD has a lot of features going beyond the original TTD emulation.

   194

Unfortunately, there is currently no comprehensive list of features, but there

   195

is a basic features list on the web, and some optional features can be

   196

controlled through the Configure Patches dialog. We also implement some

   197

features known from TTDPatch (http://www.ttdpatch.net/).

   198

   199

Several important non-standard controls:

   200

   201

* Use Ctrl to place semaphore signals

   202

* Ingame console. More information at

   203

  http://wiki.openttd.org/index.php/Console

   204

   205

   206

6.0) Configuration File:

   207

---- -------------------

   208

The configuration file for OpenTTD (openttd.cfg) is in a simple Windows-like

   209

.INI format. It's mostly undocumented. Almost all settings can be changed

   210

ingame by using the 'Configure Patches' window.

   211

   212

   213

7.0) Compiling:

   214

---- ----------

   215

Windows:

   216

  You need Microsoft Visual Studio .NET. Open the project file

   217

  and it should build automatically. In case you want to build with SDL support

   218

  you need to add WITH_SDL to the project settings.

   219

  PNG (WITH_PNG) and ZLIB (WITH_ZLIB) support is enabled by default. For these

   220

  to work you need their development files. For best results, download the

   221

  openttd-useful.zip file from SourceForge under the Files tab. Put the header

   222

  files into your compiler's include/ directory and the library (.lib) files

   223

  into the lib/ directory.

   224

  For more help with VS see docs/Readme_Windows_MSVC.txt.

   225

   226

  You can also build it using the Makefile with MSYS/MinGW or Cygwin/MinGW.

   227

  Please read the Makefile for more information.

   228

   229

Solaris 10:

   230

  You need g++ (version 3 or higher), together with SDL. Installation of

   231

  libpng and zlib is recommended. For the first build it is required

   232

  to execute "bash configure" first. Note that ./configure does not work

   233

  yet. It is likely that you don't have a strip binary, so use the

   234

  --disable-strip option in that case. Fontconfig (>2.3.0) and freetype

   235

  are optional. "make run" will then run the program.

   236

   237

Unix:

   238

  OpenTTD can be built with GNU "make". On non-GNU systems it's called "gmake".

   239

  However, for the first build one has to do a "./configure" first.

   240

  Note that you need SDL-devel 1.2.5 (or higher) to compile OpenTTD.

   241

   242

MacOS X:

   243

  Use "make" or Xcode (which will then call make for you)

   244

  This will give you a binary for your CPU type (PPC/Intel)

   245

  However, for the first build one has to do a "./configure" first.

   246

  To make a universal binary type "./configure --enabled-universal"

   247

  instead of "./configure".

   248

   249

BeOS:

   250

  Use "make", but do a "./configure" before the first build.

   251

   252

FreeBSD:

   253

  You need the port devel/sdl12 for a non-dedicated build.

   254

  graphics/png is optional for screenshots in the PNG format.

   255

  Use "gmake", but do a "./configure" before the first build.

   256

   257

OpenBSD:

   258

  Use "gmake", but do a "./configure" before the first build.

   259

  Note that you need the port devel/sdl to compile OpenTTD.

   260

   261

MorphOS:

   262

  Use "make". However, for the first build one has to do a "./configure" first.

   263

  Note that you need the MorphOS SDK, latest libnix updates (else C++ parts of

   264

  OpenTTD will not build) and the powersdl.library SDK. Optionally libz,

   265

  libpng and freetype2 developer files.

   266

   267

OS/2:

   268

  A comprehensive GNU build environment is required to build the OS/2 version.

   269

  See the docs/Readme_OS2.txt file for more information.

   270

   271

   272

8.0) Translating:

   273

---- -------------------

   274

See http://www.openttd.org/translating.php for up-to-date information.

   275

   276

The use of the online Translator service, located at

   277

http://translator2.openttd.org/, is highly encouraged. For a username/password

   278

combo you should contact the development team, either by mail, IRC or the

   279

forums. The system is straightforward to use, and if you have any problems,

   280

read the online help located there.

   281

   282

If for some reason the website is down for a longer period of time, the

   283

information below might be of help.

   284

   285

8.1) Guidelines:

   286

---- -------------------

   287

Here are some translation guidelines which you should follow closely.

   288

   289

    * Please contact the development team before beginning the translation

   290

      process! This avoids double work, as someone else may have already

   291

      started translating to the same language.

   292

   293

8.2) Translation:

   294

---- -------------------

   295

So, now that you've notified the development team about your intention to

   296

translate (You did, right? Of course you did.) you can pick up english.txt

   297

(found in the SVN repository under /lang) and translate.

   298

   299

You must change the first two lines of the file appropriately:

   300

   301

##name English-Name-Of-Language

   302

##ownname Native-Name-Of-Language

   303

   304

Note: Do not alter the following parts of the file:

   305

   306

    * String identifiers (the first word on each line)

   307

    * Parts of the strings which are in curly braces (such as {STRING})

   308

    * Lines beginning with ## (such as ##id), other than the first two lines of

   309

      the file

   310

   311

8.3) Previewing:

   312

---- -------------------

   313

In order to view the translation in the game, you need to compile your language

   314

file with the strgen utility, which is now bundled with the game.

   315

   316

strgen is a command-line utility. It takes the language filename as parameter.

   317

Example:

   318

   319

strgen lang/german.txt

   320

   321

This results in compiling german.txt and produces another file named german.lng.

   322

Any missing strings are replaced with the English strings. Note that it looks

   323

for english.txt in the lang subdirectory, which is where your language file

   324

should also be.

   325

   326

That's all! You should now be able to select the language in the game options.

   327

   328

9.0) Troubleshooting

   329

---- ---------------

   330

   331

To see all startup options available to you, start OpenTTD with the

   332

"./openttd -h" option. This might help you tweak some of the settings.

   333

   334

If the game is acting strange and you feel adventurous you can try the

   335

"-d [[<name>]=[<level>]" flag, where the higher levels will give you more

   336

debugging output. The "name" variable can help you to display only some type of

   337

debugging messages. This is mostly undocumented so best is to look in the

   338

source code file debug.c for the various debugging types. For more information

   339

look at http://wiki.openttd.org/index.php/Command_line.

   340

   341

The most frequent problem is missing data files. Don't forget to put all GRF

   342

files from TTD into your data/ folder including sample.cat!

   343

   344

Under Windows 98 and lower it is impossible to use a dedicated server; it will

   345

fail to start. Perhaps this is for the better because those OS's are not known

   346

for their stability.

   347

   348

With the added support for font-based text selecting a non-latin language will

   349

result in garbage (lots of '?') shown on screen. Please open your configuration

   350

file and add a desired font for small/medium/-and large_font. This can be a font

   351

name like "Tahoma" or a path to a font.

   352

   353

Any NewGRF file used in a game is stored inside the savegame and will refuse

   354

to load if you don't have that grf file available. A list of missing files

   355

will be output to the console at the moment, so use the '-d' flag (on windows)

   356

to see this list. You just have to find the files (http://grfcrawler.tt-forums.net/)

   357

put them in the data/ folder and you're set to go.

   358

   359

X.X) Credits:

   360

---- --------

   361

The OpenTTD team (in alphabetical order):

   362

  Jean-Francois Claeys (Belugas) - GUI, newindustries and more

   363

  Bjarni Corfitzen (Bjarni)      - MacOSX port, coder and vehicles

   364

  Matthijs Kooijman (blathijs)   - Pathfinder-guru, pool rework

   365

  Loïc Guilloux (glx)            - General coding

   366

  Christoph Elsenhans (frosch)   - General coding

   367

  Jaroslav Mazanec (KUDr)        - YAPG (Yet Another Pathfinder God) ;)

   368

  Jonathan Coome (Maedhros)      - High priest of the newGRF Temple

   369

  Attila Bán (MiHaMiX)           - WebTranslator, Nightlies, Wiki and bugtracker host

   370

  Owen Rudge (orudge)            - Forum host, OS/2 port

   371

  Peter Nelson (peter1138)       - Spiritual descendant from newGRF gods

   372

  Remko Bijker (Rubidium)        - Lead coder and way more

   373

  Benedikt Brüggemeier (skidd13) - Bug fixer and code reworker

   374

  Zdenek Sojka (SmatZ)           - Bug finder and fixer

   375

   376

Inactive Developers:

   377

  Victor Fischer (Celestar)      - Programming everywhere you need him to

   378

  Tamás Faragó (Darkvater)       - Ex-Lead coder

   379

  Christoph Mallon (Tron)        - Programmer, code correctness police

   380

   381

Retired Developers:

   382

  Ludvig Strigeus (ludde)        - OpenTTD author, main coder (0.1 - 0.3.3)

   383

  Serge Paquet (vurlix)          - Assistant project manager, coder (0.1 - 0.3.3)

   384

  Dominik Scherer (dominik81)    - Lead programmer, GUI expert (0.3.0 - 0.3.6)

   385

  Patric Stout (TrueLight)       - Programmer, webhoster (0.3 - pre0.6)

   386

   387

Thanks to:

   388

  Josef Drexler                  - For his great work on TTDPatch.

   389

  Marcin Grzegorczyk             - For his TTDPatch work and documentation of TTD internals and graphics (signals and track foundations)

   390

  Petr Baudis (pasky)            - Many patches, newgrf support, etc.

   391

  Simon Sasburg (HackyKid)       - For the many bugfixes he has blessed us with

   392

  Stefan Meißner (sign_de)       - For his work on the console

   393

  Mike Ragsdale                  - OpenTTD installer

   394

  Cian Duffy (MYOB)              - BeOS port / manual writing

   395

  Christian Rosentreter (tokai)  - MorphOS / AmigaOS port

   396

  Richard Kempton (RichK67)      - Additional airports, initial TGP implementation

   397

  Michael Blunck                 - For revolutionizing TTD with awesome graphics

   398

  George                         - Canal graphics

   399

  David Dallaston (Pikka)        - Tram tracks

   400

  All Translators                - For their support to make OpenTTD a truly international game

   401

  Bug Reporters                  - Thanks for all bug reports

   402

  Chris Sawyer                   - For an amazing game!