.tdb file - TrackNode Query

[slipperman]

Hi All,
In entries such as this :

TrackNode ( 23164 TrJunctionNode ( 0 39445 0 )
UiD ( -6097 15006 25881 0 -6097 15006 290.152 91.4283 455.169 0 -2.88099 0 )
TrPins ( 1 2
TrPin ( 0 0 )
TrPin ( 23165 1 )
TrPin ( 23171 1 )

what is the purpose of the TrPin ( 0 0 ) line?

For each TrackNode with such an entry, Open Rails gives two warning messages :
"Track node nnnnn pin 0 has invalid link to track node 0" and
"Ignored invalid track node nnnnn pin [0,0] link to track node 0"

My question is, can that entry be removed?
if so, should the 'TrPins ( 1 2' line be changed to 'TrPins ( 1 1' and the '1' on the next TrPin line changed to '0'?
Or could such changes be "fatal" to the route?

Or, maybe, Open Rails shouldn't give the warnings if the entries are deemed to be 'harmless'?!

This query was prompted by my running a route having 183 'TrPin ( 0 0 )' lines which created a total of 366 warnings in the OR log!

Cheers,
Ged

[michelouim]

Hi Ged,

I am not an expert, but it seems that the "(" do not match the ")". First line, you open one, and 3rd line you open another, but they are never closed.

Michel

[slipperman]

Hi Michel,
Thanks for replying, but it's nothing to do with matched/unmatched brackets! It's my fault for missing them from the quote - when used in a quote they appear as emoticons!!

I'm not saying the entry doesn't work, because it does, just asking a question (or two)

Cheers,
Ged

[baldwin]

TrPin ( 0 0 ) is a rogue blue pole, a track node not linked to another node. UKTS_22427 is a TDB primer and does give a method for removing these errors, but it involves use of the route editor and a text editor to change each bad trpin entry in the TDB.

As these rogue poles do not seem to affect the running of a route, perhaps we should be asking the OR dev team to suppress these messages.

[eric]

What harm is caused by the warnings? They're a legitimate error, and being reported as such. It shouldn't cause any problems running the route.

[R. Steele]

What harm is caused by the warnings? They're a legitimate error, and being reported as such. It shouldn't cause any problems running the route.

It's all about the amount of errors reported in the log...combing through the stuff a user cannot correct to find some useful information about errors/warnings they can correct...there have been some discussions about how to mitigate all the warnings in the logs. It's especially difficult for new OR users unaccustomed to using the log to diagnose problems.

Currently there are options to -- show/not show -- verbose eng-wag configuration messages and shape warnings...why not add other options...this appears a likely candidate. Perhaps another Options tab devoted to what warnings a user wants to appear in log? -- or just add that user selection to the "Data logger" tab.

[geepster775]

As these rogue poles do not seem to affect the running of a route

I wouldn't make an assumption that broad.

If a route has that many rogue blue poles, then perhaps the issue is with the route itself. If it runs fine in OR with errors logged, that's alright, too.

I would rather have a logged indicator that something might not be right with the route when it comes to debugging other activity aspects that are not performing as expected.

Lastly, doesn't TSRE have some feature to auto-fix blue poles?

[slipperman]

Hi Chaps,
@baldwin : Many thanks for that information, especially the TDB_Primer.

@eric : They don't cause any harm, except by bulking out the log file, by more than 360 lines in the case of the route I ran.

Cheers,
Ged

[charland]

OK sorry for bringing up this old threat but I'm currently having this problem and I'm not sure how to handle it.

I'm laying roads, finished four days of laying them and this morning I was selecting each piece and hitting "Y" to bring the terrain to the bottom of the pieces. Soon after starting I was hit with an end to end error. OR's log shows the one and only error, and it's a road section:

Warning: Track node 55 pin 0 has invalid link to track node 0 in C:\ Program Files (x86)\Microsoft Games\Train Simulator\ROUTES\CP_BSub\CP_BSub,rdb:line 421

This is a road right beside a station and without this error fixed, the road can not have traffic on it, so even though it still runs in OR it would be nice to fix.

After deleting the road sections on either side of the problem piece I ran a tdb rebuild twice. Both times it stopped 30 miles away claiming the error was below the camera on a piece of track. I was able to select and delete the piece of track with the error but it left two blue poles with a white hanger line connecting them... not seen this before.

I'll look for UKTS_22427, but any ideas would be appreciciated.

Paul :-)