Advanced Settings/Vehicles

From OpenTTD
Jump to: navigation, search


Advanced Settings window: Vehicle section

The Vehicles section allows you to set various options related to trains, road vehicles, aircraft and ships. The purpose of the available settings is explained below. For each setting, the respective variable from the config file is listed with it's possible values.

Contents

The Vehicles section of the Advanced Settings window (1.3.1)

Routing

Pathfinder for trains

Feature availability (since 0.6.0)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

Select the pathfinding algorithm for trains. YAPF is the default and recommended setting, but you can still select the older pathfinders.

Possible Settings: NPF or YAPF (Recommended)
In Openttd.cfg config file: ([pf] pathfinder_for_trains = <0-2>)

Forbid trains and ships from making 90° turns

Feature availability (since 0.4.0)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

Disallows trains and ships from making sharp 90 degree turns. The NPF or YAPF pathfinder for trains needs to be enabled for this option to work for trains.

Possible Settings: On or Off
In Openttd.cfg config file: ([pf] forbid_90_deg = <true|false>)

Pathfinder for road vehicles

Feature availability (since 0.6.0)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

Select the pathfinding algorithm for road vehicles. YAPF is the default and recommended setting, but you can still select the older pathfinders.

Possible Settings: NPF or YAPF (Recommended)
In Openttd.cfg config file: ([pf] pathfinder_for_roadvehs = <0-2>)

Road vehicle queueing (with quantum effects)

Feature availability (since 0.2.0)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

Trucks and buses queue up at a busy station rather than turning around.

Possible Settings: On or Off
In Openttd.cfg config file: ([pf] roadveh_queue = <true|false>)

Pathfinder for ships

Feature availability (since 0.6.0)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

Select the pathfinding algorithm for ships. YAPF is the default setting, but you can still select the older pathfinders.

YAPF for ships has the advantage of not having to use buoys for long distances, but prior to OpenTTD 1.2 it had serious performance issues when using a large number of ships (i.e. more than ten).

Possible Settings: Original, NPF or YAPF (default)
In Openttd.cfg config file: ([pf] pathfinder_for_ships = <0-2>)

Autorenew

Are you sick of replacing all your vehicles with the same model once every twenty years? Let this setting take care of that for you. When you enable it, vehicles will automatically be replaced. With the following settings you can define the autorenew as you like. (If you want to replace them with a different model, you should use Replace_vehicles instead.)

Notice.png

Note
If the vehicle does not enter a service depot, it will not be renewed. You will not get a 'vehicle is getting old' warning!

Autorenew vehicle when it gets old

Feature availability (since 0.3.3)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

Vehicles are automatically replaced when they get old, provided that the same vehicle type is still available for purchase.

Possible Settings: On or Off
In Openttd.cfg config file: ([company] engine_renew = <true|false>)

Autorenew when vehicle is ... months before/after max age

Feature availability (since 0.3.4)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

If autorenew is enabled, a vehicle is automatically renewed the next time it enters a service depot when its age reaches the set amount of months before or after its maximum age.

Possible Settings: -12 to 12
  • -12 means that the vehicle is replaced 12 months before it gets old.
  • +12 means that the vehicle is replaced 12 months after it gets old.
In Openttd.cfg config file: ([company] engine_renew_months = <num_val>)

Autorenew minimum needed money for renew

Feature availability (since 0.3.4)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

If autorenew is enabled and a vehicle is going to be replaced, the amount money of the player has needs to be more than this value plus the cost of the new vehicle.

If the value is, for example, £200,000, a new vehicle costs £10,000 and you have £205,000, the vehicle will not be replaced. Instead, you will get a warning that autorenew has failed on that vehicle.

Possible Settings: £0 to £4,000,000 ($8,000,000)
In Openttd.cfg config file: ([company] engine_renew_money = <0-2000000>)

Servicing

Service intervals are in percents

Feature availability (since 0.3.4)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

When this switch is on the service intervals are considered to be in percents of the max. reliability rather than days. For example, if an engine has the max reliability of 80% and you set the service interval to 10% then it will go to depot at 72%.

Possible Settings: On or Off
In Openttd.cfg config file: ([vehicle] servint_ispercent = <true|false>)

Default service interval for trains

Feature availability (since 0.3.2)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

The default service interval when a new train is built.

Possible Settings: disabled or 15 days/% to 800 days/%
In Openttd.cfg config file: ([vehicle] servint_trains = <0, 5-800)

Default service interval for road vehicles

Feature availability (since 0.3.2)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

The default service interval when a new road vehicle is built.

