I did some tracing, and indeed it is a signal item (TrItemId 3994).
If you check the 100a-140.tdb file in your route directory, you will find the following block
SignalItem (
TrItemId ( 3994 )
TrItemSData ( 7920.46 00000002 )
TrItemRData ( -219.872 99.8775 -232.114 -5375 14704 )
TrSignalType ( 00000000 1 2.08729 AS )
)
TrItemId ( 3994 )
TrItemSData ( 7920.46 00000002 )
TrItemRData ( -219.872 99.8775 -232.114 -5375 14704 )
TrSignalType ( 00000000 1 2.08729 AS )
)
LevelCrItem (
TrItemId ( 3988 )
TrItemSData ( 7859.25 00000006 )
TrItemPData ( -220.955 -237.232 -5375 14704 )
TrItemRData ( -220.955 99.8733 -237.232 -5375 14704 )
)
TrItemId ( 3988 )
TrItemSData ( 7859.25 00000006 )
TrItemPData ( -220.955 -237.232 -5375 14704 )
TrItemRData ( -220.955 99.8733 -237.232 -5375 14704 )
)
Why MSTS ignore it, I think the TrSignalType may have some hidden values and MSTS knows that, while ORTS could not decipher it yet.







Comment