behaviour of ROUTE_SET() and BLOCK_STATE()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Open Rails |
New
|
Undecided
|
Unassigned |
Bug Description
By testing a signal-script Type NORMAL which not use the Function ENABLED, I have found the following Problems in OpenRails:
For SignalType NORMAL, if the Train pass the Signal, there is a different behaviour of the functions:
ROUTE_SET()
BLOCK_STATE()
between MSTS and OpenRails!
Function OpenRails MSTS
ROUTE_SET() TRUE to FALSE stay TRUE
BLOCK_STATE() CLEAR to JN_OBSTRUCTED CLEAR to OCCUPIED
For Signals not Type NORMAL the behaviour in MSTS and OpenRails is identical and similar to the behaviour of MSTS for signals Type NORMAL.
Can you please have a look on the code for these two functions in OpenRails.
I think this different behaviour has not make a problem until yet, because usually Signals Type NORMAL are closed by !ENABLED.
see also elvastower: www.elvastower. com/forums/ index.php? /topic/ 28752-switch- protecting- signal- on-an-unsignall ed-route/
http://