[ckawahara]

Does anyone know what file(s) contain the data used by Trackviewer when it seeks data during the "Finding the angles to draw signals, endnodes" operation?

[vince]

 ckawahara, on 26 August 2016 - 07:34 AM, said:

Does anyone know what file(s) contain the data used by Trackviewer when it seeks data during the "Finding the angles to draw signals, endnodes" operation?

Track Database and Track Item Table for two. I can't imagine it would need anything else.
regards,
vince

[ckawahara]

 vince, on 26 August 2016 - 07:53 AM, said:

Track Database and Track Item Table for two. I can't imagine it would need anything else.
regards,
vince

Thank you Vince.

To expand slightly, since the route in question does open and run on OR, but fails in Trackviewer, would an error on one tile with RE possible crash Trackviewer but not OR? I know any answer is a best guess answer.

[copperpen]

I think it also reads the world files. I have a route that has several signals that show in Trackviewer, but are reported by RR as being in the world file, but not in the TDB.

[Genma Saotome]

This post was written for MSTS but the tool itself works on any program. Just specify Contrib.TrackViewer.exe instead of train.exe and your good to go.

Do note the tool describes a whole lot of stuff and therefore can be bewildering to a noob but play around with suppressing things that appear to be irrelevant and you will eventually clear things away so the file accesses are easily found.

[ckawahara]

 Genma Saotome, on 26 August 2016 - 08:52 AM, said:

This post was written for MSTS but the tool itself works on any program. Just specify Contrib.TrackViewer.exe instead of train.exe and your good to go.

Do note the tool describes a whole lot of stuff and therefore can be bewildering to a noob but play around with suppressing things that appear to be irrelevant and you will eventually clear things away so the file accesses are easily found.

This is a good start, however there needs to be a means of identifying a specific process' event....in my case the error message displays. The Process Monitor displays many, many events that make it difficult to see where a single specific action took place. As mentioned, it is now a process of filtering out what may be the fluff in the display.

I guess I am not helping myself, but in a parallel effort to pin down the culprit, I have been overwriting files from the last know good version that worked in Trackviewer , the sigscr,dat, the tbd, and such. The good thing is that it keeps me at the Grey Goose bottle.

[ckawahara]

To close this post, the issue was not Trackviewer, but two mal-formed entries in the .tbd file. Once corrected, Trackviewer performed as expected.

[Goku]

Trackviewer fails to load routes in many rare situations, when MSTS, OR and TSRE can.