Re: Bug with WR signal
Posted: 27 Jul 2019, 12:30
I think, the problem is, that the Signal T_Signal_Head_WR.s has in the sigcfg.dat two Signaltype:
T_Stop_R
T_Head_WR
both are of SignalFnType( NORMAL )
The Simulatorlogic is calculating one SignalHead after the other and will held the result of the last calculated Head as State for the whole Signal.
I think the Result of zwo Signalheads with SignalFnType( NORMAL ) at the same Pole will deliver a not defined result, depending which head the simulator is calculating at least, so for a correct function you have to correct the sigscf.dat.
I have in the *.tdb discover the following difference by placing signal with more the one head
TSRE5 is writing:
TrackNode ( 12
TrVectorNode (
TrVectorSections ( 7 2 2 -5862 14836 10 1 0 00 -5862 14836 -281.267 ………
TrItemRefs ( 2
TrItemRef ( 8 )
TrItemRef ( 9 )
)
)
MSTS-RE is writing for the same Signal:
TrackNode ( 12
TrVectorNode (
TrVectorSections ( 7 2 2 -5862 14836 10 1 0 00 -5862 14836 -281.267 …….
TrItemRefs ( 2
TrItemRef ( 9 )
TrItemRef ( 8 )
)
)
The sequence of the signalItems in the TrItemTable and the TrItemId ( ) are the same with both Editor's.
Maybe this different sequence may causing a different Signal-State-Result.
But as I sad the Cause ist a incorrect sigcfg.dat
Regards
EugenR
T_Stop_R
T_Head_WR
both are of SignalFnType( NORMAL )
The Simulatorlogic is calculating one SignalHead after the other and will held the result of the last calculated Head as State for the whole Signal.
I think the Result of zwo Signalheads with SignalFnType( NORMAL ) at the same Pole will deliver a not defined result, depending which head the simulator is calculating at least, so for a correct function you have to correct the sigscf.dat.
I have in the *.tdb discover the following difference by placing signal with more the one head
TSRE5 is writing:
TrackNode ( 12
TrVectorNode (
TrVectorSections ( 7 2 2 -5862 14836 10 1 0 00 -5862 14836 -281.267 ………
TrItemRefs ( 2
TrItemRef ( 8 )
TrItemRef ( 9 )
)
)
MSTS-RE is writing for the same Signal:
TrackNode ( 12
TrVectorNode (
TrVectorSections ( 7 2 2 -5862 14836 10 1 0 00 -5862 14836 -281.267 …….
TrItemRefs ( 2
TrItemRef ( 9 )
TrItemRef ( 8 )
)
)
The sequence of the signalItems in the TrItemTable and the TrItemId ( ) are the same with both Editor's.
Maybe this different sequence may causing a different Signal-State-Result.
But as I sad the Cause ist a incorrect sigcfg.dat
Regards
EugenR