TTWiki - User contributions [en-gb]

ECSTVTCNeuSchwansteinCastle

2011-06-17T19:28:22Z

Pm-bot: Fix tables

|-
|=[http://en.wikipedia.org/wiki/Neuschwanstein_Castle||Schloß Neuschwanstein, Schwangau, Germany]=

Drawn by George, help by Oz, Zimmlock (road to entrance, shadows)

Based on

==General data==

{|
!Tiles!!31

|-
|Usage||81%

|-
|Growth Factor||70%
|}

==Stockpile size==

{|
!Level!!Tourists

|-
|Very low||422

|-
|Low||603

|-
|Normal||862

|-
|High||1231

|-
|Very high||1759

|-
|Ultimate||2513
|}

==Location/Positioning Conditions==
*Build outside towns !Tz1, !Tz2, !Tz3, !Tz4 (Town zone 0 allowed)
*Build > 3 tiles from desert tile
*Build on terraformed land (certain tiles must be sloped) see image
*Build > FF FF FF FFh tiles from Tourists centre with the same layout (only one layout instance per map)
*Build > 31 tiles away from other layout of Tourists centre

[http://wiki.ttdpatch.net/tiki-index.php?page=LocationConditions| Description of Location/Positioning Conditions]

==Features==

Supports snow, different trees for different landscapes, company colours.

When built by the player during a game, the roofs will be in Company Colours of the builder. When generated by the game or built while in the scenario editor, the roofs will be Black or Brown.

Supports industry animation.

ECSTVTCKarlstein

2011-06-17T19:28:12Z

Pm-bot: Fix tables

|-
|=[http://en.wikipedia.org/wiki/Karl%C5%A1tejn||Karlštejn, Prague, Czech Republic]=

Drawn by Darkwalker, snowed and company colours by George

Based on

==General data==

{|
!Tiles!!21

|-
|Usage||65%

|-
|Growth Factor||70%
|}

==Stockpile size==

{|
!Level!!Tourists

|-
|Very low||229

|-
|Low||328

|-
|Normal||468

|-
|High||669

|-
|Very high||956

|-
|Ultimate||1365
|}

==Location/Positioning Conditions==
*Build outside towns !Tz1, !Tz2, !Tz3, !Tz4 (Town zone 0 allowed)
*Build > 3 tiles from desert tile
*Build on terraformed land (certain tiles must be sloped) see image
*Build > FF FF FF FFh tiles from Tourists centre with the same layout (only one layout instance per map)
*Build > 31 tiles away from other layout of Tourists centre

[http://wiki.ttdpatch.net/tiki-index.php?page=LocationConditions| Description of Location/Positioning Conditions]

==Features==

Supports snow, different trees for different landscapes, company colours.

When built by the player during a game, the roofs will be in Company Colours of the builder. When generated by the game or built while in the scenario editor, the roofs will be Black.

NewTownGrowthSwitchesdetails

2011-06-15T11:38:36Z

Pm-bot: style: fix <tt> mess-up

=New Town Growth Switches (details)=

How the new town growth switches work

This section describes the switches that apply in "towngrowthratemode 2". They fine tune and control every detail of town growth.

As described in the previous section, TTD internally uses an inverse growth rate, i.e. the number of 70-tick time units between attempts to build a new house. However, the enhanced rate calculation uses a direct growth rate, defined as the average number of new town buildings per 38400 time units, which is approximately 100 years. At the end of calculations this rate is converted to the inverse growth rate. If the inverse growth rate is greater than 255, it's reduced and town growth is blocked randomly to have the same effect on the average.

For comparison, with "towngrowthratemode 0" (TTD's original calculation), the rates are:

{|
!number of active stations!!average rate (new houses per 100 years)

|-
| 0 ||20

|-
| 1 ||182

|-
| 2 ||256

|-
| 3 ||349

|-
| 4 ||480
|}

or, if a building fund is active, the rate is fixed at 640 new houses per century. These rates are as they're normally in TTD, except that a bug with 5 or more stations (see the previous section) is fixed.

For the new growth rate calculation, we have the maximum and minimum rate, the towngrowthratemin and towngrowthratemax switches. Let <tt>''ratediff''</tt> be the difference between the maximum and the minimum, i.e. ratediff = towngrowthratemax - towngrowthratemin</pre>

Then the '''base rate delta multiplier''' (BRDM) is calculated as follows: BRDM = (AS*ASW + PO*POW + MO*MOW + PI*PIW + MI*MIW + GI*GIW + FI*FIW + WI*WIW + SI*SIW + DI*DIW)</tt>

<pre> / (ASW + POW + MOW + PIW + MIW + GIW + FIW + WIW + SIW + DIW)</pre>

where the two-letter abbreviations represent '''growth boost components''' (explained in detail below) depending on, respectively:

{|
!<tt>''AS''</tt> !!the number of active stations

|-
|<tt>''PO''</tt> ||percentage of passengers transported (`passengers out')

|-
|<tt>''MO''</tt> ||percentage of mail transported (`mail out')

|-
|<tt>''PI''</tt> ||incoming passengers (`passengers in')

|-
|<tt>''MI''</tt> ||incoming mail (you get the picture...)

|-
|<tt>''GI''</tt> ||incoming goods

|-
|<tt>''FI''</tt> ||incoming food

|-
|<tt>''WI''</tt> ||incoming water

|-
|<tt>''SI''</tt> ||incoming sweets/candy

|-
|<tt>''DI''</tt> ||incoming fizzy drinks
|}

Each component is a number between 0 and 1, so the result (BRDM) is also between 0 and 1. The rest are weighting factors, represented by the following settings in the configuration file:

{|
!<tt>''ASW''</tt> !!tgractstationsweight

|-
|<tt>''POW''</tt> ||tgrpassoutweight

|-
|<tt>''MOW''</tt> ||tgrmailoutweight

|-
|<tt>''PIW''</tt> ||tgrpassinweight

|-
|<tt>''MIW''</tt> ||tgrmailinweight

|-
|<tt>''GIW''</tt> ||tgrgoodsinweight

|-
|<tt>''FIW''</tt> ||tgrfoodinweight

|-
|<tt>''WIW''</tt> ||tgrwaterinweight

|-
|<tt>''SIW''</tt> ||tgrsweetsinweight

|-
|<tt>''DIW''</tt> ||tgrfizzydrinksinweight
|}

The higher the weighting factor for some component is relative to the other weighting factors, the more influence the asociated growth boost component has on the final growth rate. Note that it's the relation betwen weighting factors that matters; for instance, if all the other weighting factors are zero, the following set tgractstationsweight = 10</tt>

<pre> tgrpassoutweight = 5</pre>

yields exactly the same results as tgractstationsweight = 2</tt>

<pre> tgrpassoutweight = 1</pre>

The growth boost components are calculated as follows:

;<pre>''AS''</tt> = [[NTB / tgrtownsizebase) * TSF) + (1 - TSF]]</pre>

where <tt>''NTB''</tt> is the number of buildings in the town and <tt>''TSF''=tgrtownsizefactor/255</tt> (i.e. it's a value between 0 and 1, which determines how much of the growth rate depends on the town size, in percent). This can be used to add a bit of `exponentiality' to the growth of towns (remember, the growth rate is expressed in new buildings per time unit, so with a constant rate larger towns will appear to grow more slowly).

Then the '''real growth rate''' is calculated:
<pre>RGR = towngrowthratemin + ratediff*CRDM</pre>

where <tt>''CDRM''+===+''RDM''</tt> if <tt>''RDM''</tt> <= 1, and <tt>''CRDM=1''</tt> otherwise.

Then, if a town building fund is active in this town, 600 is added. Then, if the town is one of those supposed to be larger (see the largertowns switch), the rate is doubled. And ''this'' is the final growth rate, in new houses per century.

As a final note, the real growth of towns is a second- or third-order effect of the final growth rate, so don't expect towns to grow exactly at the rate you've calculated from the formulae above.... But on the average it shouldn't be far off.

RoutingRestrictions:Alpha

2011-06-15T11:34:41Z

Pm-bot: /* Examples */ no nocache here

=Routing Restrictions=

Enables train routetracing to be restricted according to user criteria

2.6 alpha 0 r1078 or later

==Switch==

Configuration file: tracerestrict on|off

Command line: -ZZ

==Description==

This features allows the route finding algorithm of trains to be conditionally allowed or denied to search past a restricted signal based upon criteria set by the user.

This feature does not actually block a train from passing, but merely convinces the train's route finding algorithm that the path is a dead end, if a train does not meet the required criteria.

In essence a restricted signal discourages trains which do not meet the criteria from passing.

The criteria of restricted signals are viewed and set by clicking the 'Routefinding' button at the bottom of the signal gui window [[ExperimentalFeatures:Alpha]].

The available variables which can be tested are:
*Number of train carriages (this includes the locomotive)
*Maximum train speed in mph/kph
*Station of current order
*Station of next order
*Last visited station
*Depot of current order
*Depot of next order
*Total train horsepower
*Total train weight (in tonnes)
*Train cargo (can the train carry/not carry the selected cargo)
*Number of tiles from signal
*Signal status: SW, SE, NW or NE
*Train is/is not searching for a depot
*Entered side of tile
*Tile from which the PBS block was entered

The variable is selected from the drop down box opened by pressing the first button, labeled: 'Variable'.

The comparative operator is then selected from the second button, labeled: 'Op', the default operator for all variables except signal status is 'is'.

The value to which the variable is compared is set by pressing the third button, labeled: 'Value'. If the variable is comparing a depot, station or signal, the mouse icon will change, indicating that you may click on the appropriate tile.

A train will pass the signal if it satisfies the comparison test(s) set.

The share and copy buttons are used to share or copy respectively criteria sets with existing restricted signals by clicking on the button and then the signal to copy/share with.

The criteria set is deleted when the last signal which references it is deleted/reset.

The reset button clears the restriction criteria of a signal, without affecting any shared signals, as if the signal had been deleted and reconstructed.

Restricted signals can be distinguished from non-restricted signals using the landinfo window: the text will include the word: 'Restricted'.

==Boolean Operators==

More than one criteria may be used by the use of one of the boolean operators and, or, or xor.

Or is defined as: one or the other, or both.

Xor is defined as: one or the other, but not both.

This is done by clicking on the and, or or xor buttons.

A boolean operator appears directly before and one indent level to the left of the two criteria it operates on.

Boolean operators can be recursed.

Boolean operators can be removed only if at least one of its criteria is not set, and, upon removal, will be replaced by the one which is set, or a blank criteria if neither is set.

A criteria or boolean operator can be selected by clicking it or the line it is on. It can be then deleted using the delete button, or modified. A blank restriction criteria is indicated by a dash. Any blank or incomplete restriction criteria returns true/allows a train to pass.

==Signal Status==

The signal status criteria test whether one of the up to four signals on a tile is red or green. There are four track directions on which signals can be placed. Which signal status criteria is used indicates which signal to test, as shown below:

/

SW&NW;=Signal in SW direction

SE&NE;=Signal in NE direction

\

SW&NW;=Signal in NW direction

SE&NE;=Signal in SE direction

||

NW=West side facing North

NE=East side facing North

SW=West side facing South

SE=East side facing South

=

NW=North side facing West

NE=North side facing East

SW=South side facing West

SE=South side facing East

Non-existent signals are classified as red.

==PBS block entered from==

When not in a PBS block, the condition "Entered tile of the PBS block is..." will always return false/prevent a train from passing; the condition "Entered tile of the PBS block is not..." will always return true/permit a train to pass.

Current technical limitations:

There is a limit on the number of signal restrictions that can be placed on the map. Max 16,384 objects total, including all sub objects, copied objects, binary operators, etc.

Maximum of 256 restricted signals per sixteenth sector of map. 64x64 area.

Shared restrictions only count once for each criteria/binary operator on the first limit.

These limits may be increased in the future if the need arises.

==Examples==

See the [http://uwe.s2000.ws/ttdx/signal/restrictions.php?lang=en| TTDPatch Signalling Guide] for examples how to use routing restrictions (and other signalling stuff).

This feature was contributed by Jonathan G. Rennison.

RoutingRestrictions:Alpha

2011-06-15T11:34:14Z

Pm-bot: style fix

=Routing Restrictions=

Enables train routetracing to be restricted according to user criteria

2.6 alpha 0 r1078 or later

==Switch==

Configuration file: tracerestrict on|off

Command line: -ZZ

==Description==

This features allows the route finding algorithm of trains to be conditionally allowed or denied to search past a restricted signal based upon criteria set by the user.

This feature does not actually block a train from passing, but merely convinces the train's route finding algorithm that the path is a dead end, if a train does not meet the required criteria.

In essence a restricted signal discourages trains which do not meet the criteria from passing.

The criteria of restricted signals are viewed and set by clicking the 'Routefinding' button at the bottom of the signal gui window [[ExperimentalFeatures:Alpha]].

The available variables which can be tested are:
*Number of train carriages (this includes the locomotive)
*Maximum train speed in mph/kph
*Station of current order
*Station of next order
*Last visited station
*Depot of current order
*Depot of next order
*Total train horsepower
*Total train weight (in tonnes)
*Train cargo (can the train carry/not carry the selected cargo)
*Number of tiles from signal
*Signal status: SW, SE, NW or NE
*Train is/is not searching for a depot
*Entered side of tile
*Tile from which the PBS block was entered

The variable is selected from the drop down box opened by pressing the first button, labeled: 'Variable'.

The comparative operator is then selected from the second button, labeled: 'Op', the default operator for all variables except signal status is 'is'.

The value to which the variable is compared is set by pressing the third button, labeled: 'Value'. If the variable is comparing a depot, station or signal, the mouse icon will change, indicating that you may click on the appropriate tile.

A train will pass the signal if it satisfies the comparison test(s) set.

The share and copy buttons are used to share or copy respectively criteria sets with existing restricted signals by clicking on the button and then the signal to copy/share with.

The criteria set is deleted when the last signal which references it is deleted/reset.

The reset button clears the restriction criteria of a signal, without affecting any shared signals, as if the signal had been deleted and reconstructed.

Restricted signals can be distinguished from non-restricted signals using the landinfo window: the text will include the word: 'Restricted'.

==Boolean Operators==

More than one criteria may be used by the use of one of the boolean operators and, or, or xor.

Or is defined as: one or the other, or both.

Xor is defined as: one or the other, but not both.

This is done by clicking on the and, or or xor buttons.

A boolean operator appears directly before and one indent level to the left of the two criteria it operates on.

Boolean operators can be recursed.

Boolean operators can be removed only if at least one of its criteria is not set, and, upon removal, will be replaced by the one which is set, or a blank criteria if neither is set.

A criteria or boolean operator can be selected by clicking it or the line it is on. It can be then deleted using the delete button, or modified. A blank restriction criteria is indicated by a dash. Any blank or incomplete restriction criteria returns true/allows a train to pass.

==Signal Status==

The signal status criteria test whether one of the up to four signals on a tile is red or green. There are four track directions on which signals can be placed. Which signal status criteria is used indicates which signal to test, as shown below:

/

SW&NW;=Signal in SW direction

SE&NE;=Signal in NE direction

\

SW&NW;=Signal in NW direction

SE&NE;=Signal in SE direction

||

NW=West side facing North

NE=East side facing North

SW=West side facing South

SE=East side facing South

=

NW=North side facing West

NE=North side facing East

SW=South side facing West

SE=South side facing East

Non-existent signals are classified as red.

==PBS block entered from==

When not in a PBS block, the condition "Entered tile of the PBS block is..." will always return false/prevent a train from passing; the condition "Entered tile of the PBS block is not..." will always return true/permit a train to pass.

Current technical limitations:

There is a limit on the number of signal restrictions that can be placed on the map. Max 16,384 objects total, including all sub objects, copied objects, binary operators, etc.

Maximum of 256 restricted signals per sixteenth sector of map. 64x64 area.

Shared restrictions only count once for each criteria/binary operator on the first limit.

These limits may be increased in the future if the need arises.

==Examples==

See the [http://uwe.s2000.ws/ttdx/signal/restrictions.php?lang=en| TTDPatch Signalling Guide| nocache] for examples how to use routing restrictions (and other signalling stuff).

This feature was contributed by Jonathan G. Rennison.

VersionTrouble

2011-06-15T11:32:54Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Version Trouble=

What if TTDPatch doesn't recognize your version of TTD.

This section should now be of no relevance, since all versions of TTD that I know of are supported by TTDPatch. But if you're interested anyway, read on.

TTDPatch will have to know the locations of code that has to be patched. This will usually be a table that has to be compiled into the program to make it work.

If the version of TTD you are using is not known to TTDPatch, it will tell you so and offer the option to try and start anyway. However, this is a bit tricky, and may result in the program locking up, or causing a protection violation. Depending on your operating system, this may lead to complete hang of the computer. So, don't try this if you have any important programs running in the background.

These are the versions that are known to work:

{|
! !!File size

|-
|Language ||DOS ||Windows

|-
|American ||496,543 ||1,695,744

|-
|English ||496,601 ||1,696,256

|-
|German ||499,583 ||1,699,328

|-
|French ||505,759 ||1,707,008

|-
|Spanish ||506,237 ||1,707,520
|}

ErrorMessages

2011-06-15T11:32:44Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Error Messages=

An explanation of all the error messages.

This is a list of all errors and warnings that can occur while TTDPatch is still loading. Messages while inside the game are not covered here.

The messages are sorted alphabetically, ignoring an initial "Warning:" or "Error:" that is not part of the actual message.

;*** Internal TTDPatch error #[number] ***: This message should not occur, it means something went wrong in the patching program. Report this message to the author of TTDPatch.

;Can't write to TTDLOAD.OVL, is it read-only?: This happens after copying the TTD executable to <tt>ttdload.ovl</tt>, when TTDPatch tries to patch this copy. Most likely it is set to read-only. Remove the read-only flag and it should work.

;Configuration line is longer than 32 chars, truncated: For some reason, you have a very long line in the configuration file. Only the beginning of it has been considered by the patch.

;Copy error - file doesn't exist.: When TTDPatch tried to copy the old executable to <tt>ttdload.ovl</tt>, something went wrong and nothing was copied. You can try to copy it yourself and run TTDPatch again. It will then try to work with this copy instead, and not copy the file itself.

;Could find neither TYCOON.EXE nor TTDX.EXE.:

;Could not find GAMEGFX.EXE.: There are two possibilities. Either you started TTDPatch from the wrong directory, or you have the wrong version of the patch. Make sure that you copied the patch into the TTD folder, and that you didn't mismatch the DOS and the Windows versions.

;Could not determine program version.: This means that TTDPatch couldn't find out what version of TTD you are using, and thus cannot patch it. This can only be fixed by sending your executable to the maintainer of TTDPatch. It's most likely that it actually isn't TTD but something else.

;Couldn't execute TTDLOAD.OVL: There was a problem running the game (contained in TTDLOAD.OVL). This message is followed by a more detailed error description that may help you determine the cause of this problem.

;Couldn't find cfg file <file>. Ignored.: You specified a file with the -C option or the include directive, but it could not be found. You probably have a typo in the filename.

;Couldn't install code loader - try deleting TTDLOAD.OVL.: TTDPatch found some problem in <tt>ttdload.ovl</tt> and couldn't patch it. You can try to delete <tt>ttdload.ovl</tt> so that TTDPatch creates it again, hopefully correct this time. Otherwise there is some problem with your TTD executable.

;Create process failed.: This happens in the Windows version of TTDPatch, when it is unable to start TTD. The reason can be that TTD is not installed properly, or that <tt>ttdloadW.ovl</tt> is outdated. Please try deleting <tt>ttdloadW.ovl</tt> first, and see if it helps. If not, check whether TTD runs without the patch. If it doesn't, you may have to re-install. One other possibility is a conflict with another program or not enough system resources. Try shutting down all other programs before running TTDPatch.

;Invalid cfg line `<name>': You have a switch in the configuration file or on the command line that TTDPatch does not recognize. Either you have made a typo, or it could be that your configuration file is for a different version of the patch. For example, you may have a configuration tool that makes files for TTDPatch 2.0, but you only actually have TTDPatch 1.9. In that case TTDPatch 1.9 will complain about all switches that are new in version 2.0, because it doesn't understand them yet. Just upgrade your TTDPatch version, or remove the offending line from the configuration file.

;Invalid original segment length.: This message indicates that something is wrong with the <tt>ttdload.ovl</tt>. Try deleting that file, so that TTDPatch can create it again, hopefully correctly this time.

;Not enough memory available, need <number> KB more: The DOS version ran out of memory. You must make more memory available to the patch for it to work.

;Reading ttdpttxt.dat: Invalid file format.: TTDPatch could not read ttdpttxt.dat because it is not in the expected format. You must run mkpttxt.exe to generate this file from ttdpttxt.txt. Do not edit ttdpttxt.dat directly.

;Sorry, this version of TTDPatch works only with the DOS/Windows version: You have the wrong version of the patch, or the wrong version of TTD. You must get the DOS version of the patch for the DOS version of TTD, and the Windows version of the patch for the Windows version of TTD.

;TTD is not installed properly (registry error <number>): This message can occur if you have the Windows version, but didn't install it with its installer program. TTDPatch tried reading the registry entries for the game, but they were either missing or incorrect. Try reinstalling TTD with its installer program.The specific meaning of the registry error numbers:
#The registry key "HKLM\Software\Fish Technology Group\Transport Tycoon Deluxe" does not exist.
#
#The value "HDPath" does not exist or could not be read from the registry key.
#
#The TTD folder does not have a short (DOS-compatible) name.Other numbers indicate that the "HDPath" registry value could not be updated.

;The switch `<name>' (-<option>) is obsolete: You have a switch in the configuration file or on the command line that is no longer valid in this version of TTDPatch. Either it has been replaced by a different switch, or it is no longer required. Simply remove it from the configuration file or command line.

;This is not Transport Tycoon Deluxe: You are trying to run TTDPatch, but you do not have Transport Tycoon Deluxe. You probably have a version of regular Transport Tycoon, which will not work with the patch.

;This is not a known executable format: TTDPatch could not determine whether your game is the DOS or Windows version. This probably means that the installation is corrupt; try installing TTD again.

;ttdpttxt.dat must be remade for this version of TTDPatch: You are using ttdpttxt.dat, see [[CustomIngameTexts| Custom in-game texts]]. Your file was for a different version of TTDPatch and must be updated. Simply run mkpttxt.exe again to do this.

;Unknown switch `<name>': See "Invalid cfg line" above.

;Unknown on/off state <name>, set to off: You have a line in the configuration file that has a switch setting which the patch does not recognize, so the switch is turned off. Perhaps you made a typo when editing the file.

;Unrecognised .EXE format.: <tt>tycoon.exe</tt> is not an executable file. This should not happen, unless you copied or renamed something else to <tt>tycoon.exe</tt>.

;Version has too many numbers!: While trying to find out version of TTD, the program got confused because it found more than the usual three numbers. This can only be fixed by sending your executable to the maintainer of TTDPatch.

;Version is unknown!:

;Your program version is not known to this program: You are running TTDPatch with an unknown version of TTD, or you told it to ignore its version data. This will usually work fine, but it may take a longer time to start TTD than usual, up to a minute on slow computers.

VersionHistory

2011-06-15T11:32:34Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Version History=

What feature was added when?

For versions from 1.9 and above, this section lists the versions that introduced new features or sign cheats. It only mentions final release versions, and neither alpha nor beta versions. It also omits all minor changes, bug fixes and small improvements to existing versions. For a full list of changes, check the change log on the source code page of the TTDPatch site.

{|
!Version<span style='color:white'>_</span>!!Changes

|-
|V2.0 ||New Graphics for all vehicle types

|-
|09/25/03 ||Unified Maglev

|-
|||Bridge Speed Limits

|-
|||Eternal Game

|-
|||Show Full Date

|-
|||Signals on Road Traffic Side

|-
|||Electrified Railways

|-
|||New Starting Year

|-
|||Realistic Acceleration

|-
|||Error Popup Time

|-
|||New Town Growth Switches

|-
|||Miscellaneous Modifications

|-
|||Save Optional Data

|-
|||More Build Options

|-
|||Semaphore Signals

|-
|||Plant Many Trees

|-
|||More Hotkeys

|-
|||More Currencies and Euro

|-
|||Manual Track Conversion

|-
|||Enhanced Graphical User Interface

|-
|||More Town Statistics

|-
|||New Wagon Age Rating

|-
|||Build on Slopes

|-
|||Track Type Cost Differences

|-
|||New Plane Speed

|-
|||Build on Coasts

|-
|||Sell Entire Trains

|-
|||New Road Vehicle Crashes

|-
|||Stable Industries

|-
|||Cht: Semaphores to switch between semaphore and light signals

|-
|||Cht: PlantTrees to plant trees in a rectangular area around the sign

|-
|||Cht: RemoveHQ to remove the company headquarters

|-
|||Cht: Climate to switch the current climate

|-
|||Cht: Subsidy to force a new subsidy to be offered

|-
|||Cht: Debugger to activate TTD's built-in debugger

|-
|||Cht: Graphics to activate or deactivate specific new .grf files

|-
|V1.9 ||Go to Depot

|-
|10/29/02 ||New ship models and graphics

|-
|||Cht: PlayerID supports switching temporarily

|-
|||Subsidiary management

|-
|||Move red error popup windows into a corner

|-
|||Gradual loading/unloading

|-
|||Signal wait times

|-
|||Disaster selection

|-
|||Distinction between forced and regular auto-renewal

|-
|||News items generated for more events

|-
|||Custom in-game texts

|-
|||Cht: NoUnload

|-
|||Cht: ReloadEngines

|-
|||Lots of bug fixes again...

|-
|V1.8.1 ||Multiheaded Steam and Diesel engines smoke properly

|-
|07/24/02 ||Cht: PlayerID

|-
|||Feeder service

|-
|||Added Hungarian, Italian and Spanish translations

|-
|||Pre-signals without signals are green now

|-
|||Screenshots work in the Windows version too

|-
|||Many bugfixes: Ctrl key, Clearghosts, etc.

|-
|V1.8 ||Add extended command line options (-X...)

|-
|03/11/02 ||Plane crash control (by Marcin)

|-
|||Bribe option

|-
|||Show current vehicle speed

|-
|||Sign cheats optionally cost money

|-
|||New signal graphics for pre-signals

|-
|||More complex pre-signal setups

|-
|||Autorenew: automatically renew old vehicles

|-
|||Crash logger for crashes of the DOS version

|-
|||Windows 2000/XP compatibility for the Windows version

|-
|||Savegames with more vehicles now get a <tt>trp</tt> filename

|-
|||Add load option to the disk menu

|-
|||City bridges can be removed

|-
|||Cht: AllEngines, Cht: RemoveEngines, Cht: ClearPreSig

|-
|||Multihead option now has an optional speedup parameter

|-
|||Convert source code from C++ to C (by Marcin)

|-
|||... and many, many bug fixes

|-
|V1.7 ||TTDPatch supports the Windows version of TTD

|-
|02/24/01 ||Trains with additional engines for more power

|-
|||TTDPatch can swap out and leave more memory to TTD

|-
|||A low memory version that only needs 2.5 MB

|-
|||Road vehicles queue up at the station

|-
|||Cht: resetstation

|-
|||More airports allowed per city

|-
|||Many, many bug fixes

|-
|||Now patching <tt>ttdload.ovl</tt>, not <tt>ttdload.exe</tt>

|-
|||TTDPatch is now distributed under the terms of the GPL

|-
|V1.6 ||Several bug fixes in the cfg file, etc.

|-
|07/15/00 ||Keep small airports around

|-
|||Fixed eternal servicing after 2055

|-
|||Build 7x7 station with Ctrl

|-
|||Longer bridges, up to half the map length

|-
|||Multiplayer: Cheats only affect player placing signs

|-
|||Bulldoze all city roads

|-
|||Boost AI, set recursion factor

|-
|||Cht: AllNonStop and Cht: NoNonStop

|-
|||Cht: ServInt

|-
|||Automatic language selection and support for English, Dutch, French, German and Italian.

|-
|V1.5.1 ||Configuration file support

|-
|10/16/99 ||Convert source code to C++

|-
|||Convert docs to Texinfo

|-
|||Framework for multiple language support

|-
|V1.5 ||Turn off inflation

|-
|09/04/99 ||Office towers in Tropic/Arctic accept food too

|-
|||Longer stations (up to 7 squares)

|-
|||Borrow/Repay maximum amount by holding Ctrl key

|-
|||The default service interval is selectable

|-
|||Cht: DumpMemory for saving uncompressed

|-
|||Pre-signals no longer experimental

|-
|||Persistent engines won't become obsolete if in use

|-
|||Full load for any cargo type, not the whole train

|-
|||Selectable station goods

|-
|||Fixed Cht: OwnCrossing (I think...)

|-
|V1.4.3 ||This was just a bug fix beta version, no real release

|-
|08/16/99 ||Fixed -trpb and -x, they were broken (except when using -a) since V1.4

|-
|V1.4.2 ||Three new versions supported: German, French and Spanish

08/12/99

|-
|V1.4.1 ||-w switch for pre-signals now actually works

|-
|07/31/99 ||(no need to use -a anymore)

|-
|V1.4 ||More multiplayer support (now also for -l)

|-
|07/29/99 ||Improved algorithm to calculate load/unload times

|-
|||Mammoth trains up to 127 cars

|-
|||Cht: Renew and Cht: Owncrossing

|-
|||Pre-signals supported but still experimental

|-
|||All switches must be entered in lowercase letters now, to allow for future switches. Sorry for the inconvenience but I'm running out of letters...

|-
|V1.3 ||Fixed "ghost train" bug

|-
|07/16/99 ||Added multiplayer support

|-
|V1.2 ||Enable CD-only version of TTD by passing the CD drive parameter to TTDPatch

|-
|06/06/99 ||Stations extensible to up to 7 equal platforms

|-
|V1.1 ||Now also supports version V2.01.119 with a file size of 496601 bytes.

06/03/99

|-
|V1.0 ||First version, supports TTD V2.01.119, with an executable file size of 496543 bytes.

|-
|05/30/99||Train refitting

|-
|||Improved handling of way points to prevent trains from getting lost

|-
|||Automatic Track Conversion to Monorail or Maglev (including trains)

|-
|||Trains can be faster on hills and in curves

|-
|||More vehicles; now up to 40000 instead of just 690

|-
|||More trains, planes etc.; now up to 240 of each type
|}

If you're interested, you can read the original announcement of version 1.0 [http://groups-beta.google.com/group/comp.sys.ibm.pc.games.strategic/msg/3d275b8366f42cbb| here] (Google Groups).

CurrencyEntries

2011-06-15T11:32:24Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Currency Entries=

How to change currencies and create custom ones

With "morecurrencies", TTD can have up to 19 currencies. All available slots are filled by default, but you can change any of the new currencies to another one simply by overwrititng its data in <tt>ttdpttxt.txt</tt>, see above.

The entries beginning with "curr_" specify the data for a currency. Each of them consists of six parts, separated by NUL codes (\00). Filling the first part is mandatory, but all other parts can be empty, meaning that the values hardcoded in TTDPatch should be applied. If you specify numbers, you can put spaces before and after them.

The first part is the name of the currency followed by the currency symbol in brackets (For example: "Hungarian Forint (Ft)".) This text will be shown in the currency list in the Game Options window. This part is mandatory.

The second part is the exchange ratio between British pounds and the currency multiplied by 1000. For example, 1 British pound is 375.62 Forint, so this value should be 375620 for the Forint.

The third part defines the thousand separator and symbol placement of the currency. If this isn't empty, the first character will be used for the thousand separator. If a second character is present, and it's a character number one (\01), the currency symbol will be placed after the number by default. If there is no second character or it's not \01, the currency symbol will be before the number by default. These options can be overridden if the player forces all currencies to have the same separator or placement by modifying the parameter of the morecurrencies switch.

The fourth and fifth parts can't be longer than four characters, these specify the currency symbol. The first symbol is used before the number, the second after the number. If there should be no space between the number and the symbol ("$100,000"), both of them should be the same and they shouldn't contain spaces. If there should be a space separating the number and the symbol ("$ 100,000"), the first symbol entry should end with a space, the second should start with a space.

The sixth part specifies when should the currency change to Euro. If it should never change, specify 0, otherwise specify the year when it changes to Euro.

If you simply want to translate the name of the currency, translate the first part and put six NUL codes (\00) after it. If you want to change only some options (for example, you want to lower the exchange ratio), specify only the data you want to change, and leave the other parts empty (the currency name must be specified, though). If you want to change the currency to something else, specify all the parts to override all the hardcoded TTDPatch data.

Here's an example that sets the options of the Hungarian Forint to the defaults used by TTDPatch:<pre>curr_HUF="Hungarian Forint (Ft)\00375620\00.\01\00Ft \00 Ft\002008\00"</pre>

Note that each option starts immediately after the preceding \00 separator.

DetailedInformation

2011-06-15T11:32:14Z

Pm-bot: Bot: Automated text replacement (--= +==)

What all the custom text entries mean

This section has a list of all entries in <code>ttdpttxt.txt</code>, with the default values, and what they are used for. You should leave the control codes (a backslash followed by two hexadecimal digits, e.g. \7c) alone, they are place holders for numbers, other text strings or colour or font changes. To put a literal backslash, use two backslashes (\\). \00 marks the end of a string.

;bribetext="Bribe the local authority\00": Menu entry in the local authority menu for the bribe option

;bribedesc="\94\80\n":<code>"\90 Bribe the local authority to increase your rating, at the risk "</code>

<code>"of a severe penalty if caught.\n"</code>

<code>" Cost: \7f\00"</code>

Description of the bribe option in the local authority menu

;bribefailed1="\94Your attempted bribery has been\00":

;bribefailed2="\94discovered by a regional investigator.\00": Both lines of the error message shown when a bribe is denied.

;headingfor="\95\80, \84\00":

;headingfordepot1="\95\80 Train Depot, \84\00":

;headingfordepot2="\95\80 Road Depot, \84\00":

;headingfordepot3="\95\80 Ship Depot, \84\00":

;headingfordepot4="\95\80 Hangar, \84\00": Used with "showspeed" in the status bar of each vehicle. The first entry is used for stations, the rest for specific types of depots. You can modify the first two entries to show tractive effort and acceleration when the realistic acceleration model is enabled. For details, see [[RealisticAcceleration| Realistic Acceleration]].

;withsignals="Railroad track with \80 (\80)\00":

;wplainsignals="plain signals\00":

;wpresignals="pre-signals\00":

;wpresigexits="pre-signal exits\00":

;wprecombined="combined signals\00":

;presigautomatic="automatic\00":

;presigmanual="manual\00": Description of track with signals when using the presignal switches, for the four different kinds of signals possible, as well as whether they were set automatically or manually.

;vehmulttoolow1="\94Warning: Game saved with veh. multiplier \7e.\00":

;vehmulttoolow2="\94Removed \7e vehicles in \7e consists and \7e special objects.\00": Error message shown when a savegame is loaded that had a "morevehicles" setting larger than the current setting. See [[IncreasedNumberOfVehicles| Increased Number of Vehicles]].

;rchunknotloaded1="\94Warning: Game uses some features of\00":

;rchunknotloaded2="\94TTDPatch that are disabled or not present in this version. "

"Data may be lost.\00": Error message shown when a savegame is loaded that requires certain switches to be enabled. It is not easily possible to tell which switches these are, unfortunately. As of version 2.0, this message is shown when the savegame contains extended town data but they're not enabled in TTDPatch. See [[MoreTownStatistics| More Town Statistics]].

;loadgame="Load game\00": Load menu item in the disk menu

;gotodepot="Go to \80\00":

;gotodepotonly="Service at \80\00":

;gototraindepot="\80 Train Depot\00":

;gotoroaddepot="\80 Road Depot\00":

;gotoshipdepot="\80 Ship Depot\00":

;gotoairdepot="\80 Hangar\00": Display of depots in vehicle orders with the "gotodepot" switch.

;cannotcheat="\94Cannot carry out sign cheat action\00":

;cheatinvalidparm="\94Invalid parameter\00":

;cheatunknown="\94Unknown sign cheat\00":

;cheatobsolete1="\94Note: Cht: \80 is obsolete.\00":

;cheatobsolete2="\94Use Cht: \80 instead.\00": Various error messages about sign cheats.

;managedby1=" (temp. Player 1)\00":

;managedby2=" (temp. Player 2)\00":

;manage="\98Manage\00": Display of current player status and the "manage" button in the player info window when using the subsidiary management feature.

;newwagoninfo="\98Cost: \7f Weight: \7ct\n"

"Capacity: \80\00":

;railwaywagon="railroad wagon\00":

;monorailwagon="monorail wagon\00":

;maglevwagon="maglev wagon\00": Description of wagons when they become newly available.

;rvweightinfo="\98Weight: \95\7c.\7dt \98Power: \95\7chp \80\00":

;rvweightpurchasewindow="\98Cost: \8a\7f\98 Speed: \8a\84\n"

"\98Running Cost: \8a\7f/yr\n"

"\98Power: \8a\7chp\98 Weight: \8a\7d.\7dt\n"

"\98Capacity: \8a\80\n"

"\98Designed: \8a\7e\98 Life: \8a\7c years\n"

"\98Max. Reliability: \8a\7d%\00": Description of road vehicle stats when using realistic acceleration, first in the vehicle info window, then the purchase window.

;grfloaderror="\94Error loading new graphics:\00":

;toomanysprites="\94More sprites than specified (file \80).\00":

;outofmemory="\94Out of memory (file \80).\00":

;wronggrfversion="\94Wrong .grf version (file \80).\00":

;toomanyspritestotal="\94Cannot load more sprites (from file \80).\00":

;filenotfound="\94File \"\80\" not found.\00":

;invalidsprite="\94File \"\80\" has invalid sprite #\7c.\00": Error messages shown when loading new graphics fails.

;elecrailconstitle="\94Electrified Railroad Construction\00":

;elecrailconsmenu="Electr. railroad construction\00": Construction menu entry and window title for electrified railroad construction.

;ufodestroyed="\98\0f'UFO' destroyed in huge explosion near \80!\00":

;lmilloutoftrees="\98\0f\80 \80 ran out of nearby trees!\00":

;eurointroduced="\98\0fMonetary union!\n\n"

"European countries switch from national currencies to Euro!\00":

;aircraftcleared="\98\0fRemnants of the recent plane crash have been cleared from \80!\00":

;zeppelincleared="\98\0fRemnants of the recent Zeppelin crash have been cleared from \80!\00":

;traincleared="\98\0fRemnants of the recent train crash have been cleared near \80!\00": News messages about various events.

;curr_HUF="Hungarian Forint (Ft)\00\00\00\00\00\00":

;curr_PLN="Polish Zloty (zl)\00\00\00\00\00\00":

;curr_ATS="Austrian Shilling (ATS)\00\00\00\00\00\00":

;curr_BEF="Belgian Franc (BEF)\00\00\00\00\00\00":

;curr_DKK="Danish Krone (DKK)\00\00\00\00\00\00":

;curr_FIM="Finnish Markka (FIM)\00\00\00\00\00\00":

;curr_GRD="Greek Drachma (GRD)\00\00\00\00\00\00":

;curr_CHF="Swiss Franc (CHF)\00\00\00\00\00\00":

;curr_NLG="Dutch Guilder (NLG)\00\00\00\00\00\00":

;curr_ITL="Italian Lira (ITL)\00\00\00\00\00\00":

;curr_SEK="Swedish Krona (SEK)\00\00\00\00\00\00":

;curr_RUB="Russian Rubel (RUB)\00\00\00\00\00\00":

;curr_EUR="Euro (\9e)\00\00\00\00\00\00": Definition of new currencies, see the next section for details.

;townlastmonthaccepted="\98Cargo accepted last month at all stations:\00": Display of more town statistics using "moretownstats".

;endofsharedorders="\01\0a- - End of shared orders - -\00": End of a shared order list.

;hotkeylistdos="x !@#$t%1234567890==\1e\\\00":

;hotkeylistwin="x !@#$t%1234567890==`\\\00": List of new hotkeys for the DOS and Windows version. The first four characters are reserved. After this follow six characters which toggle display options, and finally 14 characters for the fourteen construction items in the railway construction menu. If the second character (the first after the "x") is a question mark "?", it will turn on the key code display, meaning that every time you press a key in TTD, it will display what key it thinks that was, so that you can find out what character to use in the hotkey list. Note that the control codes are not placeholders here, but keycodes.

CustomIngameTexts

2011-06-15T11:32:04Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Custom in-game texts=

Translating the new in-game texts

TTDPatch adds several new messages that are displayed in the game, for example the bribe option. TTDPatch includes translations of these in all languages that TTD is available in. However, you may have used the TTD Translator described in the previous section, in which case your TTD is in a language that is not available with TTDPatch. As a result, the in-game texts will be in English (or whichever language your version of TTD was originally in), not your language.

It is now possible to translate these in-game texts to your own language by using the <tt>mkpttxt.exe</tt> program distributed with TTDPatch. Simply run this program once, and it will create a file called <tt>ttdpttxt.txt</tt>, which contains all in-game text strings.

To translate it, open it in a Windows editor like Notepad, or any other editor that is capable of using the ISO-8859-1 character set. Follow the instructions at the beginning of the file, and translate the entries. Then, simply run <tt>mkpttxt.exe</tt> again, and it will create the file <tt>ttdpttxt.dat</tt>, which will automatically be loaded by TTDPatch if it is present in the TTD directory.

If you would like to distribute your translations, please distribute the <tt>ttdpttxt.txt</tt> and not <tt>ttdpttxt.dat</tt>, because the latter uses an internal format of TTDPatch that may change from time to time. If the format changes, people who have the <tt>.txt</tt> file can simply run an updated version of <tt>mkpttxt.exe</tt>, which isn't possible with the <tt>.dat</tt> file.

TranslatingTTDPatch

2011-06-15T11:31:54Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Translating TTDPatch=

How you can translate TTDPatch into your language.

TTDPatch is available in a variety of languages. To choose a language, please refer to [[LanguageSelection| Language Selection]].

It is very easy to add more languages. I just need people who are willing to translate either the program texts or the documentation, or both. For translating the program output, download the [http://www.ttdpatch.net/src/ttdptlng.zip| program texts] for all languages that TTDPatch has been translated to. Please change only the text that is in double quotes, the comments should remain the way they are, to make things easier for me.

I'm using [http://texinfo.org/| Texinfo] for the manual itself, which makes it possible to have a single file that can easily be converted into a pretty-print file (Postscript or PDF) as well as HTML for online documentation and a nicely formatted plain text file. If you want to translate the documentation, it would help if you know Texinfo, but it's pretty easy to figure out, so you shouldn't have a problem translating it.

If you have any questions about this or would like to help translate it, please contact Josef, see [[ContactInformation| Contact Information]].

You can get the current version of the manual in Texinfo format from the [http://www.ttdpatch.net/src/manual.zip| TTDPatch source code page].

For translating TTD itself, Csaba Varga has written the excellent [http://www.csucsposta.hu/csaboka/ttdtrans.htm| TTD Translator].

FrequentlyAskedQuestions

2011-06-15T11:31:44Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Frequently Asked Questions=

Look here: [http://wiki.ttdpatch.net/tiki-list_faqs.php]

TTDPatchMailingLists

2011-06-15T11:31:34Z

Pm-bot: Bot: Automated text replacement (--= +==)

=TTDPatch Mailing Lists=

The mailing lists about TTDPatch

The TTDPatch mailing lists are email lists that allow you to discuss TTDPatch with other list subscribers, as well as ask questions about the patch and keep up to date with the latest developments of the patch.

Note that if you have questions about the patch or need help, there are other ways than the mailing lists described in the previous section. Use whichever you find the most convenient.

There are three mailings lists for TTDPatch:

;ttdpatch: The general topic list for questions, comments, general discussion and so on. Anyone who is subscribe can contribute. All messages to the announcements lists are copied to this list as well. This is a high volume list, with on average about 5-10 messages per day.

;ttdpatch-announce: TTDPatch announcements only. A message is posted to this list whenever a new version of TTDPatch comes out, as well as general news and announcements about the patch and related utilities. This list is moderated, which means that only messages which are genuine announcements will be posted. It is low volume, with usually no more than one message per week.

;ttdpatch-digest: Digested version of the above lists. All messages sent to either the general or the announcements list will be digested, and a digest is sent out on average every 30 messages, or three days after the first message in the digest, whichever comes first.

The lists are archived at [http://lists.ttdpatch.net/]. It is often a good idea to search or browse the archive to see if your question has been answered already.

|-
|If you want to ask a question or contribute to the lists, you need to subscribe to them. To do that, send a message to [mailto:Majordomo@ttdpatch.net||Majordomo@ttdpatch.net], with the following in the message ''body'':<pre>subscribe <list name></tt>

<tt>end</pre>

Here, the list name can be any of the above lists. For example, to subscribe to the digest list, put the following in the email body:<pre>subscribe ttdpatch-digest</tt>

<tt>end</pre>

You only need to subscribe to one of the lists, because all announcements are copied to the "ttdpatch" list as well, and the digests contain message from both lists too.

Instead of composing the email yourself, you can try the following links, which should open your email program with an appropriate message, so that all you have to do is click the send button:
*[mailto:Majordomo@ttdpatch.net?Body=subscribe%20ttdpatch%0Aend%0A| Subscribe to the general topic list]
*[mailto:Majordomo@ttdpatch.net?Body=subscribe%20ttdpatch-announce%0Aend%0A| Subscribe to the announcements list]
*[mailto:Majordomo@ttdpatch.net?Body=subscribe%20ttdpatch-digest%0Aend%0A| Subscribe to the digested list]

All emails to the announcements list are tagged so that you can filter the already infrequent messages you're not interested in. The subject line will look like this:<pre>Subject: Beta: TTDPatch 2.0 beta 4 released</pre>

Here's a list of the possible tags:

;Alpha, Beta, Release: Announcements of a new alpha, beta or release version of TTDPatch.

;Related: Messages regarding programs related to TTDPatch, such as configuration utilities

;Announce: A general announcement about changes in the mailing lists; about policies, new lists etc.

;News: General news about TTDPatch

Help

2011-06-15T11:31:24Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Help=

Where to get help with TTDPatch

So, you have tried TTDPatch and it didn't work like it should? You need some help getting it to work?

You've already found a good way to get help, namely this manual itself. If you can't find what you're looking for, a good place to start is to search the site (see the box at the left). Just try to think of a keyword that might relate to your question.

Also, you might try reading the FAQ section just below, it has answers to many common questions.

There are also a few ways of asking other people for help:
*Mailing list: If the FAQ or the manual don't answer your questions, you can post to the mailing list, see [[TTDPatchMailingLists| TTDPatch Mailing Lists]] in the next section.
*Official TTDPatch forum: You can ask your question on the official [http://www.tt-forums.net/| TTDPatch forum].
*Newsgroup: If you have access to Usenet, ask your question on the Transport Tycoon newsgroup [news:alt.games.microprose.transport-tyc| alt.games.microprose.transport-tyc].
|-
|*IRC: There's the [irc://irc.quakenet.org/tycoon||#tycoon] channel on Quakenet as well, see also [[TheIrcChannel]].

Finally, if all else fails, you can of course contact the author, see [[ContactInformation| Contact Information]]. Note that this is usually the ''slowest'' way to get answers, because Josef is very busy working on the patch...

DebugSwitches

2011-06-15T11:31:14Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Debug switches=

Modifying how TTDPatch works

Debug switches are not useful for most people, but they can sometimes help fixing odd problems in the patch. They are mostly intended to be used by developers when testing the patch.

To use them, they must be the first switch on TTDPatch's command line, and start with an exclamation mark, "!". After the exclamation mark follows the list of debug switches, each of them possibly trailed by a "+" or "-" to choose two different modes of operation. Currently if neither "+" nor "-" is specified, "+" is assumed. An example:<pre>ttdpatch.exe -!v+T+w-</pre>

This would run TTDPatch to collect new version information and terminate before even starting TTD. If any warnings occur, they are ignored.

Alternatively, since revision 798 debug switches may be specified in the configuration file: <pre>debugswitches v+T+w-</pre>

Here's the complete list of debug switches:

{|
!Switch !!Meaning

|-
|v- ||Ignore TTD version info stored with TTDPatch (i.e. do not recognize TTD version)

|-
|v+ ||Collect TTD version info and write to a file

|-
|s- ||Never swap out the real mode code when starting TTD (DOS only)

|-
|s+ ||Always swap out the real mode code when starting TTD (DOS only)

|-
|c ||This switch is very special: if specified, TTDPatch will not process the command line options as usual, instead it will treat the rest of the command line as name and arguments of a program to run. This feature can be used to analyze TTDPatch's memory usage in the DOS version.

|-
|t- ||Assume <tt>TTDLOAD(W).OVL</tt> exists and is correct, don't process it or try to locate the original files. Currently this is useful only if combined with the c debug switch, otherwise it'll prevent TTDPatch from working and may cause a crash.

|-
|m- ||Run even if there's not enough memory to start TTD (DOS only)

|-
|f- ||Don't read or create the default <tt>ttdpatch.cfg</tt>

|-
|a- ||Don't check dependencies between switches. If used, TTDPatch will not correct illegal combinations of switches. Warning: some switch combinations are dangerous. For example, if startyear is set to 1927 and generalfixes to off, TTD will probably hang when you try to start a new random game. Normally, i.e. without this debug switch, TTDPatch would prevent that by turning generalfixes on. See [[NewStartingYear| New Starting Year]] for more information.

|-
|w- ||Do not wait for a key after a warning message, just continue

|-
|w+ ||Do not wait for a key after a warning message, just abort

|-
|o+ ||Reorder all switches alphabetically when writing a configuration file, not only the new ones

|-
|T- ||Terminate TTDPatch after parsing the cfg/cmdline (only TTDPatch 2.0.1 alpha 51 or higher)

|-
|T+ ||Terminate TTD immediately after collecting version information (see v+)

|-
|L+ ||Load language data from the file named <tt>language.dat</tt> instead of the TTDPatch executable. Useful in debugging because many debuggers fail to load symbol information with those data appended to the executable.

|-
|C+ ||Load patch code from <tt>loaderd.bin</tt> and <tt>ttdprotd.bin</tt> for DOS or <tt>loaderw.bin</tt> and <tt>ttdprotw.bin</tt> for Windows. Useful in debugging because many debuggers fail to load symbol information with that code appended to the executable.

|-
|R+||Load relocation information from <tt>relocd.bin</tt> for DOS or <tt>relocw.bin</tt> for Windows. Useful in debugging because many debuggers fail to load symbol information with that code appended to the executable.

|-
|I- ||Prevent the enhanced keyboard handler from updating keyboard LED indicators. The Lock keys will still toggle internal flags, though. (DOS only)

|-
|S+ ||Dump information about all supported switches (non-debug, non-special ones) to swtchlst.txt and abort

|-
|S-||Write current patch version and switch information in XML format to switches.xml and abort (only TTDPatch 2.0.1 alpha 21 or higher)

|-
|P+||Don't check ttdpatch.dll to see if it needs to be updated.

|-
|n+ ||Use noregistry information from registry.ini

|-
|n- ||Do not use noregistry information

|-
|r||Do not run TTDLOAD(W).OVL directly (since 2.5 beta 9)
|}

EnhancedKeyboardMapping

2011-06-15T11:31:04Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Enhanced Keyboard Mapping=

Remapping key combinations in TTD

TTD uses its own character set, which is a modification of the ISO-8859-1 (also known as Latin-1) character set with some less useful characters replaced with special symbols. For the most part, this set matches the Windows Western code page (Windows-1252), so e.g. accented letters may be entered directly in the Windows versions of TTD as long as your keyboard layout supports them. However, it doesn't work that well if you want to translate TTD (see [[TranslatingTTDPatch| Translating TTDPatch]]) to a language not covered by the Western set, like Czech or Polish, and you're going to modify TTD's character set to support characters that occur in those languages. Non-Western Windows code pages are, unfortunately, more or less incompatible with TTD. For instance, some letters that occur in Czech are mapped by Windows to character codes that TTD uses to change color of text.

A similar problem occurs with the Euro character (see [[MoreCurrenciesAndEuro| More Currencies and Euro]]), which in most Windows code pages is mapped to the code 128; but that code has special meaning in TTD, so no character may be mapped to it, and therefore TTDPatch maps the Euro glyph to the unused code 158. Unfortunately this means you have to resort to key combinations like Alt-0158 if you want to enter the Euro character into e.g. the name of a savegame, even if the Euro character is directly supported in your keyboard layout.

The problem is even more severe in the DOS versions of TTD, which have hardcoded and sometimes very restricted keyboard mappings (in particular, the French version is notorious for missing the colon (:) key mapping), and have no support for key combinations involving the right Alt key, common in many European locales.

Therefore, since version 2.0 TTDPatch supports keyboard remapping. To enable this feature, first you have to get (or create yourself) the keyboard remapping file, <tt>ttdpatch.kbd</tt> for the DOS version or <tt>ttdpatchw.kbd</tt> for the Windows version. Simply place that file in the TTD directory, and TTDPatch will load it and enable its '''enhanced keyboard handler'''.

The keyboard remapping file is a binary file; the DOS version and the Windows version use a different format. You may download a sample file from the TTDPatch website at [http://www.ttdpatch.net/kbd-sample.zip], which contains a detailed description of the file formats as well.

DOS versions of TTD feature its own low-level keyboard handler, so TTDPatch's enhanced keyboard handler is more powerful in the DOS version, allowing the user to remap virtually any key or key combination. Windows versions of TTD rely on the Windows keyboard driver to map keys to characters, so the Windows version of TTDPatch offers a more simple character-based remapping.

When the enhanced keyboard handler is active, some bug fixes are activated even if the generalfixes switch is disabled (see [[GeneralFixes| General Fixes]]), and some aspects of the keyboard interface change, which is explained in detail in the sample file mentioned above.

In the DOS versions, if the enhanced keyboard handler is active, the three Lock keys (Num Lock, Caps Lock, Scroll Lock) toggle the LED indicators on the keyboard, as they normally do in DOS and Windows. This works even if <tt>ttdpatch.kbd</tt> is empty; however, TTD normally ignores the states of the Lock keys anyway, so if proper key mappings are not defined in <tt>ttdpatch.kbd</tt>, this feature is rather useless.

The enhanced keyboard mapping can work together with the morehotkeys switch (see [[MoreHotkeys| More Hotkeys]]) and the `ttdpttxt' mechanism (see [[CustomIngameTexts| Custom in-game texts]]). The keyboard remapping file defines which keys (or combinations) translate to which characters, while the `ttdpttxt' mechanism decides which characters trigger which functions if morehotkeys is turned on.

RealisticAcceleration

2011-06-15T11:30:54Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Realistic Acceleration=

How the new realistic acceleration is calculated

Here you'll find out how exactly the train acceleration is calculated if you enable realistic acceleration (see [[NewCurveAndMountainHandling| New Curve and Mountain Handling]]).

This realistic model takes into account physical properties of the train, such as engine weight, total train weight, power and tractive effort. It is of course not 100% realistic, because it doesn't support details such as a realistic torque curve, powered wheel arrangements and bogie types (although vehicles defined by new graphics sets can set this correctly), and other things that TTD knows nothing about. It had to work within the description of engines offered by TTD. As such, it assumes that the engines always operate at optimum torque, and ignores the differences between steam, diesel and electric propulsion (for example that usually not all wheels of a steam engine are powered, unlike most electric engines. Again, this is not necessarily true for new vehicle sets).

The result is thus not perfectly realistic, but it is reasonably close. It's certainly close enough that the train acceleration "feels" more realistic. For example, effects such as friction and air drag (enhanced in tunnels) are taken into account. Therefore very heavy trains may not reach their stated top speed at all, or be able to make it up a steep hill. The acceleration also decreases the faster a train is, so that it will accelerate very quickly in the beginning, but then take a long time to reach its top speed, just like a real train.

The basis of the calculation is the maximum force that can be generated by the engine. This is using an idealistic model of constant power, or equivalently, constant torque, which is close enough to reality though, for most real engines:

<pre>TE{SUB()}eng{SUB} = P / v</pre>

TE{SUB()}eng{SUB} is the maximum force generated by the engine in Kilonewtons, P is the power in Kilowatts and v is the speed in m/s. Of course the patch has to do a conversion from TTD's units.

After this, the patch calculates the maximum tractive effort that the engine can exert on the rails. This depends on its adhesive weight (i.e. the weight resting on powered axles), and the coefficient of friction on steel:

<pre>TE{SUB()}max{SUB} = W{SUB()}adh{SUB} * µ</pre>

TE{SUB()}max{SUB} is the maximum tractive effort in kN, W{SUB()}adh{SUB} = m{SUB()}adh{SUB} * 9.81 is the total adhesive weight in kN, and µ = 0.30 is the coefficient of friction for steel on steel as used by TTDPatch.

The actual tractive effort is then the lower of the two values:

<pre>TE = min (TE{SUB()}eng{SUB}, TE{SUB()}max{SUB}) </pre>

This is then added up for all powered vehicles in the consist, which gives the total tractive effort shown in the vehicle speed window if you have enabled that, see below.

From the total tractive effort, the patch subtracts the loss forces of static/kinetic friction, rolling friction and air resistance, and any tangential forces from an inclined track to arrive at the net force:

<pre>F{SUB()}net{SUB} = TE{SUB()}effective{SUB} - c0 * W - c1 * W * v - c2 * v² - F{SUB()}incl{SUB}</pre>

F{SUB()}net{SUB} is the net force in kN, W is the total weight of the train in kN, c0 is the coefficient of static/kinetic friction, c1 is the coefficient of rolling friction, c2 is the coefficient of air resistance and F{SUB()}incl{SUB} includes the tangential forces of inclined track.

For c0 and c1 the patch uses the same values for all trains. These values were chosen to give a realistic feeling to the acceleration, and not strictly derived. The reason for that is that TTD doesn't have a consistent time scale, so that it is impossible to calculate the values of such constants. c2 depends on the top speed of the engine, to account for the fact that faster engines are usually streamlined. Roughly speaking, an engine that has twice the top speed than another engine is considered to have half the air resistance.

The incline forces are calculated as a sum over all train vehicles:

<pre>F{SUB()}incl{SUB} = sum [ W[i] * sin(theta[i]) ] </pre>

W[i] is the weight of the i'th vehicle and theta[i] is the slope of the incline for that vehicle.

The slope is taken to be either -5%, 0% or +5%, depending on whether the vehicle is moving downhill, flat or uphill.

Finally, once the net force is known, the patch can calculate the train acceleration:

<pre>a = F{SUB()}net{SUB} / m </pre>

a is the acceleration in m/s² and m is the total mass of the train in kg.

And that's the final acceleration value used to calculate the increase in train speed from one engine tick to the next.

If you are interested, you can see the resulting values for tractive effort and acceleration by using custom patch texts, see [[DetailedInformation| Detailed Information]]. You need to modify the "headingfor" entries to have them show tractive effort and acceleration. For example, use the following format:

<pre>headingfor="\95\80, \84, TE=\7c kN, a=\7c\00"</pre>

This shows the tractive effort (TE) in Kilonewtons, and the acceleration (a) in cm/s². The unit of acceleration is cm/s² because it is usually very small, and TTD cannot easily show decimals. It is only used if "showspeed" is on. Note that this can sometimes make the status bar text too wide to fit in the window, if that annoys you, you will have to remove these displays again.

NewTownGrowthSwitchesdetails

2011-06-15T11:27:44Z

Pm-bot: Bot: Automated text replacement (--= +==)

=New Town Growth Switches (details)=

How the new town growth switches work

This section describes the switches that apply in "towngrowthratemode 2". They fine tune and control every detail of town growth.

As described in the previous section, TTD internally uses an inverse growth rate, i.e. the number of 70-tick time units between attempts to build a new house. However, the enhanced rate calculation uses a direct growth rate, defined as the average number of new town buildings per 38400 time units, which is approximately 100 years. At the end of calculations this rate is converted to the inverse growth rate. If the inverse growth rate is greater than 255, it's reduced and town growth is blocked randomly to have the same effect on the average.

For comparison, with "towngrowthratemode 0" (TTD's original calculation), the rates are:

{|
!number of active stations!!average rate (new houses per 100 years)

|-
| 0 ||20

|-
| 1 ||182

|-
| 2 ||256

|-
| 3 ||349

|-
| 4 ||480
|}

or, if a building fund is active, the rate is fixed at 640 new houses per century. These rates are as they're normally in TTD, except that a bug with 5 or more stations (see the previous section) is fixed.

For the new growth rate calculation, we have the maximum and minimum rate, the towngrowthratemin and towngrowthratemax switches. Let <tt>''ratediff''</tt> be the difference between the maximum and the minimum, i.e. ratediff = towngrowthratemax - towngrowthratemin</pre>

Then the '''base rate delta multiplier''' (BRDM) is calculated as follows: BRDM = (AS*ASW + PO*POW + MO*MOW + PI*PIW + MI*MIW + GI*GIW + FI*FIW + WI*WIW + SI*SIW + DI*DIW)</tt>

<tt> / (ASW + POW + MOW + PIW + MIW + GIW + FIW + WIW + SIW + DIW)</pre>

where the two-letter abbreviations represent '''growth boost components''' (explained in detail below) depending on, respectively:

{|
!<tt>''AS''</tt> !!the number of active stations

|-
|<tt>''PO''</tt> ||percentage of passengers transported (`passengers out')

|-
|<tt>''MO''</tt> ||percentage of mail transported (`mail out')

|-
|<tt>''PI''</tt> ||incoming passengers (`passengers in')

|-
|<tt>''MI''</tt> ||incoming mail (you get the picture...)

|-
|<tt>''GI''</tt> ||incoming goods

|-
|<tt>''FI''</tt> ||incoming food

|-
|<tt>''WI''</tt> ||incoming water

|-
|<tt>''SI''</tt> ||incoming sweets/candy

|-
|<tt>''DI''</tt> ||incoming fizzy drinks
|}

Each component is a number between 0 and 1, so the result (BRDM) is also between 0 and 1. The rest are weighting factors, represented by the following settings in the configuration file:

{|
!<tt>''ASW''</tt> !!tgractstationsweight

|-
|<tt>''POW''</tt> ||tgrpassoutweight

|-
|<tt>''MOW''</tt> ||tgrmailoutweight

|-
|<tt>''PIW''</tt> ||tgrpassinweight

|-
|<tt>''MIW''</tt> ||tgrmailinweight

|-
|<tt>''GIW''</tt> ||tgrgoodsinweight

|-
|<tt>''FIW''</tt> ||tgrfoodinweight

|-
|<tt>''WIW''</tt> ||tgrwaterinweight

|-
|<tt>''SIW''</tt> ||tgrsweetsinweight

|-
|<tt>''DIW''</tt> ||tgrfizzydrinksinweight
|}

The higher the weighting factor for some component is relative to the other weighting factors, the more influence the asociated growth boost component has on the final growth rate. Note that it's the relation betwen weighting factors that matters; for instance, if all the other weighting factors are zero, the following set tgractstationsweight = 10</tt>

<tt> tgrpassoutweight = 5</pre>

yields exactly the same results as tgractstationsweight = 2</tt>

<tt> tgrpassoutweight = 1</pre>

The growth boost components are calculated as follows:

;<tt>''AS''</tt> = [[NTB / tgrtownsizebase) * TSF) + (1 - TSF]]</pre>

where <tt>''NTB''</tt> is the number of buildings in the town and <tt>''TSF''+==tgrtownsizefactor/255 (i.e. it's a value between 0 and 1, which determines how much of the growth rate depends on the town size, in percent). This can be used to add a bit of `exponentiality' to the growth of towns (remember, the growth rate is expressed in new buildings per time unit, so with a constant rate larger towns will appear to grow more slowly).

Then the '''real growth rate''' is calculated: RGR = towngrowthratemin + ratediff*CRDM</pre>

where <tt>''CDRM''+===+''RDM''</tt> if <tt>''RDM''</tt> <= 1, and <tt>''CRDM=1''</tt> otherwise.

Then, if a town building fund is active in this town, 600 is added. Then, if the town is one of those supposed to be larger (see the largertowns switch), the rate is doubled. And ''this'' is the final growth rate, in new houses per century.

As a final note, the real growth of towns is a second- or third-order effect of the final growth rate, so don't expect towns to grow exactly at the rate you've calculated from the formulae above.... But on the average it shouldn't be far off.

TTDTownGrowth

2011-06-15T11:27:34Z

Pm-bot: Bot: Automated text replacement (--= +==)

=TTD Town Growth=

How towns grow in regular TTD

This is very technical, and only required if you want to fine-tune your town growth. Otherwise, you can skip over this and the next section.

The basic time unit in TTD is a "tick". In the following, it will be used to describe how often something happens. A tick of the simulation engine takes ca. 27 ms, if your computer is fast enough, otherwise it takes as long as necessary. One TTD day is ca. 74 ticks, which is about 2 seconds of real time on fast enough computers.

The "expansion state" of a town is determined by two fields in town structure: bit 0 in the word at the offset 0x12 (I'll call it the <tt>growth_flag</tt>) and the byte at 0x0A (<tt>idle_countdown</tt>):

{|
!<tt>growth_flag</tt> !!<tt>idle_countdown</tt> !!state

|-
|0 ||any ||blocked

|-
|1 ||0 ||expanding

|-
|1 ||nonzero ||idle
|}

Town status update (including expansion) is performed on every tick in a round-robin fashion; since the town array can hold 70 entries, the main town status update procedure is called every 70 ticks for each town. If the town is blocked, nothing happens. If it's idle, <tt>idle_countdown</tt> is decremented. If it's expanding, an attempt to place a new building or a piece of road (or a bridge) is taken; if it succeeds, the expansion state is changed to idle by setting <tt>idle_countdown</tt> to the byte at 0x39, from now on referred to as <tt>growth_delay</tt> (extension of an existing road usually doesn't change the state to idle). Therefore, <tt>growth_delay</tt> determines how often the town will be in the expanding state, and thus is the ''inverse'' growth rate of the town. Smaller values of <tt>growth_delay</tt> mean faster growth.

<tt>growth_delay</tt> is reset each month, and depends on the number of "active" stations within town's transport zone as follows:

{|
!number of !!<tt>growth_delay</tt>

|-
|"active" stations ||normal ||funded[1] ||funded[2]

|-
| 0 || 160 [3] || 60 || 60

|-
| 1 || 210 || 60 || 60

|-
| 2 || 150 || 60 || 60

|-
| 3 || 110 || 60 || 50

|-
| 4 || 80 || 60 || 40

|-
| 5 or more || 11 [4] || 60 || 30
|}

Footnotes:

{|
![1] !!When a town building fund is active (i.e., up to 3 months after using the "Fund new buildings" option).

|-
|[2] ||When a town building fund is active and "towngrowthratemode" is set to 1.

|-
|[3] ||In this case the town is blocked with a 11/12 probability, so the effective mean <tt>growth_delay</tt> is 1920.

|-
|[4] ||This is a bug in TTD (array overrun). TTDPatch now fixes this if any of "generalfixes", "towngrowthratemode" or "towngrowthlimit" is active. If "towngrowthratemode" is 0 or off, <tt>growth_delay</tt> is set to 80 (which seems to be the original programmer's intention); if "towngrowthratemode" is 1, it's set to 55.
|}

Apart from the random blocking in the case [3], town growth is also blocked:
*in the sub-arctic climate, if the central tile of the town is above the snow line, and no food has been delivered to the town in the last month;
*in the sub-tropical climate, if the central tile of the town is in desert, and no food or no water has been delivered to the town in the last month.

The switches townminpopulationsnow and townminpopulationdesert may be used to prevent blocking of towns with population less than some threshold, so they get a chance to grow enough to accept food.

If "largertowns" is active, <tt>growth_delay</tt> is halved for selected towns, making them grow twice as fast (except in the case [3] above, so transport is still necessary to make towns grow; this is different if "towngrowthratemode" is 2, as explained in the next section).

A station is "active" if any cargo has been picked up or accepted there within the last 50 days. The type of cargo is irrelevant, so if there's a coal mine in the middle of a town and you're picking up coal there, it will contribute to the growth of the town. This also means that many single-facility stations make a town grow faster than one multi-facility station, as long as they're serviced regularly.

The town's transport zone is a circular area around the town's central tile. Its radius (in tiles) is a function of the number of town buildings as follows:

{|
!number of town buildings !! radius of transport zone

|-
|0--3 ||2

|-
|4--7 ||4

|-
|8--11 ||5

|-
|12--15 ||6

|-
|16--19 ||7

|-
|20--35 ||8

|-
|36--71 ||9

|-
|72 or more ||0
|}

Notice the last row. If there are more than 71 town buildings, the transport zone vanishes and stations no longer contribute to the growth. However, if "towngrowthlimit" is enabled, TTDPatch changes this by extrapolating the function for larger values.

Also note that the internal number of buildings may be incorrect in games save under old versions of TTDPatch or without TTDPatch, due to the bugs mentioned in [[GeneralFixes| General Fixes]]. However, this is not a big problem since TTDPatch recalculates these numbers (and populations) if the extended town data are enabled (see [[MoreTownStatistics| More Town Statistics]]) and the game without those data is loaded, and all the new town growth switches do enable the extended town data.

The function called if a town is in the expanding state starts by searching for a piece of road in the vicinity of town's centre. If no road is found, an attempt is made to create it. If a road piece is found, the function randomly `walks' along the roads trying to find a place to create a new house, or possibly branch out a new street or extend an existing one. Normally, this walk is limited to 20 steps (where a tunnel counts as one step), which limits the maximum possible extents of a town. The "towngrowthlimit" switch modifies this value.

Regardless of all the town growth processing mentioned above, each town building's status is updated periodically (every 256 ticks). This includes construction progress and "production" of passengers and mail. If the town the building belongs to is not blocked, this also includes destroying the building (and, with 61/64 probability, immediately building a new one in its place) at random intervals. This process is not controlled by <tt>growth_delay</tt> or any of the new town growth switches, althought is does indirectly affect the growth of a town.

CompanyColorSelection

2011-06-15T11:27:24Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Company Color Selection=

Advanced company color selection

{picture file=img/wiki_up/2cc.png}

This window, enabled by the [[EnhancedGraphicalUserInterface| enhanced graphical user interface]] switch, allows a more sophisticated selection of color schemes.

The global color scheme at the top applies to everything that doesn't have any different settings from the tabs below, including stations, fences and all company windows.

To enable different colors for certain vehicle types, simply tick the checkbox for the type and select the color scheme you like. Note that the secondary color is only available for vehicle sets which make use of it; TTD's default vehicle graphics have no secondary color. In that case, the setting here is ignored.

Note that train wagons belonging to a train set (i.e. having a livery override for the current engine) will always use the colors of the engine, regardless of whether they transport freight or not.

GRFAuthorHelperWindow

2011-06-15T11:27:14Z

Pm-bot: Bot: Automated text replacement (--= +==)

=GRF Author Helper Window=

In-game adjustment of real sprite offsets.

This is what it looks like:

{picture file=img/wiki_up//GRFHelper.png}

This window is accessed by selecting a grf file in the [[GRFStatusWindow]], and then control-clicking on the information area--the section that contains the description of the GRF.

Click on the sprite button, and enter the number (decimal) of the sprite you want to adjust. If a pseudosprite is specified, the Sprite: ... line will not appear. Assuming a real sprite is specified, the selected sprite will then be shown in the lower portion of the window. Adjust the xrel and yrel values with the four +/- buttons. Changes are applied immediately, and the sprite in the window will move to reflect the new xrel and yrel values.

Once you have found the correct values, replace the bogus values in your grf with the correct values, and re-encode.

Note: Action A replacement real sprites aren't supported.

This feature was contributed by Oskar Eisemuth.

GRFStatusWindow

2011-06-15T11:27:04Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Graphics Status Window=

This is what it looks like:

{picture file=img/wiki_up//grfstatus.png}

The flags and symbols have the following meanings:

{|
!{picture file=img/wiki_up//grfstat_green.png} Graphics set is currently active in the game

{picture file=img/wiki_up//grfstat_red.png} Graphics set is currently inactive in the game

{picture file=img/wiki_up//grfstat_blue.png} Graphics set is special and can only be activated/deactivated by the corresponding patch switch

{picture file=img/wiki_up//grfstat_orange.png} Graphics set conflicts with another set and was disabled temporarily

{picture file=img/wiki_up//grfstat_gray.png} Graphics file is faulty and was disabled

|-
|{picture file=img/wiki_up//grfstat_err.png} This symbol marks error or warning messages, select the set to display the message
|}

By clicking on a red or green flag, you can switch the activation state of that set. Note that you still can't activate sets for the wrong climate or incompatible sets.

When you're happy with your selection, click the "Apply" button to apply the changes to the current game. Note that those changes will only be saved if "saveoptionaldata" is on.

If you click on "Default", the selection is reset and all graphics are reset to the default. Note: this also applies the default selection immediately and cannot be undone!

==Title Screen Settings==

Since 2.0.1 alpha 57, you can access the Graphics Status Window from the title screen by opening the game options menu. This allows you to choose which graphics sets should be active in a new random game. It does not apply to savegames or pre-existing scenarios.

There are a few differences between the regular window and the title screen version that are explained below:
* After you change the new game climate, the selection will be reset when opening the window
* If you change the climate after closing the window, the settings will not apply to the new game
* You must manually close the window, or the settings may not apply to the new game
* Clicking "default" will reset the selection to the default for the chose climate
* The "apply" button is unavailable, because it would apply the settings to the title screen

In summary, choose the climate first, then open the Graphics Status Window and choose your settings, then make sure to close the window, and finally start a new game.

EnhGUIWindow

2011-06-15T11:26:54Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Enhanced GUI Window=

This is what it looks like:

{picture file=img/wiki_up//enhguiwindow.png}

You can access it from the toolbox menu in TTD.

==Station signs==

Here you can choose transparent or regular, "TTD style" station signs.

==Depot Size==

This sets the width of the train depot windows.

==Depot allTrash==

When enabled, this means everything in a depot outside the main train list area will act like the trash bin. You can then sell train vehicles by moving them onto the title bar for example.

==Stick Settings==

Save these settings with the current game. Only works if "saveoptionaldata is on".

==Unstick==

Remove these settings from being save with the current game.

==Save as default==

Make these settings apply to all games which haven't had settings saved with them.

GraphicsErrors

2011-06-15T11:26:44Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Graphics Errors=

Because of a limitation in the amounts of graphics TTD can load you might get error messages. Troubleshooting deals with problems concerning the installation of grf-files. There shouldn't be problems after succesfully installing new graphics from an executable.

==Troubleshooting==
* Always make sure you have TTDPatch switches enabled (see [[NewVehicleGraphics| New Vehicle Graphics]])
* Check if you downloaded the correct version. Remember that DOS graphics don't work with the Windows version and v.v.
* When using new grf-files, check if the configuration file is named correctly and if there are no spelling errors ''in'' the file.
* Check if the new grf-file appears in the proper directory

==Error Messages==

Each error message describes the file that caused the error, and the place within the file where the error occured (the so-called "sprite number"). These are all possible error messages you can get:
*Out of memory: TTDPatch ran out memory when trying to load more sprites. Make more memory available to it, or remove some entries from <tt>newgrf(w).cfg</tt>.
*Wrong .grf version: This grf-file is for a different version of TTDPatch. Download the correct version of either the graphics, or the patch.
*Cannot load more sprites: The total number of sprites that TTD can handle is limited at 11484 active sprites. You must deactivate or remove some entries from <tt>newgrf(w).cfg</tt> to get below that limit.
*File not found: The specified file does not exist. Check to make sure that it is installed in the <tt>newgrf</tt> folder, and that you haven't made a typo when entering it in <tt>newgrf(w).cfg</tt>.
*More sprites than specified: This is an error caused by a corrupt .grf file. It has to be fixed by the author of the graphics file. It means the first entry in the graphics file's info file is wrong.
*File has invalid sprite: This is an error caused by a corrupt .grf file, or by an invalid parameter in <tt>newgrf(w).cfg</tt>. If you have one or more numbers after the filename in <tt>newgrf(w).cfg</tt>, remove all numbers and try again. If the error still occurs, it's a problem in the graphics file, and needs to be fixed by the author.

Still having trouble? Visit the [http://www.tt-forums.net/| TT-forums] and look for an answer there.

UseOfNewGraphics

2011-06-15T11:26:34Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Use of New Graphics=

This section explains how to deal with the many available new graphics files. Some of them can't be loaded at the sime time or aren't available in all climates.

==Summary==

Most of the new graphics sets are designed for a certain climate. They will only work in the right climate, for example you can't use the DBset in anything but the temperate climate. The DB set is also incompatible with the Temperate set ("tempset"), which means only one of the two can be active at the same time.

==Switches==

The most important TTDPatch switches that control activation and automatic selection of graphics are "loadallgraphics" (only applies in 2.0) and "saveoptionaldata".

If "loadallgraphics" is off (which is the default, and the only state in 2.5 and later), only those graphics are loaded that were loaded when the game was saved. If you later add new grf-files to '''<tt>newgrf.cfg</tt>''', those graphics won't be loaded in your existing savegames. The reason for this is that the new graphics also change the vehicle stats, and could lead to an inconsistent state of your vehicles. If you set the switch to on, all new graphics will be loaded when you load an existing savegame. This switch only applies to ''new'' graphics, so it should better be called "loadnewgraphics", but for historical reasons it isn't.

The "saveoptionaldata" switch allows TTDPatch to actually ''save'' the information about active graphics with your savegames. It is recommended that you always leave it turned on. If turned off, TTDPatch doesn't know which graphics are old and which ones are new, so it assumes all of them are new. In that case, "loadallgraphics" applies to all entries in the '''<tt>newgrf.cfg</tt>''' file.

Additionally, you can use the Cht: Graphics sign cheat to activate or deactivate individual graphics files. See the [[GraphicsCheat| description of that cheat]] to find out how it works.

NewGraphicsInstallation

2011-06-15T11:26:24Z

Pm-bot: Bot: Automated text replacement (--= +==)

=New Graphics Installation=

How to install and work with new graphics

TTDPatch enables the player to load new graphics of various kinds. Most of these require certain TTDPatch switches to be enabled, please read [[NewVehicleGraphics| New Vehicle Graphics]] for more details.

==Downloading new graphics==

Several websites are available for locating and downloading TTDPatch compatible graphics sets.
* [http://www.ttdpatch.net/newgrf.html| New Graphics Page at ttdpatch.net] - official patch graphics
* [http://grfcrawler.tt-forums.net/| GRF Crawler] - a database of graphics sets
* [http://www.tt-forums.net/viewtopic.php?t=3125&start;=0| Download Topic for new graphics] -- TT Forums topic with lots of graphics sets

Make sure that when you download graphics, you download the right version: DOS graphics for DOS TTD and Windows graphics for Windows TTD. If the graphics look very strange, you have probably downloaded the wrong version.

==Installation==

To add a new graphics set to TTDPatch, follow these three steps:
# Download and unpack (with Winzip/Winrar/etc) the set into your "newgrf" folder. If you do not have a "newgrf" folder, simply create a new folder in the TTD folder and name it "newgrf".
# Add the set to your graphics configuration: open <tt>newgrfw.cfg</tt> (Windows) or <tt>newgrf.cfg</tt> (DOS) in for example Notepad, and add a line like the following:

+ newgrf/''newset.grf''</pre> where ''newset.grf'' is the name of the file you've added in step 1
# Enable the set in the [[GRFStatusWindow| Graphics Status Window]]

(Note, if the graphics set is not a .grf file but either .grd or .exe, read below under "Old style graphics".)

Both TTDXC or Graphics Manager can help with step 2 and make it easier for you. You can find them on the [http://www.ttdpatch.net/tools.html| TTDPatch Tools] page.

Normally most sets will try to activate when you start a new random game. If you don't want to use a certain sets by default and rather only enable them when you want, add an exclamation mark after the filename, like this:

newgrf/dullset.grf !</pre>

Some graphics sets also support certain "parameters" you can change. You do this by adding the parameters as numbers after the filename (and after the exclamation mark if you have one) in newgrf(w).cfg, separated by a space:

newgrf/niceset.grf 15 3</pre>

This sets the first parameter to 15 and the second parameter to 3. What the parameters do depend on each set, so be sure to read the documentation that they provide.

In particular, the base graphics set for TTDPatch 2.5 or higher has the following parameters:

{|
!Parameter!!Meaning

|-
|<center>1</center>||Foundation type in temperate climate*

|-
|<center>2</center>||Foundation type in arctic climate*

|-
|<center>3</center>||Foundation type in tropical climate*

|-
|<center>4</center>||Foundation type in toyland*

|-
|<center>5</center>||Canals type, 0=default style, 1=old style
|}

* The value of each foundation type may be 0, 1, 2 or 3 for temperate, arctic, tropical or toyland foundations, respectively.

All parameters are optional, and if you omit them, the default graphics will be used.

==Old style graphics==

Before TTDPatch had sophisticated newgrf capabilities, graphics sets were distributed as .grd or .exe files. These do not go into newgrf(w).cfg, and instead they modify your TTD graphics directly.

Often, the most convenient way to use them is to convert the .exe or .grd file into a TTDPatch .grf file, for which you can use the above methods of adding, enabling and disabling the set. For this, download [http://www.bytetransfer.de/projects/ttdpatch/grdtogrf/| GRDtoGRF], and use that to convert the .exe or .grd file to a .grf

Otherwise, since these graphics sets modify your TTD graphics, the first thing you should do is to backup the following files:

{|
!Filename!!Contains

|-
|<tt>trg1r.grf</tt>||temperate terrain tiles, all vehicles and buildings

|-
|<tt>trgcr.grf</tt>||sub-arctic terrain tiles

|-
|<tt>trghr.grf</tt>||sub-tropical terrain tiles

|-
|<tt>trgir.grf</tt>||start screens

|-
|<tt>trgtr.grf</tt>||toyland map
|}

'''Note:''' The DOS version has grf-filenames without an r.''

While some sets come with an "undo" file to restore the original graphics, it is still safer to make a backup first in case anything goes wrong.

Always make sure you download the correct version. Windows executables won't work with TTD for DOS and the opposite won't work too!

Once you have the set, here's how to install a .exe graphics set:
# Download the set and if necessary unpack it in your TTD directory
# Locate the ''executable'' and double-click it
# Run TTDPatch and enjoy the new graphics

To install a .grd graphics set, you need the "grfmerge" tool from the [http://www.ttdpatch.net/grfcodec/| GRFCodec suite], read its documentation for more details.

If you didn't enjoy the new graphics follow one of these steps:
* Copy the original grf-file(s) over the modified one(s)
* Locate the UNDO-executable and double-click it

SpecificExamplesOfUsefulPresignalSetups

2011-06-15T11:26:14Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Specific examples of useful pre-signal setups=

Terminus station, through station and overflow loops

==The through station== (sometimes called "roro" or roll on/roll off station)

Such a station should be built like this:

src="http://www.ttdpatch.net/Manual/through.png"

There are four sets of signals involved, labelled 1 to 4. Signal 1 is the pre-signal, and only go green if any of the exit signals 2 are green. Signals 3 are those letting the trains out of the station. Finally, signal 4 terminates the exit block.

The following conditions have to be met for this to qualify for automatic conversion. Note that if you convert it manually, it will work like you might expect.
#Signal 1 must be a one-way signal leading into the station. This is the pre-signal.
#All of signals 2 must be two-way signals. There have to be at least two of these. (Otherwise pre-signals are useless.)
#All of signals 3 must be one-way signals leading out of the station

Also, even though not shown in the figure,
*There can be more than one of signal 1
*There can be more than one of signal 4 (or none, or a two-way)
*You don't have to follow the actual track layout, it can go in any direction you like. It doesn't even have to be at a station.

If conditions two and three are only met for part of the signals, it will work neither as it should, nor as it did before pre-signals. Those signals will not be converted to exits, so the pre-signal will not consider them when deciding to go green.

To repair a signal stuck at red, you'll have to modify its pre-signal setup with the Ctrl key, or remove and replace it.

==The terminus station==

src="http://www.ttdpatch.net/Manual/terminus.png"

This very compact layout of a station is often useful in a city, where there is not enough space for a full roro station. Here, the same conditions apply as in the previous case, and there can also be more than one of signals 1 and 3.

You can even combine both types of stations, i.e. have some of the platforms go through and others end.

==Improved overflow loops==

These improved overflow loops are useful at the entrance of a busy station, where you need to prevent traffic backup into the main line.

src="http://www.ttdpatch.net/Manual/overflow.png"

Here, (a) is the usual way to the station, and it's used if there's no train waiting. Make sure that your longest train will fit entirely on (a) to make this work. If there is already a train waiting, other trains will take route (b) and line up at signal 6. You can make (b) as long as you like. It should have a few one-way signals 7 along the way to allow several trains to line up.

A few important points:
*Signal 1 is the pre-signal leading into the station
*Signals 5 have to be two-way, or all trains will want to use route (a)
*Route (b) can either cut into route (a) before signal 1, or lead directly into the station. I recommend the above setup (connecting before signal 1) because that way all trains will use the overflow if it is in use. Otherwise trains will be able to take the shortcut even though they should line up at the end of route (b).
*Signal 6 has to be a one-way signal, as does signal 1.
*If you put a one-way signal before signal 5, it will be a pre-signal

This has a few advantages over a regular overflow loop. First, the trains only have to use it once before lining up at signal 6 and don't continue to loop until a platform is available. Also, even if the station is full, at least one more train will not have to use it, only if two or more trains are waiting will it be used. Third, one of the waiting trains will enter the station as soon as a platform is free, without having to complete a loop because it already is waiting at the station entrance. And lastly, the trains will be served in the order that they arrive in. In an overflow loop, there is no guarantee that a train will not loop indefinitely at a very busy station, just because newly arriving trains steal into the platforms.

==Example savegame==

Many aspects of pre-signalling can be confusing to those new to it. To help with the understanding, I have created a demonstration with a small savegame that you can [http://www.ttdpatch.net/presig.zip| download]. Please make sure that it won't overwrite one of your savegames. The save file is <tt>trt56.sv1</tt>, so if you already have that file, make a copy of it. It features both a through station and a terminus station, and has two improved overflow loops.

I encourage you to test this savegame with the pre-signal switch disabled, too, so you can see the difference it makes, and try different numbers of trains (as low as 7 maybe) by sending them to the depot, and more or fewer platforms at both stations.

AutomaticPresignalBlocks

2011-06-15T11:26:04Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Automatic pre-signal blocks=

How to set up automatic pre-signal blocks

With automatic pre-signal setups enabled (see [[Presignals| Pre-signals]]), all signal blocks that satisfy the following conditions will be converted to pre-signal blocks:
#At least one one-way signal going in
#At least two two-way signals
#At least one of these two-way signals leads to a block with another one-way signal going out, or an end-of-line.

If these three conditions are met, the one-way signals from condition 1 will be turned into a pre-signal, and the two-way signal(s) satisfying condition 3 will be turned into pre-signal exits. All other signals are left as they are, in particular, non-conforming two-way signals will not be converted.

HowPresignalsWork

2011-06-15T11:25:54Z

Pm-bot: Bot: Automated text replacement (--= +==)

=How pre-signals work=

Detailed information about the prinicples behind pre-signals

TTDPatch's pre-signals work differently, more like most real-life station signals, or similar to advance signals. They state whether a train can enter a station by looking if there is a free platform, not just by looking if the entrance is clear.

The basic principle is very simple: a pre-signal shows a green light if, and only if, there is a green exit from the block behind it (or if there are ''no'' exits at all). In the context of a station entrance, for example, this means that trains will enter the entrance only when there is at least one platform it can go to. If there isn't, it will wait in front of the pre-signal, and not block the station entrance.

src=http://www.ttdpatch.net/Manual/presig1.png

This simple principle can allow you to build very efficient yet simple stations, but first you have to understand how. The next few sections attempt to explain in more detail what the different types of signals are.

With these signals, is quite easy to have a small and yet very efficient station without the usual problems you get with busy stations, because now trains will be able to queue in front of a station, and get to the platforms in the order that they've arrived in.

Note that pre-signals ''do not'' change ''where'' a train goes, only ''when''. You cannot use them to tell trains where to go, instead you should use waypoints for that (see [[NewNonstopHandling| New Non-stop Handling]]).

==Types of signals==

In the context of pre-signals, there are four different types of signals: plain signals, pre-signals, pre-signal exits, and combo signals.

{|
!Type !!Appearance !!Function

|-
|Plain signals ||Single green light, no bar ||normal

|-
|Pre-signals ||Double green light, horizontal yellow bar ||Entrance to a pre-signal block

|-
|Exits ||Double green light, vertical gray bar ||Exit from a pre-signal block

|-
|Combo ||Double green light, vertical yellow bar ||Between two pre-signal blocks
|}

Pre-signals and combo signals are the only signals that really ''behave'' differently, the exits only affect how the other signals behave.

src=http://www.ttdpatch.net/Manual/presig2.png

Pre-signals will show a green light if any of the exits or combo signals behind it show green. They prevent a train from entering a block unless it can leave it quickly. A pre-signal with no exit signals will behave as a normal signal, to allow the use of two-way pre-signals (where the other direction would usually lead to a route serviced by one train only). The pre-signal only considers actual exit signals when deciding whether to go green or remain red, even if there are other, non-exit signals that would allow a train to leave the block. Pre-signals can be either one-way or two-way signals, but will usually be one-ways.

Pre-signal exits are signals leading away from the pre-signal block, and should normally be two-way signals, so as to give the train a choice. If they were one-way signals, the trains would all attempt to go to what they consider the "best" choice, even if there are other green signals they could go to as well. Therefore, an exit will in almost all cases have to be a two-way signal.

Combo signals are a combination of both pre-signals and exits. They serve as exit to a prior pre-signal, but are a pre-signal themselves. As such, they are to be placed between two pre-signal blocks, so that trains can go to the additional exits behind a combo signal if they need to, but the blocks are still separate and allow a train in each block. Please see below for a specific example. Note that combo signals are not as useful as they should be, because they currently have some limitations. In the case where all exits are blocked, and trains are waiting at both pre-signal blocks, both trains will start moving when one exit becomes available, but of course there is only one platform, so one train ends up waiting in the pre-signal block.

Unlike pre-signals, combo signals with no exit signals always show red.

UnReservePBSTrack:alpha

2011-06-15T11:25:44Z

Pm-bot: Bot: Automated text replacement (--= +==)

This sign cheat was introduced in TTDPatch 2.6 alpha 0 r1725.

==Usage==

Cht: ))UnReservePBSTrack[[]]UnReservePBSTrack[[

==Description==

This sign cheat unreserves any and all PBS-reserved track pieces on the current tile.

The purpose of this cheat is primarily for track reservation errors, where an isolated track piece has been left reserved, which subsequently blocks the affected track piece indefinitely, unless a train is ordered to ignore signals, which is highly unsafe, or if the affected tile is totally demolished and rebuilt, which is not always feasible, or desirable.

This typically occurs during a train crash clear-up, during certain types of reversing manoeuvres, or other abnormal train movement.

Supported tile types currently include: track, level crossings, PBS signals, tunnel entrances (and enhanced tunnel track), and track under and on bridges.

This cheat should be used with caution, as improper usage may result in train crashes.

LandGen:Alpha

2011-06-15T11:25:34Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Terrain Generator Control Cheat=

Change the parameters for the new terrain generator (Enable with [[ExperimentalFeatures:Alpha#New_Terrain_Generator| experimentalfeatures.newterraingen]])

==Usage==

Cht: ))LandGen[[]]LandGen[[ <delta-height> <water> <roughness>

==Description==

This cheat sets the three parameters for the new terrain generator. This cheat takes effect the next time you generate a random terrain. The three parameters are as follows:

Delta-height controls how mountainous the terrain will be, with larger numbers meaning more mountainous.

Water controls how much water will appear on the map, with larger numbers meaning more water.

Roughness controls how rough the landscape will be, with larger numbers generating a rougher map. The maximum value is 255.

As long as the first number is not too large, and the second one is larger than the first, you get decent landscapes.

==Examples==

<pre>Cht: ))LandGen[[]]LandGen[[ 10 60 140</pre>

Seems quite a nice island generator -- m3henry.

(Decreasing the 60 will tend towards a few large islands, while increasing it will tend towards many small islands.)

PurgeHousesIndustries

2011-06-15T11:25:24Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Purge house and industry data=

Removes unused house and industry data from the savegame

(Available since TTDPatch 2.6 r1358)

==Usage==

Cht: ))PurgeHouses[[]]PurgeHouses[[

Cht: ))PurgeIndustries[[]]PurgeIndustries[[

==Description==

When you use the newhouses or newindustries switches, TTDPatch remembers all house/industry types that have ever been enabled in your game, even if they're not available right now. This allows playing the game withouth loss of information even when the used GRFs aren't available for some reason. When the GRF is turned back on, everything can be restored correctly.

There are times, however, when you don't want this functionality. For example, when you decide to stop using a building set, the IDs will stay occupied nevertheless, and this may prevent you from enabling some other big building sets. That's the reason this cheat was implemented.

When you're using "Cht: PurgeHouses", you're saying "I don't need the house types that aren't available right now". Those houses will be permanently replaced by their substitute types, and their slots become available for re-use. Therefore, the intended way to use these cheats is:
# Open the GRF Settings window, and disable all house/industry GRFs that you don't want to ever use again. (It's important that everything you ''want'' to use must be enabled, since you will lose everything that isn't enabled.)
# Plant the "Cht: PurgeHouses" and/or "Cht: PurgeIndustries" sign cheat.
# (optional) Open the GRF Settings window again. Now you may be able to turn on the sets you couldn't earlier because there are more free slots available for them.

Purging industry types is a bit more complicated than purging house types. When you purge industry types, the new types that aren't currently available will be removed from the map, since they're unusable without their definitions anyway. When a set changed the behaviour of an old industry instead of adding a brand new one, though, the industry type in question will remain, and will revert to its old behaviour. That is, coal mines should stay, but potash mines should be removed. TTDPatch may make a mistake about what is a modification and what is a brand new type, though, so you might have to remove some of the industries manually. Additionally, some of the old industries may still work differently from the TTD default; if this happens, you can use [[ResetIndustryData| Cht: ReloadIndustries]] to restore their default properties. (This will reset their production to the default, though.)

There is another tricky part. Industry sets can disable some of the default industry types without replacing them. When a set does that, TTDPatch can't decide what do you want when purging: do you want to re-enable those industries, or keep them disabled? The fate of these industries is decided the next time you apply GRF settings. (This happens whenever you load the game, or press Apply in the GRF Settings window.) If the disabling GRF is still enabled when that happens, the old types stay disabled; if, however, the disabling GRF is gone, the old types get available again.

Because of all the difficulties mentioned above, Cht: ))PurgeIndustries[[]]PurgeIndustries[[ is probably useful in the scenario editor only. It is possible to use it in a running game, but it can cause a great chaos in your company when some industries vanish and others start behaving differently. The damage is usually so great that you may as well start a new game from scratch.

FaceSelection

2011-06-15T11:25:14Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Face Selection Cheat=

Allows editing the company manager's face

==Usage==

Cht: Face [code]

==Description==

This cheat has two functions. Without a code, it displays the code of the current company manager's face. If a code is given, e.g. "Cht: Face 65AF5057", the manager's face will be set correspondingly.

Currently, the exact format of the face code is unknown, so the most reliable way to use this cheat is to find a face you like, read its code, and then write it down to use in the future.

The face code is apparently a bunch of bit-packed values:

{|
!bit(s)!!meaning

|-
|0..3||ignored

|-
|4..6||chin

|-
|7..9||forehead

|-
|10..15||mouth/nose/moustache

|-
|16..19||hair

|-
|20..23||shirt/coat

|-
|24..27||tie

|-
|27||skin color (female) (set for black, clear for white)

|-
|28||skin color (male) (set for black, clear for white)

|-
|29..30||glasses

|-
|31||gender (set for female, clear for male)
|}

This table should be taken with a very large grain of salt. Note, especially, the absence of "earring". For some female faces, toggling bit 26 changes the earring, but for others it does not, and that's only two settings, not four, as is clearly necessary.

ResetFifo

2011-06-15T11:25:04Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Reset Fifo loading=

Reset Fifo loading

==Usage==

Cht: ))ResetFifo[[]]ResetFifo[[

==Description==

This cheat resets the fifo loading feature. It may be useful if a station has become stuck and will no longer load any trains at all. It makes the game forget the order in which trains have arrived at all stations.

DeleteVehicles

2011-06-15T11:24:54Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Delete Vehicles Cheat=

Delete all vehicles on tile

==Usage==

Cht: ))DeleteVeh[[]]DeleteVeh[[

==Description==

This cheat deletes from the game all vehicles on the tile on which it the sign is placed. The vehicles simply disappear without trace. If any part of a train is on the tile, the whole train is deleted (even if the train is broken into 2 parts).

This may be useful in certain cases where there are vehicles that cannot be removed otherwise, for example stuck road vehicles or ships. You can only do this for your own vehicles, of course.

ResetIndustryData

2011-06-15T11:24:44Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Reset Industry Data=

Reload all industry data

==Usage==

Cht: ))ReloadIndustries[[]]ReloadIndustries[[

==Description==

Normally, it is not possible to change industry tile properties in an existing game. GRF changes that cause the tiles to accept a new cargo are normally only available after starting a new game. This can cause problems if the industry starts requiring a new cargo, but the tiles don't accept it.

With this cheat, all stored industry and industry tile information is reloaded, usually from the GRF files.

StopAllVehicles

2011-06-15T11:24:34Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Stop All Vehicles=

Stop (or start) all vehicles

==Usage==

Cht: ))StopAll[[]]StopAll[[ [0/1]

==Description==

When used without a parameter (or with parameter 1), this cheat stops all vehicles, except airplanes in flight of course.

When used with parameter 0, it starts all stopped vehicles.

RestartConstruction

2011-06-15T11:24:24Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Restart Construction=

Restart construction stages of town building or industry

==Usage==

Cht: ))RestartConst[[]]RestartConst[[

==Description==

This cheat restarts the construction of the house or industry under the sign. It's useful for GRF authors making new town buildings or industries to check out the construction stages.

GraphicsCheat

2011-06-15T11:24:14Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Graphics Cheat=

Activate or deactivate new graphics sets

==Usage==

Cht: Graphics [<ID> [0/1]]

==Description==

''Note:'' From TTDPatch 2.0.1 alpha 39 on, this cheat is deprecated, and instead simply opens the [[GRFStatusWindow| GRF Status Window]].

With this cheat, you can selectively activate or deactivate specific new .grf files.

If entered without any parameters, all graphics will be activated if they can.

If you say "Cht: Graphics <ID> [0/1]", you can activate or deactivate a specific graphics file, identified by the GRFID. If you leave off the 0 or 1, it will be activated by default. To find out the right graphics IDs for a certain .grf file, you can use Shadow's Graphics Manager, available from [http://www.ttdpatch.de.vu/]. Note that for these activations/deactivations to be permanent, "saveoptionaldata" must be ''on''.

Note also that you can't for example activate the tempset if the dbset is already active, because these two sets are mutually exclusive. You have to turn off the first one, then turn on the second one if you want to switch.

Here's a list of some GRFIDs:
*arcticset: 6D620104
*dbset: 6D620400
*newships: 6D620004
*tempset: 6D620204
*cargoset: 6D620305

Finally, this switch forces the vehicle list to be reset, so that new vehicles are available and have the correct stats. In effect, this is the same as Cht: ResetVehicles. See the description of that cheat for more details.

DebuggerCheat

2011-06-15T11:24:04Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Debugger Cheat=

Enable TTD's internal debugger

==Usage==

Cht: Debugger

==Description==

This cheat shows the window of TTD's built-in debugger. It shows some statistics about the game, for example how much memory is used, how many vehicles there are and other things. It is strongly recommend to save your game before using this cheat.

SwitchClimate

2011-06-15T11:23:54Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Switch Climate=

Switch to a new climate

==Usage==

Cht: Climate <newclimate>

==Description==

This cheat switches to the given climate: 0=temperate, 1=arctic, 2=tropical, 3=toyland.

It is somewhat dangerous, because it means that the existing industries and vehicles are for the wrong climate. This means that some of your transport routes may be useless and need to be adjusted. It is advisable to keep a backup savegame from before using this sign cheat in case something goes wrong.

This cheat may be useful for example to buy vehicles that are not normally available in the current climate.

Note that the climate-specific graphics will not change until you save and reload the game.

<span style='color:#FF0000'>Warning: TTD doesn't load initial climate data, you can't save switch from one climate to another and then use it to play, it's not safe to do so!!! </span>

RemoveHeadquarters

2011-06-15T11:23:44Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Remove Headquarters=

Remove headquarters

==Usage==

Cht: RemoveHQ

==Description==

This cheat removes your company headquarters. For example this is useful if you want to move the headquarters to a different city, or if they're in the way of your railway tracks.

SubsidyCheat

2011-06-15T11:23:34Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Subsidy Cheat=

Make TTD offer a new subsidy

==Usage==

Cht: Subsidy

==Description==

This cheat forces the offer of a new random subsidy. Note that it may fail if TTD is unable to find any sources with cargo in need of a subsidy, or if the maximum of 8 subsidies has been reached.

PlantManyTreesCheat

2011-06-15T11:23:24Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Plant Many Trees Cheat=

Plant a large rectangular area of trees

==Usage==

Cht: PlantTrees [<SizeX>] [<SizeY>] [<type>]

==Description==

This cheat plants a rectangular area of trees around the location of the sign. It is especially useful to plant trees for a lumber mill, just place a sign with Cht: PlantTrees on top of the lumber mill.

If SizeX is given, it specifies the size of the rectangle in the X direction. By default the size is just right to cover the range of a lumber mill (40 squares).

If SizeY is given, it specifies the size of the rectangle in the Y direction. If not given, the size in Y direction is the same size as in X direction.

Finally, you can specify the tree type as a number from 0 to the maximum tree type. If not given, random trees are planted.

ChangeSemaphores

2011-06-15T11:23:14Z

Pm-bot: Bot: Automated text replacement (--= +==)

==Usage==

Cht: Semaphores 0/1 <nowiki>[tracktype]</nowiki>

==Description==

This sets all signals to be light signals (if 0) or semaphores (if 1). Optionally you can restrict the conversion to the given track type. Note that to see the semaphores, the "semaphores" option has to be turned on and you must have loaded the semaphore graphics.

ClearUnloadOption

2011-06-15T11:23:04Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Clear unload option=

Remove unload option from all orders

==Usage==

Cht: NoUnload

==Description==

When taking over an AI company using either Cht: PlayerID or the subsidiary management, you will notice that most of their services use the unload command on all orders, even though it is unnecessary. As a result, all of these services will be considered to be feeder services (see [[FeederService| Feeder Service]]) if you have enabled them. This means that they will not earn any money and no cargo will ever reach a final destination.

This cheat will remove the unload command from all orders, so that you can take over an AI company without having to go through all orders manually.

SwitchingCompaniesplayers

2011-06-15T11:22:54Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Switching companies/players=

Switch control to a different company or player

==Usage==

Cht: PlayerID <num> [<temp>]

==Description==

Note: this sign cheat has largely been superceded by the new subsidiary management.

You can switch control to a different company or player using this cheat. The parameter is the number of the player, ranging from 0 to 7. If the company doesn't exist or is another human player (in multiplayer games), the cheat will fail, otherwise you now own a different company.

If you specify <temp> and it is not zero, the company is only taken over temporarily, and you can switch back using Cht: PlayerID with no parameters, or with your original company ID as the number. Without <temp>, the takeover is permanent, which means that the computer AI will take over your old company.

If you intend to switch back to your old company, make sure that you do a temporary takeover, otherwise the computer may shut down several of your lines, or waste money by building some of its brain-damaged routes.

You may also find it easier to switch temporarily by using the subsidiary management (see [[Subsidiaries| Subsidiaries]]).

GhostStationRemoval

2011-06-15T11:22:44Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Ghost station removal=

Remove ghost stations

==Usage==

Cht: ClearGhosts

==Description==

Previous versions of TTDPatch (before 1.8) had a bug that sometimes caused the creation of "ghost" train stations. These are either station buildings on the map without an associated station sign, or station signs where the train station did not exist.

This cheat will correct both problems. The first case will be converted to plain tracks, so that these can then be removed. (They can't be removed automatically in case there are trains on these tiles.) The second case will lose the train facility, and turn into a gray sign that eventually disappears, if the train terminal was the only facility.

Note: Always save your game before using this cheat, because it might remove stations that look alright, but are in fact ghost stations. If you find a station gets removed that you want to keep, place an additional facility right next to it (e. g. a bus station), and re-build the station after using this cheat.

PresignalRemoval

2011-06-15T11:22:34Z

Pm-bot: Bot: Automated text replacement (--= +==)

=Pre-signal removal=

Remove all pre-signal setups, or only automatic ones

==Usage==

Cht: ClearPreSig [<all>]

==Description==

This clears pre-signal setups and reverts signals back to the normal type. If <all> is specified and non-zero, the cheat clears all pre-signals, even manual ones. Otherwise, only automatic pre-signals will be reset.

Note that if automatic pre-signals are enabled, the signals will be converted to pre-signals again when a train enters the corresponding block, as long as they are a valid automatic pre-signal block (see [[Presignalsdetailed| Pre-signals (detailed]]]].