Track Masters - Riddle Me This - TSRE Track Swap?

[scottb613]

Hi Folks,

Question - I tried taking a bad kink out of LHR track - that has bothered me for years - as an experiment.

Just north of Butzville - yes - it's a real town - it's NJ.
😂

I removed interactives in the area - signals and a milepost - used Z to turn off the existing Track DB lines on the existing track - deleted a dozen track pieces - then laid in new track. Mostly conventional - one piece of Dynamic Track. All looked good in TSRE. I used Z to put back the yellow Track DB lines - all looked smooth - all contiguous - with no jinks or steps in the yellow line. The yellow line most definitely followed the new track.

I launched ORTS - I see artifacts from the old track - and - the train is obviously following the old Yellow DB line path before I changed it - with the kink. The issue was present on both the conventional and dynamic tracks.

Do I need to rebuild the track database somehow?

I went back into TSRE and all still looked good in TSRE - reflecting the new condition - the yellow line was unbroken - smooth - and - still followed the new path. I went into wireframe mode - and there are definitely no missed pieces from the old track - haven't a clue where the track artifact is coming from - or how to make the track database actually reflect the changes.

Any thoughts?

Thanks.

The track on the right is the old condition and is most assuredly not present in TSRE.
2024-02-06 07_52_35-Greenshot.jpg



Regards,
Scott

[rdayt]

That is a strange one. The track and town name.
Any errors? OR or TSRE?

Randy

[scottb613]

Hi Randy,

Good thought - just checked the old ORTS logs - plenty of errors - just not something obvious to the track - sounds and textures.

I don't think it would matter - but I'm still using the same old path file for the train - I don't think the path file would do this - though.

I also did this twice - recovering from a backup - to insure I didn't fudge something myself - same result.

Regards,
Scott

[scottb613]

Hi Folks,

Paul had responded to a PM I had sent - regarding same - and he's had some similar recent experiences on a much grander scale - like 120 miles of track. He needed to use MSTS RE, TSRE, and Route Riter to clean it up. It sounds like something isn't right with TSRE - or - I just have some gross conceptual error? I don't have any of the old MSTS tools loaded.

Thanks.

Regards,
Scott

[eric]

What does Trackviewer show?

[scottb613]

Hi Eric,

It's not easy to see - but - Track Viewer reflects the OLD condition. No trace of the NEW condition - it's clearly still reading the old Track Database. What annoyed me about the curve - is one section jinks right before immediately turning left.

I'm sure Rich used the pieces he had available to make the connection - at the time. I don't know if it's prototypical - but - it never looked "right" to me. It always caught my attention as I passed through it.

If the problem warrants looking into - I can pack it up and post it. It's not a MASSIVE route.

Thanks.

Regards,
Scott


Same spot in Track Viewer - no sign of the NEW CONDITION:
2024-02-06 09_04_57-Greenshot.jpg


Same spot in TSRE - no sign of the OLD CONDITION:
2024-02-06 09_50_36-Greenshot.jpg

[scottb613]

Hi Folks,

Disregard - I think the Track DB was being messed up by some old backup copies in the same directory - there were multiple. I don't know what made the backups - as I don't really do any track work. I deleted all the backups and left only a single-track database - and the problem just went away. Open Rails must have been reading more than one track database.

Thanks for the help.

Regards,
Scott

[eric]

I was going to ask if there was another copy.... glad you figured it out.

[scottb613]

Hi Eric,

Greatly appreciate the interest and help.
😉

Regards,
Scott

[joe_star]

That's interesting, how were the other tdbs named? And what extension format was used?