TDB Alignment Problems Intermittent Random TDB mis-alignment
#1
Posted 09 December 2017 - 02:49 PM
I'm baaaack....
I have a perplexing problem with the yellow TDB lines (a.) Going off alingment, (b.) missing from a previously installed section(s).
The alignment problems have turned up in various locations in the route, locations where I'm sure there were no alignment problems.
The TDB especially in a switch, crossover or a section with multiple paths should (in theory) never be able to get mis-aligned and yet, it is happening.
Here's a view of a A1tPnt5dSRgt.s switch where the paths went off alignment, produces a noticeable sideways jump when passed: TDB_Alignment-06.jpg (120.79K)
Number of downloads: 15
Correcting the alignment is very easy as I noted in the text in the attached picture but this keeps happening and I can't recall anything I'm doing that would cause this.
Sorry to dump another hot potato in your lap but this ones got me stumped.
best regards,
vince
#2
Posted 09 December 2017 - 02:59 PM
Of course I agree, it doesn't look nice.
#3
Posted 09 December 2017 - 03:54 PM
That track was placed using the MSTS RE, so it likely isn't just a TSRE issue
#4
Posted 09 December 2017 - 07:12 PM
Goku, on 09 December 2017 - 02:59 PM, said:
Hi Goku,
What do you need?
While waiting for your reply I'll try to explain in more detail. There is very little information I can provide as the only way I find a mis-align is either visually when I'm editing or getting jerked sideways riding over the bad alignment. No formal 'errors' or such as it's a visual or physical thing and I don't get an error log for that.
+When I install track I am very, very careful, visually checking the yellow TDB map are perfectly aligned. . . . Always, and all new track is given a check ride.
+Now, taking the example I provided, an ordinary 5 degree switch that been around for many years now.
( Yes, it is an XTracks add-on, a short version of the default 5d switches.)
++Since the switch in this case has two paths with one end of each path having the same origin point?
The Origin I understand is the point where the two paths join in a switch.
Is this correct? Please correct me if I'm wrong.
++This origin point must be the same for each of the two paths through this switch in the example. It can never or should never change!
Yet here we have a separation of a single origin point. This produces a lateral jump as I drive over it.
It was not two separate vectors when I placed, checked and drove over when I installed
this tracksection.
I have a test autopilot activity that runs a single GG1 through pretty much all of the track in the area I'm modding. That's how I'm finding these mis-alignments, I sometimes catch them visually when I'm editing.
They seem show up randomly and intermittently, no particular reason that I can see and have been doing so for a couple of months.
I've refrained fromn posting on this as I wanted to collect pictures (I now have 8) and the problem is easy to correct;
Just select the track, in this case the switch,' Z' to remove TDB, select again and 'Z' the TDB back.
That's it, no moving any track at all.
Resetting the TDB for this switch via the 'Z' key lines it up every time but I sometimes discover that another tracksection somewhere in the area has gone mis-aligned.
Maybe saving a 50+ megabyte database save is causing a bit of indigestion for TSRE?
So it's something causing the TDB to move a point that is one of the path ends of this switch.
Rounding errors between the two path points that should both be the same?
I dunno' Goku but something's causing the path point of the TDB line to move, producing physical effects in the Sim.
PRR-Eastern Region routes database sizes are:
TDB = 50.1 MB
TIT = 20.8 MB
RDB = 15.0 MB
RIT = 1.6 MB
Tile objects at fail area = 3,789http://www.elvastower.com/forums/public/style_emoticons/default/jawdrop2.gif
regards,
vince
#5
Posted 10 December 2017 - 02:18 AM
Quote
That's very important information. So, it happens like forever?
Quote
That's it, no moving any track at all.
Resetting the TDB for this switch via the 'Z' key lines it up every time but I sometimes discover that another tracksection somewhere in the area has gone mis-aligned.
I think, you are not correcting this error, but moving it on to the other end of the vector line. Can you check it?
Do you think, you could edit in the past the vector lines where the error is? For example on the other end, or something.
Does it happen to long vector, or short?
I don't see any option how TSRE could do something wrong here if the vector line wasn't touched.
#6
Posted 10 December 2017 - 02:45 AM
Quote
The Origin I understand is the point where the two paths join in a switch.
Is this correct? Please correct me if I'm wrong.
This origin point must be the same for each of the two paths through this switch in the example. It can never or should never change!
It's not always the case. TDB hast only two kind of objects: lines and points. If point relates to one line, it's endnode, in other cases it's junctionnode.
As you know, line has one origin point and one end point.
So, what's happen if you have one line between two junctions?
When you connect two switches ( image A -> B ), two lines are joined into one, two end points are removed and one origin point becomes end point.
When you press Z twice ( image C ), the switch lines are created as new and the vector line is added to the new line, so vector line direction is reversed. And I don't know if you just don't move the error to the green point I or II.
https://i.imgur.com/9zXLhy2.png
#7
Posted 13 December 2017 - 11:09 AM
What bothers me is the tdb mis-align are the same shape, ie. a switch. The tdb lines seperating at the tracknode of a switch is a problem. Attempting to setup DropBox to get route to you.
No. When I use Z in the method I described to reset tdb, the divorce and the straight thru are both in correct position.
Regards,
Vince
#8
Posted 15 December 2017 - 06:40 AM
#9
Posted 15 December 2017 - 07:59 AM
Attached File(s)
#10
Posted 15 December 2017 - 08:03 AM
Train simulation doesn't use this X value.
Suprise for me is why blue pole is created when re-entered in TSRE. I think this error was fixed in TSRE. Are you using new version? Can you show me an example?