[Csantucci]

It's the second time this occurs to me.
This time I used TSRE5 to test the new ORTSSoundFileName for level crossing. I added a custom sound file name in two crossings in tile w-012506+014779.w and saved the route. Then I started an explore activity near such crossing. After some meters all objects disappeared and after some seconds the train was in a completely different place. In the OR logfile there are these warnings, that usually don't appear

Warning: Skipped track section 510 not in global or dynamic TSECTION.DAT

Warning: Skipped track section 512 not in global or dynamic TSECTION.DAT

Warning: Skipped track section 514 not in global or dynamic TSECTION.DAT

Warning: Skipped track section 528 not in global or dynamic TSECTION.DAT

I believe this occurs because this route (and also other initial ones, like USA1) uses dynamic track entries < 40000. I attach here the tsection.dat of USA2
 tsection.dat.txt (32.76K)
Number of downloads: 0

I understand it is not a high priority, but it would be nice if TSRE5 could cover this. I often use such routes for testing, because they load in short time.

[Goku]

Yes, it is known issue. TSRE doesn't convert old routes to current tsection.dat.
If you want just to edit objects, not TDB, just set writeTDB to false.

This feature is on the todo list.

[ebnertra000]

This same thing happened to me when I installed new crossing shapes on the default Hisatsu Line. I ended up replacing the route Tsection file, but I'll have to make note of the writeTDB feature in the future

[vince]

You'd get similar results attempting an edit with the MSTS editor.

And solution is the same: Use Horace or Archibald to re-index the local (route) tsection.dat file before editing.

regards,
vince