Hello.
Recently I started building the prototypical 100km long route Plzen - Cheb (in western Czech republic) in 1967 to 1999 status where so called "four-aspect-automatic-block signalling" was used. Automatic signals are half the braking distance apart and the sequence of signal aspects approaching the stop is: "clear" - "warning" - "repeated-warning" - "stop".
I decided to augment my set of signals for this (now historical) signalling pattern too. But here I found a problem. Due to the nature of my signal models and its work I need to use scripted signals. I used this setting something like this:
if (me.GetSignalStateEx()==0) {SetFXCoronaTexture("l-stop",coronaRed);}
if (me.GetSignalStateEx()==4) {SetFXCoronaTexture("l-opakovana",coronaWhite);}
if ((me.GetSignalStateEx()==4) or (me.GetSignalStateEx()==7)) {SetFXCoronaTexture("l-warning",coronaYellow);}
if (me.GetSignalStateEx()==8) {SetFXCoronaTexture("l-clear",coronaGreen);}
The desired aspect sequence is:
GREEN ---> YELLOW ---> YELLOW+WHITE ---> RED
TS2009 seems to understand the script (signals are not black) but it never displays the YELLOW light alone so the sequence is: green -> yellow+white -> red... Which (of course) is not the proper function of the 4 aspect AB and deliberately leads to SPAD for every train approaching signal at stop...
It seems that TS2009 thinks about (me.GetSignalStateEx()==7) signal status as if it was (me.GetSignalStateEx()==8) instead.
Don't you know how to override this problem?
Thanks a lot.
V. Raim
Jivora
Recently I started building the prototypical 100km long route Plzen - Cheb (in western Czech republic) in 1967 to 1999 status where so called "four-aspect-automatic-block signalling" was used. Automatic signals are half the braking distance apart and the sequence of signal aspects approaching the stop is: "clear" - "warning" - "repeated-warning" - "stop".
I decided to augment my set of signals for this (now historical) signalling pattern too. But here I found a problem. Due to the nature of my signal models and its work I need to use scripted signals. I used this setting something like this:
if (me.GetSignalStateEx()==0) {SetFXCoronaTexture("l-stop",coronaRed);}
if (me.GetSignalStateEx()==4) {SetFXCoronaTexture("l-opakovana",coronaWhite);}
if ((me.GetSignalStateEx()==4) or (me.GetSignalStateEx()==7)) {SetFXCoronaTexture("l-warning",coronaYellow);}
if (me.GetSignalStateEx()==8) {SetFXCoronaTexture("l-clear",coronaGreen);}
The desired aspect sequence is:
GREEN ---> YELLOW ---> YELLOW+WHITE ---> RED
TS2009 seems to understand the script (signals are not black) but it never displays the YELLOW light alone so the sequence is: green -> yellow+white -> red... Which (of course) is not the proper function of the 4 aspect AB and deliberately leads to SPAD for every train approaching signal at stop...
It seems that TS2009 thinks about (me.GetSignalStateEx()==7) signal status as if it was (me.GetSignalStateEx()==8) instead.
Don't you know how to override this problem?
Thanks a lot.
V. Raim
Jivora