OR is very good, but it is a pity that the errors are not corrected two of which are long known.
First - Signal in MP
When I control lights manually do not work. (when i use Stop, Aproach,Proceed )
http://s26.postimg.org/ppsyphwt1/screen_1.jpg
http://s26.postimg.org/w283zbzv9/screen_2.jpg
And second - direction on Loco
When I go to the second station in locomotion.I must have direction backwards, so I can go ahead.
http://s26.postimg.org/r2ozx0gd1/Open_Rails_2014_06_12_12_12_19.jpg
Page 1 of 1
Signals in MP and direction on Loco
#2
Posted 12 June 2014 - 05:38 AM
Howky, about the second point I agree with you, even if it cannot be considered as an error, but as a missing function.
About the first point maybe I can help you, because I had the same problem that in my case was due to a specific configuration of the sigcfg.dat file, where for some SignalType there is no SignalAspect defined for STOP, and/or APPROACH_1, and/or CLEAR_2, because such signal aspect is generated by the sigscr.dat file. In this case OR does not know what SignalAspect to show when a signal is forced. To modify this the related SignalAspect lines have to be added to the SignalType entries. If you attach here the sigcfg.dat file of your route I can check if this is the problem, and if I have some time I can provide you a modified file.
About the first point maybe I can help you, because I had the same problem that in my case was due to a specific configuration of the sigcfg.dat file, where for some SignalType there is no SignalAspect defined for STOP, and/or APPROACH_1, and/or CLEAR_2, because such signal aspect is generated by the sigscr.dat file. In this case OR does not know what SignalAspect to show when a signal is forced. To modify this the related SignalAspect lines have to be added to the SignalType entries. If you attach here the sigcfg.dat file of your route I can check if this is the problem, and if I have some time I can provide you a modified file.
#3
Posted 12 June 2014 - 07:47 AM
#4
Posted 12 June 2014 - 09:29 AM
I've looked at the file and it is as I supposed.
You should make a replacement in SignalTypes that have the line
and have SignalDrawStates that activate lights (e.g. SignalType PRED4/8; not SignalType MEZII, because it does not activate lights).
The replacement consists in replacing the above line with a block like below
where you have to replace Red, Yellow and Green with the name of the SignalDrawState you want to show when you force the signal to Stop, Approach and Clear.
In some SignalType maybe you have SignalAspects different from 0, but one of the three above SignalAspect () is missing. In this case you have to add the missing lines and have to increase accordingly the number of SignalAspects.
I'm sorry I can't prepare myself the change, as I'm not able to understand the meaning of the SignalDrawStates.
You can try, and if you have some problem, you can report it here.
I suggest you to leave sigcfg.dat unaltered, and to create a specific one for OR. To do so, you create an "Openrails" folder within the route's folder, and within such folder you put your modified sigcfg.dat and the unaltered sigscr.dat. OR will use these files instead of those within the route's root folder.
You should make a replacement in SignalTypes that have the line
SignalAspects ( 0 )
and have SignalDrawStates that activate lights (e.g. SignalType PRED4/8; not SignalType MEZII, because it does not activate lights).
The replacement consists in replacing the above line with a block like below
SignalAspects ( 3 SignalAspect ( STOP "Red" SpeedKPH ( 0 ) ) SignalAspect ( APPROACH_1 "Yellow" ) SignalAspect ( CLEAR_2 "Green" ) )
where you have to replace Red, Yellow and Green with the name of the SignalDrawState you want to show when you force the signal to Stop, Approach and Clear.
In some SignalType maybe you have SignalAspects different from 0, but one of the three above SignalAspect () is missing. In this case you have to add the missing lines and have to increase accordingly the number of SignalAspects.
I'm sorry I can't prepare myself the change, as I'm not able to understand the meaning of the SignalDrawStates.
You can try, and if you have some problem, you can report it here.
I suggest you to leave sigcfg.dat unaltered, and to create a specific one for OR. To do so, you create an "Openrails" folder within the route's folder, and within such folder you put your modified sigcfg.dat and the unaltered sigscr.dat. OR will use these files instead of those within the route's root folder.
#5
Posted 12 June 2014 - 11:40 AM
I try but I do not know exactly what the file overwrite
#6
Posted 12 June 2014 - 12:50 PM
#7
Posted 28 June 2014 - 09:51 AM
Hello, I do not know if I understood correctly. Adding image.
Before editing, I found the line "SignalAspects (0)" who I later replaced for "
SignalAspects (3
SignalAspect (STOP "Red" SpeedKPH (0))
SignalAspect (APPROACH_1 "Yellow")
SignalAspect (CLEAR_2 "Green")
)
"
Rightly so? Can be designed to show me what needs to be changed?
thank you
http://jpeg.cz/images/2014/06/28/w1IYl.jpg
http://jpeg.cz/images/2014/06/28/MlH7.jpg
I understood it correctly?
Before editing, I found the line "SignalAspects (0)" who I later replaced for "
SignalAspects (3
SignalAspect (STOP "Red" SpeedKPH (0))
SignalAspect (APPROACH_1 "Yellow")
SignalAspect (CLEAR_2 "Green")
)
"
Rightly so? Can be designed to show me what needs to be changed?
thank you
http://jpeg.cz/images/2014/06/28/w1IYl.jpg
http://jpeg.cz/images/2014/06/28/MlH7.jpg
I understood it correctly?
Page 1 of 1