[Hack]

Hi folks,

In checking my Sherman Hill route for errors in OR, I noted that the switch stands and points do not operate, yet they do so just fine in MSTS (track monitor works in OR though). Looking at the tsection.dat, the lines are the same with the exception that the ScaleRail switch does not contain a clearance entry. This, however, did not prevent MSTS from animating the switch, so my question is what do I need to look for in the ScaleRail model that OR assumes should be present? Thanks.

[StevenMasters]

Marc,

Check the JNodeposition() line in the world file. Maybe OR has a tighter tolerance for the animation position. The position can be off a little when placed with the MSTS RE.

[Genma Saotome]

There are some entries in the Tsection file for Scalerail switches that are wrong. IIRC they are those shapes where the default path is for the diverging route. Offhand I don't recall whether a parameter was missing or miscoded but the way they are is different than everything else and when the f4 window is OR was updated to show the position of the switches these were opposite of relaity.

[Hack]

 Genma Saotome, on 07 April 2017 - 05:04 PM, said:

There are some entries in the Tsection file for Scalerail switches that are wrong. IIRC they are those shapes where the default path is for the diverging route.

Sorry for the delayed response.

Are these the *_div turnouts? If so, then the paths are set correctly.

@Steven: what is the JNodePosn supposed to tell me or what I'm looking for? IIRC, when I created the sections, I based the entries on default ones. Would this affect all turnouts, even ScaleRail switches on other routes? :unsure:

[StevenMasters]

 Hack, on 11 May 2017 - 08:39 PM, said:

Sorry for the delayed response.

Are these the *_div turnouts? If so, then the paths are set correctly.

@Steven: what is the JNodePosn supposed to tell me or what I'm looking for? IIRC, when I created the sections, I based the entries on default ones. Would this affect all turnouts, even ScaleRail switches on other routes? :unsure:

The JNodePosition() line is what allows the animation to occur. Without it, there will be no animation of the shape (it does function route wise). This line is found in the world file entry for the switch. Sometimes the RE will "lose" this line.

[Hack]

Thanks Steven. The JNodePosn lines are there. However, other routes, such as the Feather River, work without issue. Is there something in the model that may be amiss?

[StevenMasters]

 Hack, on 12 May 2017 - 07:08 AM, said:

Thanks Steven. The JNodePosn lines are there. However, other routes, such as the Feather River, work without issue. Is there something in the model that may be amiss?

Mark

If the shape works fine in one route then not another, that would indicate that the shape is okay.

For the route that they don't work, is it always the same switch location? If so, I would take a closer look at the values in the JNode line. The values are the world tile X Z and the position/location of the shape. The position portion should match the Position() line. Sometimes there is a small difference in the values.

[Genma Saotome]

 Hack, on 11 May 2017 - 08:39 PM, said:

Sorry for the delayed response.

Are these the *_div turnouts? If so, then the paths are set correctly.

no. here is one:
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 ( )
)

Please see this post and the rest of the thread.