Testing v8.005

[kapitaen]

There is a connection between collideobject ( and static ( as well as the output of Unsupported WorldObj !!! telepole", unknown: "nodirlight" and unknown: "maxvisdistance".
https://www.elvastower.com/forums/in...02#entry323302

Jan

[yellowdog]

A request for consideration for the consist editor:
A search feature for consists, similar to what already exists for rolling stock.

[pwillard]

The FreightAnim Option "Flip()" has no effect in the Consist Editor and ShapeViewer.

[Martels]

Hi! I wanted to let you know of a (probaly) bug: when I put a lot of sidings for a very big yard (novi san bovo, novi ligure, alessandria, piedmont, italy) most of them the program does not save them, and at the next save and reopen it says the errors in the screenshot. Could it be that (bay complete chance) the whole yard is perfectly contained in just one world tile?
How could I solve this issue? Because It's a week that I re-place all the sidings and every time the same sidings get removed over and over again

[thomask]

Saving the route in this version messes all interactives of the route (signals, platforms, sidings etc.).

[eric]

Which version? The latest 8.005RC2 or one of the testing versions?

Sent from my SM-S911U using Tapatalk

[thomask]

The tsre-releasecandidate3-v8.005 version.

I have a big old problematic route that if I save with any older versions of TSRE I can't open the route anymore in TSRE, it crashes before opening. Even if I don't do anything to the route, just saving. I realized it messes up the .tdb file because if I replace the new one with the older one it works again in the editor.

And with this version of TSRE v8.005 RC3 when I do any change to that route and I save it, it does work to open the route again in TSRE for further editing, the only problem is that it messes up all interactives on the entire route.
Any suggestions/ideas how to fix it?

I want to extend the route with new tracks.

Thanks!

[eric]

So, you're saying 8.005 will open the route, but it destroys the interactives. Any other version simply destroys the route.

Sounds like the problem is within the original route.... Post the route name, maybe someone has already fixed the underlying issues.

[thomask]

So, you're saying 8.005 will open the route, but it destroys the interactives. Any other version simply destroys the route.

Sounds like the problem is within the original route.... Post the route name, maybe someone has already fixed the underlying issues.

You are right.

The route is 18 years old and a local one from my country and isn't public anymore, nobody tried to edit it.

The interesting thing is: I worked on the same route and extended it between 2018-2020 while using the old TSRE version at that time without problems. When I tried to continue extending the route recently I realized that I can't edit the route anymore because saving it in TSRE messes it up (the old TSRE version -- curiously even the version I used to edit it in the first place back then -- simply destroys it that you can't open it anymore, this new version TSRE v8.005 deletes all interactives in the route).

After comparing the old .tdb file and the new .tdb file (pre-saving and post-saving) I noticed something: when it comes to the old .tdb file the positions (coordinates) of the TrVectorSections have values with a maximum of 5 decimals. If I edit the file with any version of TSRE (old or new), the file size increases and in many places it adds coordinates for TrVectorSections with up to 50 decimals.

I’m wondering if this might be the problem. Does it make the file too large, and then the program struggles to open it? In the end, the .tdb file has around 770,000 lines.
I thought of this because the behavior of the editor (the old TSRE) is to crash while trying to load the route (after saving), and no error appears in the log other than the fact that it seems to be trying to initialize/read much more data than usual.

The reason I’m saying this is because I also tried an older backup version of the route, from before my extensions, and it shows the same behavior in both the old and new versions of TSRE when editing it. That doesn’t really make sense, because if the route itself were the only issue and the software had no fault, it shouldn’t have been possible for me to edit and extend the route back in 2018–2020 in the first place (while using the old TSRE).

I think this new TSRE editor v8.005 tries to fix all errors in my old .tdb and it does it succesfully but also sacrifices all interactives (a few thousands) which isn't ideal at all.

[kapitaen]

Could you please attach both the settings.txt file and the tsre-log-2026XXXX-XXXX.txt file after save, from the TSRE folder here? Another question would be: Does the global tsection.dat file match the route?

Jan

[thomask]

Could you please attach both the settings.txt file and the tsre-log-2026XXXX-XXXX.txt file after save, from the TSRE folder here? Another question would be: Does the global tsection.dat file match the route?

Jan

I don't know how to check if the global tsection.dat match the route. How can I find that? The route works without problems in Open Rails.

[kapitaen]

Automatic repair of the track database is enabled in setting.txt; I would only use this if necessary.
set > autoFix = false < or disable it by adding a # at the beginning of the line.

Log.txt:

[I] # Unsupported WorldObj !!! -261844
This entry appears 425 times; unfortunately, I don't know what it means.

[I] #event - undefined token: "ortsactsoundfile"
[I] #ACT - undefined token: "changed"
This entry appears very often.; According to the OR manual, TSRE should manages this format, I don't know what it means.

[I] Local TSection: Gap found: 41062
[I] Local TSection: Gap found: 8
Please check the route's tsection.dat file. For XTrack, all entries in it should be 40000 or higher. Without XTrack, they should start sequentially at 376.

Jan

[thomask]

Automatic repair of the track database is enabled in setting.txt; I would only use this if necessary.
set > autoFix = false < or disable it by adding a # at the beginning of the line.

If I do this, any save of the route in the editor makes it crashing it whenever I want to open it again (after saving it once, without any editing) (same behaviour as with the old TSRE). The editor crashes without opening the route.
I can't upload the new .log file because it exceeds the maximum allowed file size. But it has thousand of rows like this:

[I] = "sidingitem"
[I] = "sidingitem"
[I] = "speedpostitem"
[I] = "speedpostitem"
[I] = "sidingitem"
[I] = "sidingitem"
[I] = "soundregionitem"
[I] = "sidingitem"
[I] = "soundregionitem"
[I] = "platformitem"
[I] = "platformitem"
[I] = "platformitem"
[I] = "platformitem"
[I] = "platformitem"

Log.txt:

[I] # Unsupported WorldObj !!! -261844
This entry appears 425 times; unfortunately, I don't know what it means.

[I] #event - undefined token: "ortsactsoundfile"
[I] #ACT - undefined token: "changed"
This entry appears very often.; According to the OR manual, TSRE should manages this format, I don't know what it means.

I don't think this is something that prevents the editor to work properly in this case.

[I] Local TSection: Gap found: 41062
[I] Local TSection: Gap found: 8
Please check the route's tsection.dat file. For XTrack, all entries in it should be 40000 or higher. Without XTrack, they should start sequentially at 376.

Jan

I checked it, all entries are 40000 or higher.

[kapitaen]

If you open the route in TSRE and select “Errors and Messages” from the tool menu, you can view the errors in the route. Now you need to figure out why these errors are occurring in the interactive mode. The error message should provide a clue.
Screen Shot 05-02-26 at 07.43 PM.jpg
Jan

[eric]

The newest version also writes out the errors found in that check to a text file.

Sent from my SM-S911U using Tapatalk