Possible Settings: disabled or 15 days/% to 800 days/%
In Openttd.cfg config file: ([vehicle] servint_roadveh = <0, 5-800)

Default service interval for ships

Feature availability (since 0.3.2)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

The default service interval when a new ship is built.

Possible Settings: disabled or 15 days/% to 800 days/%
In Openttd.cfg config file: ([vehicle] servint_ships = <0, 5-800)

Default service interval for aircraft

Feature availability (since 0.3.2)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

The default service interval when a new aircraft is built.

Possible Settings: disabled or 15 days/% to 800 days/%
In Openttd.cfg config file: ([vehicle] servint_aircraft = <0, 5-800)

Disable servicing when breakdowns set to none

Feature availability (since 0.3.6)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

If you have breakdowns set to none and have this switch on, your vehicles will never go to the depot for a service. Even if this setting is enabled, vehicles will still go to depot for auto-renewal and/or replacement if those settings are activated.

Possible Settings: On or Off
In Openttd.cfg config file: ([order] no_servicing_if_no_breakdowns = <true|false>)

Service helicopters at helipads automatically

Feature availability (since 0.3.3)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

When enabled, helicopters will be serviced automatically each time they arrive at a helipad. This way, you don't need to have some airport along the helicopter's route for it to service. In previous versions this was located in Stations section.

Possible Settings: On or Off
In Openttd.cfg config file: ([order] serviceathelipad = <true|false>)

Trains

Train acceleration model

Feature availability (since 0.7.0)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

Select the default or a more realistic acceleration calculation for trains. With this setting set to realistic, trains will travel faster up hill, but slower through tight corners. This option has been renamed from Enable realistic acceleration for trains.

Possible Settings: Original or Realistic
In Openttd.cfg config file: ([vehicle] train_acceleration_model = <0-1>)

Slope steepness for trains

Feature availability (since 1.0.0)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

Sets the steepness of slopes, trains will slow down more on slopes if this setting is set to a higher value. It only applies if the realistic acceleration model is selected.

Possible Settings: 0% to 10%
In Openttd.cfg config file: ([vehicle] train_slope_steepness = <0-10>)

Enable building very long trains

Feature availability (0.2.0 to 1.0.5) (replaced with Maximum Train Length)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

You can build extremely long trains, aka mammoth trains.

Possible Settings: On or Off
In Openttd.cfg config file: ([vehicle] mammoth_trains = <true|false>)


Maximum train length

Feature availability (since 1.1.0)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

Specifies the maximal allowed length of a train in tiles. This replaces the old mammoth trains setting.

Possible Settings: 1 tile to 64 tiles
In Openttd.cfg config file: ([vehicle] max_train_length = <1-64>)


Warn if train is lost

Feature availability (since 0.5.0)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

A train will be reported lost if it cannot find a route to the station it is currently heading to.

Possible Settings: On or Off
In Openttd.cfg config file: ([gui] lost_train_warn = <true|false>)

Enable wagon speed limits

Feature availability (since 0.4.5)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

Some NewGRF's have wagon speed limits to make them more realistic, this option will enable/disable them.

Possible Settings: On or Off
In Openttd.cfg config file: ([vehicle] wagon_speed_limits = <true|false>)

Disable electric rails

Feature availability (since 0.5.0)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

Disables electrified railways. The electric trains will run on normal tracks when this setting is active and electrified railways are not available for purchase.

Possible Settings: On or Off
In Openttd.cfg config file: ([vehicle] disable_elrails = <true|false>)

Weight multiplier for freight to simulate heavy trains

Feature availability (since 0.5.0)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

The weight of freight trains is multiplied by the multiplier set here to simulate very heavy trains for more realism.

Possible Settings: 1 to 255
In Openttd.cfg config file: ([vehicle] freight_trains = <1-255>)

New train orders stop by default at the ... of the platform

Feature availability (since 1.0.0)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

Configure whether new orders will tell trains to stop at the near end, the middle or the far end of the platform by default. Later you can set these individually after the creation of orders.

Possible Settings: near end, middle or far end
In Openttd.cfg config file: ([gui] stop_location = <0-2>)

Allow goto depot orders

Feature availability (since 0.2.0)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

All vehicles can have a depot in their schedule.

Possible Settings: On or Off
In Openttd.cfg config file: ([order] gotodepot = <true|false>)

New orders are 'non-stop' by default

Feature availability (since 0.7.0)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

With this setting enabled, all newly assigned orders will be made 'non-stop' by default. With a non-stop order, vehicles will only stop at the station assigned in the order and will not halt at intermediate stations on its route not assigned as order.

