Again and again the question arises whether timetables should be created with the Tracks&Trip system or with the StationLink system.
1. What are these two systems anyway?
Before you can compile your timetable in the "Edit Timetable" window, so-called trips have to be created. Trips include all bus cubes where the AI bus should stop during its journey. Trips also contain travel time profiles, which determine the length of the trip, i.e. the duration of the trip. At the end of the day, a completed trip is just a (skilful) sequence of different trips.
Each trip requires the specification of the route as a sequence of paths. With the help of this sequence the AI vehicles are forwarded from path to path and thus find their way through the streets. Basically, there are two different types of trip for this purpose.
1.1. Tracks - Type 1
This is the "classic" (OMSI1) method of creating such paths.
A track contains a complete listing of all paths from the start path to the end path. All paths in the editor are clicked one after the other. A type 1 trip (usually from the start stop to the end stop of a route) then uses exactly one track.
1.2. StationLinks (StnLinks) - Type 2 (OMSI2 only)
This method was introduced in OMSI2 and is used on the original Spandau board for AI bus lines.
As the name suggests, this method creates many individual links that connect a bus cube A with a bus cube B. While tracks usually show the entire path from start to end point of a route, StationLinks always "shimmy" from one bus cube to the next, i.e. they only contain a partial path from one stop to the next. Type 2 trips consist of one or more StationLinks, depending on the desired path.
The advantage of StationLinks is obvious: You don't have to create a new StationLink for every line that goes over the same bus cubes. With parallel lines you have so much less work, because when creating a trip, only the stops are selected one after the other.
2. Advantages and disadvantages of both methods
2.1. Pro/Contra StationLinks
For large maps very fast creation, because each bus cube has to be connected to another one only once No double work for lines that are partially parallel. Chrono-Event: Very fast editing of paths Fewer errors when connecting paths There must ALWAYS be a start cube and an end cube. Accordingly, bus stop cubes are required for journeys without passenger changes or stops. (This is compensated for by the fact that in the trip configuration it is also possible to select not to stop at the corresponding cube) Bugs. Some busses drive around with up to 1400min delay, which is especially unpleasant at night. Between start cube and end cube there must be at least 60 meters as the crow flies on an intersection object, which often becomes narrow especially at end stops between break and start cube (see e.g. the maps Ruhrau and X10)
2.2. Pro/Contracks
Easier, especially for beginners Very reliable functionality and robustness (usually only few bugs occur) The editor immediately shows which paths the bus is currently taking- The larger and more complex the card becomes, the more complex it is to "handle" this system
Inflexible with lines that run parallel. For each partial branch, a complete track must usually be created. Teething troubles especially with chrono-events (see step 3 under [1])
3. Conclusion
In principle, both methods are recommended.
If end-/start cubes are identical or there is a sufficient distance between them, the StationLink system can be used well. It is also recommended for parallel lines.
Especially the last two contra points of the StationLinks prevent many people from using this system. The track system is certainly more complex, but just because it always works reliably and no "weird" things happen (like AI buses with extreme delays), the track system can be recommended without restrictions.
Mixing on a map is possible, e.g. AI bus lines can be created with StationLinks and AI trains and other vehicles with the track system. It should be considered to use only one of these systems per round.
