Configuration files

  • Configuration files store all data that OMSI can further use, for example, constants for scripts or information on meshes used.

    1. General information

    Configuration files in the sense of OMSI are pure text files that define the interaction of model (3D files, often also called mesh), textures and scripts. They can be opened with standard text editors, Notepad++ (free of charge) has proven itself here. Basically it can be said: All the information that can be converted into plain text (except scripts) is defined in configuration files.

    The file extension (cf. file formats) of configuration files varies, the "classic" extensions are cfg, sco, sli, bus and ovh.

    2. Keywords

    Similar to programming languages, there are keywords in configuration files, which vary depending on the file type. There can be any number of different keywords per file (according to the expected format). Almost all keywords are enclosed in square brackets (exceptions e.g. in the farm file). Everything outside keywords or blocks belonging to keywords is ignored by OMSI (cf. Comment out).

    OMSI recognises keywords case-sensitively, which means that the upper and lower case of the keywords must also match exactly!

    As a general convention, it has been established that at least one line should always be left blank before and after keywords to make it clear which blocks belong together:


    The following types of keywords exist:

    2.1. Stand-alone

    They occur on their own and do not require any further specification.

    A stand-alone keyword:
    Another stand-alone keyword:

    2.2. Fixed number of parameters

    Keywords that require additional information, for example, file names, values, etc. Such parameters can be characters, strings and/or floating point numbers (with decimal point!). The number per keyword is always fixed. Strictly speaking, stand-alone keywords are a special case of this type (0 parameters).

    2.3. Variable number of parameters

    For certain keywords, the length of the block is dynamic. In this case, the first parameter of the keyword determines the number of subsequent entries.

    A keyword followed by 3 parameters:
    In rare cases, it may also be necessary not to pass any parameters to the keyword at all:

    2.4. Explicit END Command

    For keywords that contain longer text (e.g. descriptions for the player), the previously mentioned method makes little sense. Here, the end of a block is marked with an explicit [end].

    3. Structure

    The following always applies: The keyword must stand alone in a line. Thus, there must be no space or other characters before or after the keyword. However, if this is done, the command is considered commented out and thus has no meaning (see commenting out). Comments can be written before, between or after the keywords.

    In this example:

    - [keyword]: 3 more lines will be read out.

    - [absheight]: 0 more lines are read out

    - [description]: up to the command [end].

    - [script]: one more line. This number then determines how many more numbers are read out

    4. use of configuration files

    Configuration files are used for the following:

    • AI lists
    • global.cfg files for maps
    • Signal routes
    • Timeline files for maps
    • Money configurations
    • texture configurations
    • model files
    • Seat configurations
    • Path configurations
    • cloud configurations
    • envir.cfg
    • Options

    This list is by no means complete. As described before, in OMSI almost all data that are neither scripts (.osc), model files (.x, .o3d) nor image/sound files are considered configuration data.


CC BY-SA 4.0

All contents of our OMSI Wiki are licensed under Creative Commons Attribution & ShareAlike (CC BY-SA 4.0).