Track Node Erros

[landnrailroader]

In the course of checking for errors in the Chattanooga Div. route I again noticed a number of track node errors and discovered some things that may be of interest, especially to new users of TSRE.

First, notice that the Node number is listed. I found that many of these errors are associated with turnout pieces that are lost way underground, and if that is the case, then removing the offending track piece will eliminate at least one node error. BUT, if the error is actually in track that is visible and part of the route, then the number is also visible in the editor window and by that you will see where the error is. Usually it is a misconnected track piece, or one that has not yet been entered into the track database. Then I discovered something more troubling. In several places I had A1pnt10d150r turnouts placed point to point with a 1 meter piece of track between the points. The error was showing up where this one meter piece was but in other areas where I had used a longer piece, typically 5 meters, it did not show an error. So the question is not only about the known error where you cannot connect points directly to points, back to back, BUT just how much is the minimal spacing allowed?
TRK_NODES.jpg

[commec61]

Hi Jerry,

Not sure if this helps but I can remember from some time back that it was said that you needed to have at least 2 meters separation for back to back because MSTS would complain at anything less. If this is the case, then it may still hold true for TSRE / OR as well. I could be wrong as memory is one of the first three things that goes and I can't remember the other two.

[NW 2156]

Hi Jerry,

I believe it's best practice to use either a 5m or 10m separation piece between points. Anything less and your asking for problems.

Robert

[rdayt]

I have a point to point with a 1.2 meter straight in between.
I have no errors.

Randy

[eric]

Minimum space between nodes (red poles) can be as small as 0.2m but I prefer having 0.5 to 1m separation, because when you are doing manual switching, it can get difficult to have enough time to throw a switch between points.


Sent from my SM-S911U using Tapatalk

[landnrailroader]

Oddly, what I did at the location where I had used a 1m piece was to delete the piece and insert a new one and that must have reset something because it cleared the error.

Jerry

[eric]

As long as the yellow lines and red poles look right, there likely isnt a problem.

The math used to detect the errors can be a little wonky and has reported errors that weren't really errors on inspection. And yet it also won't detect anomalies where the TDB lines reverse over themselves or one of the lines on a 2T or 3T piece can have a 0.2m jog left or right while the others are perfect...

How the line is drawn is what ultimately matters. If it looks off, sometimes a double-Z fixes everything, and sometimes you have to delete and replace like Jerry did. I've scoured the code to find where those anomalies get triggered and had zero luck aside from suspecting that the floating point precision is causing some inappropriate rounding or extra decimals to the millionth of a meter....

Sent from my SM-S911U using Tapatalk