[Docmartin]

I have a number of entries like this in my log file:

Warning: {TileX:-6082 TileZ:14925} track node 16757 could not be found in TDB

In fact, the relevant node does exist in the TDB file but is located on a different Tile as this extract from the TDB shows:

TrackNode ( 16757
TrJunctionNode ( 0 39668 0 )
UiD ( -6080 14926 3141 0 -6080 14926 -208.8614 28.550903 -965.9787 0 5.1580553 0 )
TrPins ( 1 2
TrPin ( 16756 1 )
TrPin ( 17053 0 )
TrPin ( 17066 0 )

Is this a problem with OR or is it something wrong with my route?

In addition, there are a few strange warnings in the log file like this one:

Warning: Skipped track section 53611 not in global or dynamic TSECTION.DAT

I do not understand the reference to global and dynamic TSECTION files or why I am getting this error.

I attach the full log file. Any help will be much appreciated.

Martin

Attached File(s)

•  OpenRailsLog.txt (14.56K)
  Number of downloads: 29

[steved]

Have you tried the Errors and Messages function under the Tools tab in TSRE?
Also, adding this "autoFix = true" to the settings.txt will tell TSRE to automatically fix route errors like this.
I have two versions of TSRE on my computer. In situations like this I'll open the route in v0.698 (without autofix) and minimize it, then I'll open the route again in v0.7002 (w autofix) and let the autofix function do it's thing.
After doing the autofix thing I'll open the route in OR. If the errors are no longer there and everything looks good I'll go ahead and close v0.698 without saving. If anything does go sideways I'll save the route open in v0.698 and start over with no changes.
I've never had anything go sideways but it feels nice to have a backup, just in case.

Randy

Other than these few errors your OpenRailsLog looks really good.
Nice work.

[Docmartin]

Thanks for your reply, Randy, and for the kind comment on my log file. My "Errors and Messages" window is, I am glad to say, empty. However, this of course means that in this case Autofix is irrelevant and the cause of the warnings lies elsewhere.

Martin

[engmod]

Hi Martin,

These errors are route errors, not OR errors.

Global tsection.dat is in your installs global folder, route tsection is in the route main folder.

>Warning: Skipped track section 53611 not in global or dynamic TSECTION.DAT

Dynamic tsection refers to the route tsection.
This line indicates that track section is missing from the global tsection.

There are a number of missing track sections.

What version of global tsection are you running?

[Docmartin]

Thanks for your reply, Derek. I am using Global tsection.dat build 42. I tried substituting build 56 but got an error message on loading that there were track section listed in the tsection file which were not present in the route and OR could not continue. In any case, I was happily using build 42 until out of the blue I started getting these warning messages.

Do you know whether there is a database of the different versions of tsection.dat anywhere, so that I can experiment with different builds?

Martin

[Docmartin]

I found a database of the various tsection.dat builds on GitHub. However, my problem was not solved by using any builds higher than 42.

In the end, I edited my dynamic tsection file to add the track sections which the log file flagged as missing. This solved the problem insofar as these track sections no longer appear in the log file as warnings. But I don't like the idea of using a non-standard tsection file and it also leaves the fundamental issue unresolved. Why did I get these warnings in the first place?

And I still get the other warning which I have not yet been able to resolve:

Warning: {TileX:-6080 TileZ:14925} track node 2832 could not be found in TDB

where the node does in fact exist but on a different tile from that mentioned in the warning.

Martin

[Genma Saotome]

? Why did I get these warnings in the first place?

Try this: Run the contributed track viewer. Go to the tile(s) that are being reported. Are there any tracks visible here that are mis-located? If yes, you have found a feature of TSRE (moving stuff w/o knowing you did that). They might be underground, under buildings, up in the sky. I'll guess the best course of action to deal with anything like this you find is to delete them.

[copperpen]

If global track sections end at 39999 and local track sections start at 40000, how can 53611 be in the global tsection as suggested?.

[Docmartin]

Copperpen, I said that I edited the dynamic, i.e. local, tsection.dat file not the global. The local file ran to 53606 before my additions.

I have taken a look as suggested in Track Viewer. However, since the log is telling me that it cannot find track node 2832 on tile -6080 14925 in the tdb file then, of course, it does not show up in Track Viewer. In any case, I don't see any evidence of rogue track sections. I can find track node 2832 in Track Viewer but on tile -6086 14924, which is where the tdb file tells me it should be.

[engmod]

Hi Martin,

> I tried substituting build 56 but got an error message on loading that there were track section listed in the tsection file which were not present in the route and OR could not continue.

I need to see that error, could you install 56 again and get me what ever you saw?
I administer global tsection.


>In any case, I was happily using build 42 until out of the blue I started getting these warning messages.

Are you modifying the route? as copperpen has pointed out, the numbers that are being logged are out of range.
The out of range is a route issue.


>In the end, I edited my dynamic tsection file to add the track sections which the log file flagged as missing

Bad idea as you are covering up the real error.


>However, my problem was not solved by using any builds higher than 42

And it won't be as all global tsections since 42 are backwards compatable.