The following blueprints have been fully included :
Blueprints for signalling update :
Additional Signal Script Functions
Adjustable Glow Settings
Common Script for Signal Types
Additional Signal Function Types
Signal Variables
Blueprints for timetable mode update :
Additional Timetable Functions
Attach & Detach functions in Timetable Mode
Timetable Pools
Random Restart Delays
Speed setting for trains in timetable mode
The following blueprint has been partially included :
Weather File
For this blueprint, the processing has been included but the reading of the file has been postponed while waiting for JSON functions to become available.
The following blueprints have not yet been included :
Print Position
Timetable Evaluation Functions
Also, the menu update for timetable is not yet available.
Note that this is a pretty extensive update, in particular for timetable mode. It is also still very much a work in progress.
A preliminary document detailing changes to the timetable mode is added to this post. A document for signalling changes will follow soon.
The overall OR documentation will be updated in due course, but it will take some time.
IMPORTANT NOTE.
It is well known that MSTS wasn't very good at handling AI trains - in particular, it could not handle multiple AI trains near to each other on the same track. Therefor, most signalling systems do not allow for AI trains to obtain access to tracks occupied by other trains - so called 'call on' permission. But without such permission for AI trains, the $attach, $pickup and $transfer functions now available for timetable mode cannot work.
There is an easy check to test if signalling on a route can handle these functions. Just create a timetable with two trains only - one stopping in a station, the other terminating on that same location, with an $attach command defined in the #dispose field to attach to the first train.
Select the second train as player train. If the signalling allows this train to run upto the first train, the signalling will support 'call on'. If you have to use the 'tab' function to obtain permission, the signalling does not support 'call on' and it will not be possible to run a timetable which includes attach functions.
Some further notes :
- Work is at hand on a demonstration timetable for a freeware route which includes almost all new functions.
This timetable was used for testing these new functions.
It just needs a finishing touch, and permission from the route owners. Watch this space.
- Included in the commit are changes to the handling of trains approaching station stops (timetable mode only).
This has been improved making the approach more realistic and also improves the timekeeping.
But (a lot of) more work is needed to improve the overall train control function for AI trains.
- With proper detach and attach functions now available, support for the /runround option in the #dispose field will be withdrawn.
This function is no longer required as the same can now be done much better using $detach and $attach (or $pickup) commands.
Withdrawing this option simplifies the commands, and also simplifies the program.
Preliminary document for timetable mode changes : TimetableChanges.pdf (61.7K)
Number of downloads: 1983
Regards,
Rob Roeterdink