I have posted about the following problem on Elvas Tower but since it appears to be an issue with TSRE and TSRE is a hot topic here at the moment, I thought it might be useful to post here as well.
I am getting the following warning in the OR log file:
Warning: {TileX:-6080 TileZ:14925} track node 2832 could not be found in TDB
This is the entry WORLD tile -6080 14925, showing that Track Node 2832 does exist on this tile:
TrackObj (
UiD ( 2832 )
SectionIdx ( 38668 )
Elevation ( 0 )
JNodePosn (-6080 14925 891.311 28.5577 558.573 )
CollideFlags (39 )
FileName (ukfs_tl_17m5_9d46.s )
StaticFlags (00200180 )
Position (891.311 28.5577 558.573 )
QDirection ( 00.56912 0 0.822254 )
VDbId (4294967295 )
)
This is the entry in the .tdb file:
TrackNode ( 2832
TrVectorNode(
TrVectorSections( 1 38709 39508 -6086 14924 11315 0 1 00 -6086 14924 -726.68402 36.312996 113.368 0.000733177 1.3168 6.8259496e-09 )
)
TrPins( 1 1
TrPin( 2831 0 )
TrPin( 2833 1 )
)
)
There is no Track Node 2832 in WORLD tile -6086 14924 Thus the .tdb is looking for Track Node 2832 on tile -6086 14924 not tile -6080 14925 and therefore unsurprisingly cannot find it. So the .tdb file is pointing to the wrong WORLD tile for Track Node 2832.
The entry in the .tdb file has pins to two other nodes, as follows:
TrackNode ( 2831
TrJunctionNode( 0 39508 0 )
UiD( -6086 14924 11315 0 -6086 14924 -726.68402 36.312996 113.368 -0.000733177-1.8247879 -6.8259496e-09 )
TrPins( 1 2
TrPin( 2830 1 )
TrPin( 2832 1 )
TrPin( 2834 0 )
)
)
TrackNode ( 2832
TrVectorNode(
TrVectorSections( 1 38709 39508 -6086 14924 11315 0 1 00 -6086 14924 -726.68402 36.312996113.368 0.000733177 1.3168 6.8259496e-09 )
)
TrPins( 1 1
TrPin( 2831 0 )
TrPin( 2833 1 )
)
)
TrackNode ( 2833
TrEndNode( 0 )
UiD( -6086 14924 11315 1 -6086 14924 -714.62201 36.303898 117.314 0.0007283791.1923704 -9.0975562e-05 )
TrPins( 1 0
TrPin( 2832 0 )
)
)
This is doubly suspicious because Track Node 2832 refers to a left-hand turnout and therefore there should be no end node involved. Just deleting these three references to node 2832 from the .tdb file and reducing the Track Node count by three does not work because it crashes both TSRE and OR.
Obviously, I cannot simply substitute the correct WORLD tile reference in the .tdb file since a different track vector specification will be needed
Just as an experiment, however, I did change the .tdb entry to point to the correct tile, -6080 14925, without changing anything else and I still got the same warning message in the OR log, i.e.
"Warning: {TileX:-6080 TileZ:14925} track node 2832 could not be found in TDB". So perhaps the message is not correct and does not mean what it seems to mean. I have come across instances before where the OR log message did not actually mean what it says (though at the moment I cannot recall the circumstances).
So I am at a loss as to how to correct this error in the .tdb file. Can anyone explain why TSRE has written to the .tdb incorrectly in this way and perhaps suggest a solution?
Martin
I am getting the following warning in the OR log file:
Warning: {TileX:-6080 TileZ:14925} track node 2832 could not be found in TDB
This is the entry WORLD tile -6080 14925, showing that Track Node 2832 does exist on this tile:
TrackObj (
UiD ( 2832 )
SectionIdx ( 38668 )
Elevation ( 0 )
JNodePosn (-6080 14925 891.311 28.5577 558.573 )
CollideFlags (39 )
FileName (ukfs_tl_17m5_9d46.s )
StaticFlags (00200180 )
Position (891.311 28.5577 558.573 )
QDirection ( 00.56912 0 0.822254 )
VDbId (4294967295 )
)
This is the entry in the .tdb file:
TrackNode ( 2832
TrVectorNode(
TrVectorSections( 1 38709 39508 -6086 14924 11315 0 1 00 -6086 14924 -726.68402 36.312996 113.368 0.000733177 1.3168 6.8259496e-09 )
)
TrPins( 1 1
TrPin( 2831 0 )
TrPin( 2833 1 )
)
)
There is no Track Node 2832 in WORLD tile -6086 14924 Thus the .tdb is looking for Track Node 2832 on tile -6086 14924 not tile -6080 14925 and therefore unsurprisingly cannot find it. So the .tdb file is pointing to the wrong WORLD tile for Track Node 2832.
The entry in the .tdb file has pins to two other nodes, as follows:
TrackNode ( 2831
TrJunctionNode( 0 39508 0 )
UiD( -6086 14924 11315 0 -6086 14924 -726.68402 36.312996 113.368 -0.000733177-1.8247879 -6.8259496e-09 )
TrPins( 1 2
TrPin( 2830 1 )
TrPin( 2832 1 )
TrPin( 2834 0 )
)
)
TrackNode ( 2832
TrVectorNode(
TrVectorSections( 1 38709 39508 -6086 14924 11315 0 1 00 -6086 14924 -726.68402 36.312996113.368 0.000733177 1.3168 6.8259496e-09 )
)
TrPins( 1 1
TrPin( 2831 0 )
TrPin( 2833 1 )
)
)
TrackNode ( 2833
TrEndNode( 0 )
UiD( -6086 14924 11315 1 -6086 14924 -714.62201 36.303898 117.314 0.0007283791.1923704 -9.0975562e-05 )
TrPins( 1 0
TrPin( 2832 0 )
)
)
This is doubly suspicious because Track Node 2832 refers to a left-hand turnout and therefore there should be no end node involved. Just deleting these three references to node 2832 from the .tdb file and reducing the Track Node count by three does not work because it crashes both TSRE and OR.
Obviously, I cannot simply substitute the correct WORLD tile reference in the .tdb file since a different track vector specification will be needed
Just as an experiment, however, I did change the .tdb entry to point to the correct tile, -6080 14925, without changing anything else and I still got the same warning message in the OR log, i.e.
"Warning: {TileX:-6080 TileZ:14925} track node 2832 could not be found in TDB". So perhaps the message is not correct and does not mean what it seems to mean. I have come across instances before where the OR log message did not actually mean what it says (though at the moment I cannot recall the circumstances).
So I am at a loss as to how to correct this error in the .tdb file. Can anyone explain why TSRE has written to the .tdb incorrectly in this way and perhaps suggest a solution?
Martin





Comment