[Genma Saotome]

Well, something is not right (probably my understanding of how the feature works). I see the indication when I do a ctrl-m and throw the switch to the diverging path but when the diverging path is pre-determined by the activity path I don't see any indication.

Approaching diverging path, no indication




taking diverging path




Approaching diverging path, no indication




taking diverging path

[Csantucci]

What switch are you using? Do you get the switch indication with MSTS? This can occur if in the TrackShape block of the switch MainRoute() is not present or has not the right value.
I on my side will have some check with near reversal points.

P.S.: I don't get faulty or missing indications.

[ATW]

Did Dave update to X3677 an is it a facing point or trail point? Coming out of a open switch does not display but does display when you are coming in a open switch.

[Genma Saotome]

Csantucci, on 04 December 2016 - 11:40 AM, said:

What switch are you using? Do you get the switch indication with MSTS? This can occur if in the TrackShape block of the switch MainRoute() is not present or has not the right value.
I on my side will have some check with near reversal points.

P.S.: I don't get faulty or missing indications.

The route uses Scalerail only and yeah, I did update the OR software (as I did see the indicator when I did cntl-M followed by a G to throw the switch for the diverging path. It is possible the first turnout has the diverging path set to be the default but I'm very sure the second one is ordinary.

Carlo, the last time I used MSTS to run a route was before the OR project started and AFAIK I do not have any installation of train.exe that will actually run a route. My only use of Train.exe (for many years) is to run the route editor.

[Csantucci]

I'm not able to reproduce this. To try finding this out I need the two shapes/textures and the shape/tsection entries in the tsection.dat.

[Genma Saotome]

After testing multiple activities I can say all of my Scalerail turnouts fail to display an indication when the path takes the diverging route -- except when I do the cntl-m g combination.

I use this shape a lot and AFACT it's representative of all of the rest:

TrackShape ( 20914
FileName ( SR_1tSwt_c_m03dL_Ext.s )
NumPaths ( 2 )
MainRoute ( 1 )
ClearanceDist ( 30.0 )
SectionIdx ( 3 0 0 0 0 39864 39864 33004 )
SectionIdx ( 1 0 0 0 0 39070 )
ManualJunctionShape ( )
)

[Genma Saotome]

Carlo, you have a PM.

[Csantucci]

Dave, could you please post a screenshot where you show also the switch window in addition to the track monitor window before engaging the diverging switch?

[Csantucci]

I had a test using one of Dave's short activities.
Here is a screenshot:


Both switch monitor and track monitor show a diverging switch left. However the switch in front is diverging right and, yes, the train will diverge right.
The right switch is as follows in the tsection.dat file

TrackShape ( 30220
 FileName ( SR_1tSwt_c_m06dR_NS.s )
 NumPaths ( 2 )
 MainRoute ( 1 )
 SectionIdx ( 2 0 0 0 0 39804 39804 )
 SectionIdx ( 1 0 0 0 0 191 )
 ManualJunctionShape ( )
)

What is uncommon here is that usually the two SectionIdx would be swapped, that is for a right switch first the straight route and then the diverging route. I'd like to hear experts here.
In fact if I swap the two SectionIdx lines and set MainRoute to 0 things are displayed correctly in the track monitor. Now a question: how does MSTS display this switch in its F4 window? The fact is that only from the TrackShape block data it's impossible to understand if it is a right or a left switch. For that only the tracksections used can tell whether it is a left or right switch.

[Csantucci]

OK, it came out that it is really so: Scalerail switches don't follow in general the usual convention which states that SectionIdx's in Trackshape blocks within tsection.dat are listed from left to right. This convention was used both for display of the switch in the track monitor window as well in the switch window.
The bug has been hopefully fixed in x.3682.