behaviour of ROUTE_SET() and BLOCK_STATE()

Bug #1598380 reported by Rippstein
12
This bug affects 2 people
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.

Revision history for this message
Rippstein (ch-signale) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.