The extensions.cfg file format

■ Contenu

• 1. Overview
• 2. Syntax
• 3. The Cari section
• 4. The Coupleri section
• 5. The Bogiei section
• 6. The Exterior section (outdated)

■ 1. Présentation

The extensions.cfg file allows to define properties for individual cars, like length, axle positions and exterior objects.

The file is a plain text file encoded in any arbitrary encoding, however, UTF-8 with a byte order mark is the preferred choice. The parsing model for numbers is Strict. The file is required to be located inside the train folder and is expected to be named extensions.cfg. The file is interpreted on a per-line basis, from top to bottom.

● Car indices

All cars in the extensions.cfg are enumerated from 0 (front car) to n-1 (rear car), where n is the number of cars the train has in total, according to the train.dat file. For example, on a train with 10 cars, the front car has index 0 and the rear car index 9.

● Coupler indices

A coupler in this document refers to the space between neighboring cars. All couplers in the extensions.cfg are enumerated from 0 (front-most coupler) to n-2 (rear-most coupler), where n is the number of cars the train has in total, according to the train.dat file. Coupler index i corresponds to the coupler between the cars with indices i and i+1, so the coupler between the first two cars (0 and 1) in the train has index 0. Likewise, if a train has 10 cars, the coupler between the last two cars (8 and 9) would have index 8.

■ 2. Syntaxe

Each line in the file can be empty (or solely consist of white spaces) and will be ignored, can mark the beginning of a new section or contain key-value pairs inside a section. All key-value pairs relate to the last section opened.

A new section is opened by starting the line with an opening bracket (U+005B) and ending it with a closing bracket (U+005D). The text in-between the brackets indicates the name of the section and is case-insensitive. White spaces at the beginning and the end of the line are ignored, as well as at the beginning and the end of the name of the section. Thus, the beginning of the section has the following form:

A key-value pair is indicated by giving the key, an equals sign (U+003D) and then the value. The key is case-insensitive. White spaces at the beginning and the end of the line are ignored, as well as in front and after the equals sign. Alternatively phrased, white spaces surrounding the key and the value are ignored. Thus, a key-value pair as the following form:

You can use comments anywhere at the end of a line. A comment is started by a semicolon (U+003B). Comments, if present, are stripped away from all lines before these are processed.

■ 3. The Cari section

The Cari section allows to define properties specific to a certain car.

This starts the section for car i, which is an integer between 0 and n-1, where n is the number of cars the train has.

This key-value pair defines the exterior object for this car. Within the object file, the coordinate (0,0,0) (x, y, z) corresponds to the center of the car, both horizontally (x) and forward/backward (z), while y=0 corresponds to the top of the rails.

This key-value pair defines the length for this car. This overrides the length as defined in the train.dat for this particular car. If not used, this car will have the default length as defined in the train.dat.

This key-value pair defines the positions of the axles. While Rear and Front can take any values, the condition Rear < Front must hold.

With this setting, you can reverse the car in the consist. Please note that axle positions are given as if the car was not reversed.

With this setting, you can enable or disable loading sway for a specific car in the consist.

With this setting, you can control which cars remain visible from the cab, for example if your cab is not in the front car of the train. Note: This does not apply to the current driver car.

■ 4. The Coupleri section

The Coupleri section allows to define properties specific to a certain coupler.

This starts the section for coupler i, which is an integer between 0 and n-2, where n is the number of cars the train has.

This key-value pair defines the lowest and highest allowed distances between the cars, resembling a buffer and chain coupler. The condition Minimum ≤ Maximum must hold.

This key-value pair defines the optional exterior object for this coupler. Within the object file, the coordinate (0,0,0) (x, y, z) corresponds to the center of the coupler, both horizontally (x) and forward/backward (z), while y=0 corresponds to the top of the rails.

■ 5. The Bogiei section

The Bogiei section allows to define properties specific to a certain bogie. Each car is assumed to have two bogies (whether or not an object is displayed), placed at the axle points of the car.

This starts the section for bogie i, which is an integer between 0 and n-2, where n is the number of cars the train has.

This key-value pair defines the exterior object for this bogie. Within the object file, the coordinate (0,0,0) (x, y, z) corresponds to the center of the bogie, both horizontally (x) and forward/backward (z), while y=0 corresponds to the top of the rails.

This key-value pair defines the positions of the axles. While Rear and Front can take any values, the condition Rear < Front must hold.

■ 6. The Exterior section (outdated)

The Exterior section provides an easy way of adding exterior objects to the particular train. For more control on the setting of axle positions and individual car lengths, the Cari section has been introduced and should be used instead.

This starts the Exterior section.

This key-value pair can be used to set up the exterior objects for each individual car. Within the object file, the coordinate (0,0,0) (x, y, z) corresponds to the center of the car, both horizontally (x) and forward/backward (z), while y=0 corresponds to the top of the rails.