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
Bug with WR signal
Any suggestion why TrItemRefs order is different here?
TrItemRefs are sorted by distance on a track node. But maybe if distance is the same, other rules apply.
It would be nice to check first if swapping these TrItemRefs solves the problem and if yes, think about how to fix it.
TrItemRefs are sorted by distance on a track node. But maybe if distance is the same, other rules apply.
It would be nice to check first if swapping these TrItemRefs solves the problem and if yes, think about how to fix it.
I suppose, you open and close the signal by a passing Train?
But could you tell please how you change the signal to STOP?
By help of the dispatcher?
Regards EugenR
I dont know how Kingmax fixed it (he told me that he did it) but i can handle you the fixed file. Attached.Goku wrote: ↑28 Jul 2019, 13:01 Any suggestion why TrItemRefs order is different here?
TrItemRefs are sorted by distance on a track node. But maybe if distance is the same, other rules apply.
It would be nice to check first if swapping these TrItemRefs solves the problem and if yes, think about how to fix it.
- Attachments
-
- sigcfg.zip
- (19.99 KiB) Downloaded 910 times
As I have mentioned two SignalSubObj of Type NORMAL at a signal will cause undeterminated results, the first of this is now deleted in the new sigcfg.dat.
SignalShape (
"T_Signal_Head_WR.s"
"Shunter Signal WR"
SignalSubObjs ( 7
SignalSubObj ( 0
"SIGNAL" "Stop"
SigSubType ( SIGNAL_HEAD )
SigSubSType ( "T_Stop_R" )
)
SignalSubObj ( 1
"SIGNAL" "Default Main Track Signal"
SigSubType ( SIGNAL_HEAD )
SigSubSType ( "T_Head_WR" )
)
@ Goku:
I have placed this (faulty) Signal with MSTS-RE and with TSRE5 on a Testroute, both Editors has placed the Signal correct, I could not recognice any error. Also the sequence of the
TrItemRef ( 8 )
TrItemRef ( 9 )
doesn't have any influence on the Signalfunction.
regards
EugenR