Dynamic Track issues on Marias Pass 5

[CSRX]

Recently I popped back onto this route to do a couple of Amtrak and Local runs out of Whitefish, and I happened to noticed some odd things with the track database by the looks.

Has anyone else come across this issue, and any decent way to fix it, besides the usual "route riter" route. If I click it to do the remove and readd to the TDB in TSRE, seems to do the trick, but then breaks any signals and mileposts that are set up in that general area.
Even when you run in the sim over these sections, it will take you along the dirt path, and spit you back onto the tracks...

Seems to be a lot of issues with the error and messages log too.

Almost thinking tossing this route into the recycle bin may be an easier directly, sadly.

[eric]

I'm wondering if TSRE is messing up dynamic track. There was a post on Goku's forum a while back with similar oddness.

[CSRX]

I'm wondering if TSRE is messing up dynamic track. There was a post on Goku's forum a while back with similar oddness.

That's kind of unfortunate to hear, and odd at the same time as so far, I haven't seen this issue on some of the other routes recently installed, such as the RF&P, Whitefish 4, and even the Kicking Horse Pass.
I'll probably download a couple more routes and see if they throw a fit too.
If they don't, I'm afraid this problem may be an issue with the route itself in a deeper situation. Which is a shame, considering the previous Marias Pass route have been removed from the library. If only I had looked into this much sooner than later..

[Vince]

Dynamic Track Prob?

I'm wondering if TSRE is messing up dynamic track. There was a post on Goku's forum a while back with similar oddness.

I used a lot of Dynamic Track in my rebuild of the PRR-East with zero problems.
Waaay back there were DT problems when I first started working on the PRR but Goku was able to correct them.
The threads discussing this are at Elvas Tower.

The pictures shown look like the DT is 'flipped'.

[eric]

Which is a shame, considering the previous Marias Pass route have been removed from the library. If only I had looked into this much sooner than later..

You can still look ---- we have three versions Marias Pass routes in the library.

Marias v3 is there as part of Otto's beloved Gold Spike (which is a merge with the Whitefish).

Marias v4 is still alive and well as part of the GN High Line 3 / 3.1 / 3.2

V5 is obviously there, and with 7400+ downloads, maybe it's worth reinstalling it and not opening it up in TSRE....

The only version which might have gone away was v2. And that was clearly replaced ages ago.

[eric]

I used a lot of Dynamic Track in my rebuild of the PRR-East with zero problems.
Waaay back there were DT problems when I first started working on the PRR but Goku was able to correct them.
The threads discussing this are at Elvas Tower.

The pictures shown look like the DT is 'flipped'.

I haven't had any serious issues with DT, but I still get random TDB zigs and zags in my routes (track that's picture perfect for alignment but will have a 10-20cm offset at the yellow poles), as well as the problem with flipping vectors 180* on the straight path of a red pole that still happen randomly without any rhyme or reason.

I've never been able to prove why they happen, but my gut says there's something going on with decimal precision error on one of the calculations used to chain vectors together...

Ironically, adding dummy nodes helped in a few places... I thought I was done with those forever.

[CSRX]

So I went ahead and deleted the route with a clean install. I popped it open in the ORTS Track Viewer, seems to be fine.

I open up TSRE, and it gives me the typical options for the "TBD Error"
"Convert route database to current Global now"
"Disable Writing to TBD"
"Ignore and Continue"
or "Quit TSRE"

Converting was the option I always went with, have done this with a couple other routes including the KHPv2 and no issue. So figured it would be okay here too, apparently that isn't the case.

So this time around, I went with option two, disable the writing of TBD. I have zero plans to edit the trackwork anyways, if anything it would be simply converting to scalerail or UStracks whenever I get the chance, and as far as I know that shouldn't destroy the current TBD. If it does, a fresh install again would be in play.


So, as a result, seems to be a little fluke in the system when converting the TBD to current global standards, and now makes me wonder if my global files are out of date compared to the route (which shouldn't be as I do have all of the current items and global track data installed)

I'll take a peak at what is discussed in the ET forums of what Vince has mentioned and proceed with caution.

When I first started building routes, I always learned to avoid DT as much as possible, due to these random and unexplained issues, but occasionally you do catch yourself needing to use it for a certain radius that isn't featured for a two track or even three track piece.

[eric]

Glad that worked.

Just for gits and shiggles, I downloaded it to see if I could replicate your issue. Big mistake.... and now I'm deep in a rabbit hole.

I don't have USA2 installed anymore, nor did I have Kuju or XTracks. I got a whole bunch of grey ground and no tracks....

Now I'm restoring my MSTS install folders...

[dcarleton]

I believe that the TSection for this route includes low numbered pieces as found on routes built on the default global TSection, and also higher numbered pieces consistent with XTracks. The default portion of the route should have been run through Horace before adding the XTracks portion.

After running this route in OR, what does the log look like?

[eric]

I just ran the first 50 miles or so from Whitefish heading east, and see no track related errors in the log. Hopefully Shawn is just as lucky.

[CSRX]

I ran from Shelby to Cutbank earlier and didn't have any wonky issues. Which prior it gave some issues with the TDB and Dynamic Tracks in several areas between those two points.

I just will need to remember not to hit "Convert route database to current Global now" when I go in to make activities.

[eric]

I also just replicated the problem Shawn had earlier in the week. TSRE is definitely barfing on the dynamic track when you run that "Convert" option.

[geepster775]

Looks like TSRE is trying to do its equivalent of Horacing the route after the route was already contaminated at an earlier version level when the person did not Horace it back then before adding Xtracks but should have, and just ended up on the lucky side of things. That would explain why TSRE didnt break things when Horacing other moldie oldie payware routes that didn't have crowd-sourced interim versions.

[CSRX]

Looks like TSRE is trying to do its equivalent of Horacing the route after the route was already contaminated at an earlier version level when the person did not Horace it back then before adding Xtracks but should have, and just ended up on the lucky side of things. That would explain why TSRE didnt break things when Horacing other moldie oldie payware routes that didn't have crowd-sourced interim versions.

As far as I know, the route was installed prior to TSRE and went through the Horace feature as required when x tracks and what not was installed.
Whether I had make changes in between then and now to update x tracks for some bizarre reason, or changed the TBD in the global folder for another reason, I am unsure.
This very well could be a goof on my part, as I have an tendency to forget certain things I do or have done when it comes to ORTS. Which could explain why installing KHP or Crawford Hill, or even some of Paul Charlands routes recently again, didn't spit this issue out.
Kind of why I've been debating stepping away from ORTS. Between work and family, I tend to do certain things for ORTS, and either forget why I was doing it, or where I even left off, especially seems lately I've only been spending maybe an hour or so on the computer to begin with once or twice a week...
I do recall putting this route through Horace back in the day and kept it installed through out the years however.

[CSXT Q-317]

Ran across this problem while upgrading some routes to DB tracks. A Marias pass version was one of them.

Could not for the life of me figure out what was going on.

Looks like I too have made the mistake of updating to current on a newly installed route. I will have to go back and reinstall only this time not updating to the current global.