1. Creating a Chrono Event
Advanced users can skip steps 2-4 and directly create new configuration files.
- Create the folder \maps\<Map>\Chrono. This is the folder where all chronology events are stored.
- The folder \maps\Berlin-Spandau\Chrono\5001_Bauarbeiten_1 is copied into the folder you have just created. (For explanation: We use this chrono event as a "template" so that the configuration files do not have to be created first).
- The folder can be renamed at will. Best practice is to use ascending numbers depending on the starting time and thousands if events should be categorized. However, the folder names are not practically relevant.
- Since the copied out Berlin-Spandau-Chrono event is tailored to the original Spandau map and contains map data, all .map files and the TTData folder in this folder must be deleted.
- Now there should only be configuration files (.dsc, .cfg) in the folder and we can start setting the chronology event.
First let's have a look at the Chrono_DEU.dsc. In this file we define the German text which will be displayed later when OMSI is started in the lower left corner of the selection window. Here you are completely free.
[name]
Construction work <- What should the event be called
[description]
Part of the road is closed. <- Brief info on this chrono-event. This text is displayed in the selection menu of the map in the lower left corner.
[end]The corresponding other files contain the other languages. You can simply delete these if you do not want to create explanations in other languages.
Continue with the Chrono.cfg file: Here you set what the actual "content" of the chrono event is. In the following a short overview of the different possibilities:
1.1. Start date (mandatory)
In year-month-day format (YYYYMMDD).
This entry is mandatory! All other entries are optional.
1.2. End date
1.3. Deactivating lines
Example: Setting a line
These lines cannot be selected by the player and there are no AI vehicles driving on these lines.
[deactivate_lines]
17 <- Anzahl der Linien
5 & 5N
5E
13
31
34
35
38
39
54
56
63
80
92
92E
94
97
13NThese lines must always be according to the name of the -TTL file. If the .TTL file has a different name, it looks like this, for example:
1.4. Activate lines
This must be done in the editor, see below
1.5. Changing the ticket pack
Example: fare changes, fare adjustments, ...
1.6. Change type of money
Example: Change from DM to Euro.
1.7. Change AI List
Example: timetable change, new .hof file, ...
If the chrono folder contains a file named ailists_#upd.cfg, the normal AI list in the main folder of the map is overridden and OMSI accesses this AI list. This is a very fast and practical option, especially when a timetable change with a new yard file.
2. Change things in the editor
Now open the editor and load the corresponding map. When the map is loaded, you can see a tab called Chrono on the right side of the map. The new chrono event "Baustellen_Test (19890312-19890314)" is now also displayed here. With a double click on this event it turns blue. Now the map can be redesigned as foreseen in the newly created Chrono-Event.
Basically the editing of smaller things like new signs, stop or scenery objects works without problems. However, a completely new construction of an intersection already has major consequences (path rules, AI traffic, timetables, ...), which is why this is rather recommended for advanced users.
If you have changed something on the map, go back to Chrono and click on Standard again, so that the changes are undone and you can continue to work on the "Standard" (or: earliest time without a chrono event) of the map.
3. Changing the line layout
In the example above, a construction site was created. Now the existing (timetable) courses have to be adjusted so that they now follow a different path.
3.1. ... for trips with StationLinks (Type-2)
You can easily create a new StationLink between the stop in front and the stop behind the construction site under the tab StnLinks, for the opposite direction analogously. The Chrono-Trip is then set to this new StationLink.
3.2. ... for trips with tracks (T&T / Type-1)
Due to a bug in OMSI you have to take the more complicated way.
- First of all, all tracks (.TTR files) and trips (.TTP files) that run over this site have to be collected.
- When the editor is closed, all corresponding TTR and TTP files must be copied from \maps\<Map>\TTData to \maps\<Map>\<Chrono-Event>\TTData.
- Now the tracks&trips must be assigned correctly. If we did not do this, OMSI would use the non-chrono tracks for the chrono trip.
- The TTR files in the folder must be renamed so that their names (globally, i.e. across all chrono events) are unique (in this example we add the postfix "B" to the file name, e.g. 25_VGA-BGP.ttr becomes 25_VGA-BGP_B.ttr.
- Since the file names of the tracks have changed, they have to be changed in the corresponding trips, too. For this purpose the corresponding TTP files in the [flag]\Chrono\TTData[/flag] folder are opened and the [trip] entry must be adjusted as follows (relatively high up, only one entry per file):
[trip]
25_VGA-BGP_B <- Zeile, welche auf die ttr Datei verweist.
Bergerplatz
25Here we change the line that referred to the original track file 25_VGA-BGP.ttr to the new name (in this case we add the postfix). Now we have assigned a new track file to the trip, so the AI busses now follow the new track file without errors.
If you would also rename the TTP files, OMSI would not find the file in the corresponding circulation and use the file that is not anchored in the chrono.
Next you can open the editor again and edit the copied trips and tracks according to the chrono. These are then also displayed with the addition of the chrono.
The last step: Load OMSI and see if everything worked
