[HookitandBookit]

I've read somewhere that even just touching a track piece with TSRE destroys the track.db of that route. Because of that i have been very afraid of trying to fix errors on some routes.

[Weter]

Hello.
First, thank You for warning: it's really a serious risk.
And for using MSTS RE as well, by the way. Other risk is saving route after deletion of something: last action always MUST be adding.
Well, most precise to say: if that track piece is tied with some track object – than yes: there will be problems, but if there are no signals, crossings, etc. than it can be tried.
I've done those fixes several times without any issues.
Furthermore, TSRE offers to us CONTROLLED process of TDB modifying, while MSTS RE did it only automatically and hence - unpredictable.
In other words, signals, mileposts, crossings are tied with nearby track section, so if you would edit the latter: these tied items will be lost!
So far, there is a law: never place track objects like that, before your track work for that place will be completely finished.
But, of course, you can lay new track, extending the line.

[Laci1959]

Hello.

I’ve only been using TSRE for a year to build a track with no problems.

What I pay attention to is that when deleting items that affect the tdb, I save it before leaving the Tile. I used to do this at the MSTS level editor and have been using it ever since.

Indeed, TSRE also fails if we do not follow the above rule. I saw a log file with signaling errors. The track builder only uses TSRE. I think the maker didn’t save Tile before switching.
Replacing a Siding with a Platform or creating a new one is no problem if you pay attention to the backup.

Laci1959

[Laci1959]

[quote]So far, there is a law: never place track objects like that, before your track work for that place will be completely finished.

This can also be tricked. I go from station to station in track construction. When the track is ready, backup, then signaling, milepost, track sounds. Then backup again, and then you can come up with the next station spacing.
When making changes, make sure that the elements placed on the track are removed while the track is active. If you do the opposite, it will freeze when the Signal is selected.

Hello Weter. I welcome you too.

[Weter]

To our case: since there are no signals near misaligned track, I will try to fix that.
What is "active track"? Selected?
Yes: I've heared too: if track work have to be modified anyway, first it's needed to remove all related objects, then reconstruct tracks, and finally add new track objects to proper places.
WRT save before leaving this tile-thanks, it sounds reasonable.

[Laci1959]

Quote

What is "active track"? Selected?

https://kephost.net/p/2022/02/2662_6ac405662a01.png
The switch in the image is not active because there is no yellow line above it. It is deleted from the tdb file when saved. After selecting the track element, the Z button turns it off and, if necessary, returns the track element.

https://kephost.net/p/2022/02/5396_51112d9f4daf.png
Track view with inactive switch (Pnt)

[Weter]

So, it wasn't added to TDB, which is indicated by absence of yellow line above.

[Weter]

Well, I have merged tracks, where they were just overlayed with a switch.
TSRE helped a lot with it, using two dynamic track pieces.
Else, I've corrected some station names (united names as "st. X platform 1", "st. X platform 2" to just "st. X", with two platforms)
I have added a couple of paths for passenger operations and freight traffic.
And then, I've tried to create first timetable file – the future template for rest timetables.
The creation begins with composing of the station list: they need to be arranged in proper sequence.
I've chosen to place terminus row at the top, then insert the branch (two stations)

As the list of stations was completed, I've added some extra strings, which were introduced after the last timetable editor's edition. That's why them are not added to spreadsheet automatically.
Those are #speedkph and #briefing.