[TorontoMainlineTrains]

This may have been discussed previously, however first time I have heard or seen this. Trying out the Bala2.0 sub upgrade after a tester told me the dwarf signals where not changing. I ran the route in MSTS and the signals on the siding at the north and south end are green. In Open Rails, they are both Red is this an issue that is yet to be solved or is there re-coding to do on the sig.dat?

MSTS approaching...
http://i84.photobucket.com/albums/k24/TigerTrains/Screens/scrgrb2.jpg

Open Rails approaching...
http://i84.photobucket.com/albums/k24/TigerTrains/Screens/Open%20Rails%202019-02-06%2012-14-50.png

MSTS passed...
http://i84.photobucket.com/albums/k24/TigerTrains/Screens/scrgrb3_1.jpg

Open Rails passed...
http://i84.photobucket.com/albums/k24/TigerTrains/Screens/Open%20Rails%202019-02-06%2012-15-14.png

[eugenR]

And in OR after the second picture the train has passed the red Signal with no emergency-stop?

Is this a station and the train should stop here?
OR has an Option under simulation called: "forced red at station stop"
If this option is activated, the exit-Signal of a station is hold on red until 2 min prior departure-time.

[roeter]

The Track Monitor is not shown in the OR screenshots. Therefor, it is not clear if the problem is that the signal remains at danger (which would indicate a signal script problem), or the signal has cleared but shows the wrong aspect (which would indicate a signal definition problem).
Could you please post the OR pictures showing the Track Monitor?

Regards,
Rob Roeterdink

[TorontoMainlineTrains]

Okay, so this is running in explore route, same as when ran in MSTS showing the green lights.

First this light is white but, not showing at all in OR
http://i84.photobucket.com/albums/k24/TigerTrains/Screens/Open%20Rails%202019-02-07%2006-24-27.png

2nd the dwarf signal
http://i84.photobucket.com/albums/k24/TigerTrains/Screens/Open%20Rails%202019-02-07%2006-26-50.png

John has tested the route in activities and the same thing shows.

[roeter]

Have the sigcfg.dat and sigscr.dat changed since the first release (2013)?

I noticed that I made two changes to those files in the original version:

sigcfg.dat :
a number of signals are defined as (NORMAL DISTANCE), i.e. as two different types. OR does not support that, a signal can be of one type only.

Related to this, in sigscr.dat :
many signals have the test :

		opp_sig_lr (SIGFN_DISTANCE) !=# SIGASP_STOP ||	// Entry from next interlocking blocked?

As the DISTANCE type no longer is valid for the opposite signal, this test always fails. These lines have therefor been removed.
In OR, this test is not required as the problems with opposite traffic are properly handled in OR through the deadlock logic.

If you want to keep the present versions of sigcfg.dat and sigscr.dat for use with MSTS, my advice would be to create a directory OpenRails (in the route directory), and place the adapted files in that directory.
MSTS will then use the original files, whereas OR will us the adapted files.
Please send me a PM if you want the adapted files.

Regards,
Rob Roeterdink