Page 1 of 1
Switch Monitor (F8)
#1
Posted 12 June 2020 - 05:20 PM
Happy Upcoming Father's Day everyone,
I am working on an activity for the Siskiyou route named "SISK_WCYD_TP_01" and have found that sone of the switches on the route show up in the F8 Switch Monitor as being lined for the diverging route. The switch itself is actually lined for the main line. Can someone help me to get the switch monitor to show the correct direction of the switch?
Thanks in advance for any assistance
AJ
I am working on an activity for the Siskiyou route named "SISK_WCYD_TP_01" and have found that sone of the switches on the route show up in the F8 Switch Monitor as being lined for the diverging route. The switch itself is actually lined for the main line. Can someone help me to get the switch monitor to show the correct direction of the switch?
Thanks in advance for any assistance
AJ
#2
Posted 12 June 2020 - 06:27 PM
If that switch is a scale rail switch, then its a scale rail bug.
Reported to Marc some years ago.
Reported to Marc some years ago.
#3
Posted 13 June 2020 - 11:22 AM
#4
Posted 13 June 2020 - 11:33 AM
The switch with this problem is on the Siskiyou route, yes? Dale used ScaleRail for that route, so I can all but assure you that any switch in that route is a ScaleRail switch
#5
Posted 13 June 2020 - 03:05 PM
ebnertra000, on 13 June 2020 - 11:33 AM, said:
The switch with this problem is on the Siskiyou route, yes? Dale used ScaleRail for that route, so I can all but assure you that any switch in that route is a ScaleRail switch
My misunderstanding I thought you meant it was a switch to a Scale track not a Scalerail switch.
#6
Posted 13 June 2020 - 03:52 PM
IIRC the problem here is Marc got the tsection entry wrong. You could go into the tsection file and correct it but then you might break paths that were written using the incorrect settings.
Given that I think it is something that can never be fixed, at least w/o substantial work (even in a miniroute setup) by fixing the tsection entry, possibly rebuilding the .tdb and editing the affected signals, and checking for and repairing any broken paths.
BTW, what switch is it?
Given that I think it is something that can never be fixed, at least w/o substantial work (even in a miniroute setup) by fixing the tsection entry, possibly rebuilding the .tdb and editing the affected signals, and checking for and repairing any broken paths.
BTW, what switch is it?
#7
Posted 13 June 2020 - 04:13 PM
Hi Dave,
Can you give me details about the incorrect entry so I can test the entry?
I would like to know the outcome of the fix.
Can you give me details about the incorrect entry so I can test the entry?
I would like to know the outcome of the fix.
#8
Posted 13 June 2020 - 06:18 PM
I don't recall which switch it is but take a look at SR_1tSwt_w_m06dR.s, TrackShape ( 32249 ). Almost every switch with MainRoute ( 1 ) is a leftie. SR_1tSwt_w_m06dR.s is righthanded but has a MainRoute ( 1 ) assigned to it. Marc's other rightie's with that code are marked DIV in their name indicating a diverging path is the default.
Mind you, I may be recalling the wrong set of facts, which is why I asked which switch?, above, but I think this may be the correct example.
Mind you, I may be recalling the wrong set of facts, which is why I asked which switch?, above, but I think this may be the correct example.
#9
Posted 15 June 2020 - 04:00 AM
Genma Saotome, on 13 June 2020 - 03:52 PM, said:
IIRC the problem here is Marc got the tsection entry wrong. You could go into the tsection file and correct it but then you might break paths that were written using the incorrect settings.
I can confirm that only changing the tsection entry for MainRoute does not fix the problem.
Page 1 of 1