Possible Settings: On or Off
In Openttd.cfg config file: ([gui] new_nonstop = <true|false>)

Review vehicle's orders

Feature availability (since 0.3.4)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

Enable the option to review the orders of vehicles periodically for invalid orders and other oddities. This option may be enabled for all vehicles, disabled for stopped vehicles, or disabled altogether.

Possible Settings: no, yes, but exclude stopped vehicles or of all vehicles
In Openttd.cfg config file: ([gui] order_review_system = <0-2>)

Warn if a vehicle's income is negative

Feature availability (since 0.7.0)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

If a vehicle's income is negative it will be reported in a news message. Use the transfer option in the vehicles order window if you want to set up a feeder service. This option has been renamed from Warn if a train's income is negative in 0.7.0.

Possible Settings: On or Off
In Openttd.cfg config file: ([gui] vehicle_income_warn = <true|false>)

Vehicles never expire

Feature availability (since 0.3.4)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

Old vehicles will stay in the vehicle list for you to choose and never become obsolete, so you can now run a Kirby with a Chiamera next to it! When enabling this setting in a running game, vehicles already disappeared from the list will not come back for purchase.

Possible Settings: On or Off
In Openttd.cfg config file: ([vehicle] never_expire_vehicles = <true|false>)


Max trains per player

Feature availability (since 0.3.2)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

Set the amount of trains that a player can have.

Possible Settings: 0 to 5,000
In Openttd.cfg config file: ([vehicle] max_trains = <0-5000>)

Max road vehicles per player

Feature availability (since 0.3.2)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

Set the amount of road vehicles that a player can have.

Possible Settings: 0 to 5,000
In Openttd.cfg config file: ([vehicle] max_roadveh = <0-5000>)

Max aircraft per player

Feature availability (since 0.3.2)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

Set the amount of aircraft that a player can have.

Possible Settings: 0 to 5,000
In Openttd.cfg config file: ([vehicle] max_aircraft = <0-5000>)

Max ships per player

Feature availability (since 0.3.2)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

Set the amount of ships that a player can have.

Possible Settings: 0 to 5,000
In Openttd.cfg config file: ([vehicle] max_ships = <0-5000>)

Plane speed factor

Feature availability (since 0.6.0)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

Set the speed of aircraft in relation to rail, road and water vehicles. In plain TTD, the aircraft traveled at 1/4th of ground speed. In layman terms, the lower the denominator, the faster aircraft will travel.

Possible Settings: 1/1 to 1/4
In Openttd.cfg config file: ([vehicle] plane_speed = <1-4>)


Number of plane crashes

Feature availability (since 1.0.0)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

Set the probability of plane crashes. They can be disabled if this setting is set to 'none'.

Possible Settings: none, reduced or normal
In Openttd.cfg config file: ([vehicle] plane_crashes = <0-2>)


Enable timetabling for vehicles

Feature availability (since 0.6.0)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

Allows you to use timetables for vehicles.

Possible Settings: On or Off
In Openttd.cfg config file: ([order] timetabling = <true|false>)


Road vehicle acceleration model

Feature availability (since 1.1.0)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

Set the default or a more realistic acceleration calculation for road vehicles. With this setting set to realistic. The power and tractive effort settings for vehicles only become meaningful with realistic acceleration, they will travel faster up hill, but slower through corners.

Valid options: [0|1]
0: Original
1: Realistic
openttd.cfg
[vehicle]
roadveh_acceleration_model


Road vehicle slope steepness

Feature availability (since 1.1.0)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

Sets the steepness of slopes, road vehicles will slow down more on slopes if this setting is set to a higher value. It only applies if the realistic acceleration is selected.

Valid options: [0 <= n <= 10]
0: 0% (lowest)
...
7: 7% (default)
...
10: 10% (steepest)
openttd.cfg
[vehicle]
roadveh_slope_steepness


Enable Multiple NewGRF engine sets

Feature availability (since 0.7.0)

<0.5

0.5

0.6

0.7

1.0

1.1

1.2

1.3

1.4

Nightly

When enabled, this feature allows multiple NewGRF vehicle sets to exist side-by-side. Without this feature, the maximum number of different vehicles is severely limited and vehicle sets of the same type will overwrite each others vehicles and functions. Note: using multiple vehicle sets side-by-side might result in very high or very low purchase and running costs for vehicles. Mixing wagons and trains from different train sets might result in graphical errors.

Possible Settings: On or Off
In Openttd.cfg config file: ([vehicle] dynamic_engines = <true|false>)



In previous versions

See also

Personal tools