Dear developers,
i am currently implementing a new signal set for MSTS, which should of course be compatible with OR in the future (well, as soon as MSTS signal objects are implemented in OR ;-)).
However, the MSTS has a major problem: it does not distinguish between train and shunting operations in activities, and only partially (by signal type) in the scripts.
My implementation of the signal system requires true separation of shunting and train paths, what means also the definition of shunting or train paths in an activity and an really associated signalling and block logic.
Ist there any document for OR describing the function of the signal and block system used in OR, that will be implemeted?
How will this work in OR in the future?
Kind regards
i am currently implementing a new signal set for MSTS, which should of course be compatible with OR in the future (well, as soon as MSTS signal objects are implemented in OR ;-)).
However, the MSTS has a major problem: it does not distinguish between train and shunting operations in activities, and only partially (by signal type) in the scripts.
My implementation of the signal system requires true separation of shunting and train paths, what means also the definition of shunting or train paths in an activity and an really associated signalling and block logic.
Ist there any document for OR describing the function of the signal and block system used in OR, that will be implemeted?
How will this work in OR in the future?
Kind regards



Comment