-
Notifications
You must be signed in to change notification settings - Fork 5
Limitations
Errors are present, but do not have a significant impact on running. Erros must be tolerated, but will be removed where possibleThey are mainly as follows
- Legacy MSTS errors. Some trackdatabase errors are present from the MSTS Route Editor. Some may be from the UKFS track system geometry crossover nodes.
- Differences in MSTS and ORTS interpretation of code e.g signal scripts
- Driving axle errors. As a work-around driving trailers have been given electric loco stautus with 0 power
- Stuck trains. Some trains in the timetable may have tested ok, but subsequently become stuck. In most cases simplifying the train instructions will cure
- Routeriter is a MSTS utility that has not been updated to Open Rails improvements. Many errors reported by Routeriter are not significant. eg ORTS Default snow provides a satisfactory alternative to hundreds of snow textures. A better guide is the OR log.
- Missing scenery. In some areas scenery will be minimal, and structures temporary with placeholder textures. Tracks and signals in thse areas are complete, allowing trains to complete their runs.
The timetable runs from Midnight to about 14:00. At present goods trains do not shunt wagons, but are treated as block trains. They merely wait in sidings during shunting times. Shunting individual wagons may follow. Carriages are fully exchanged between trains. Trains entering the network must start from a stand. Running starts are not yet possible. Trains leaving the system "hit a wall" Passing times can not yet be recorded, so some non stop and freight trains can have few times in the timetable.
Why are there no activities like in MSTS? Well there could be if you care to write some! I have concentrated on making timetables because I find the Open Rails timetable mode much more satifying