Testing v8.005

[eric]

Yes, I've found those single tracks between junctions as well and have a fix. Good point on the error level being raised.

Sent from my SM-S911U using Tapatalk

[vitold]

Hello. Is it possible to make it so that the track id can also be changed? The section name can be changed.

[eric]

Can you explain why you would want that? It's a fairly risky idea and could lead to an inoperable track database to alter either value.

[vitold]

To be honest, I'm not trying to change the database, I asked about changing the entry in the route w file.

[vitold]

Like here, for example Снимок_2025_02_09_20_03_04_198.jpg

[Timbit]

The reason I was asking , on Conbuilder there is something that when you are checking an activity and there is a car missing is will show up red and makes it a little easier to see, but if by changing it will cause more problems then just leave it. Thanks for getting back to me.

[eric]

You can already change the filename with no impact by using the Edit Name button. That will not update to the TDB unless you take one of the actions to update the TDB (e.g. using the Z key).

You cannot safely change the UiD or the SectionIdx in the W file without impacting the TDB. Both require referential integrity with how the vectors in the TDB are constructed. If you happen to click that piece of track and either delete or use the Z key, you've lost the correct linkage to the TDB, and might cause it to impact a different track vector if you've duplicated the UID of another track or road piece.

[eric]

Getting close to the final release for 8.005

Modified the "Reposition Camera to Object" function so that it works without having to select an object first. Rotation will be automatically adjusted to match the nearest track or road, and has been clamped so that it shouldn't flip more than +/- 90 degrees from your current view, even if the object's rotation is facing the opposite way of your camera. This makes it a bit easier to move down you track for quality control and editing.

Also added a dialog box to confirm a merge action. Previously, if you have the "routeMergeString" active in your Settings file and open up a different route, it would still try to execute the merge. Also, the routeMergeTDB, routeMergeTerrain and routeMergeTerrtex keywords are active and need to be set to True if you want to merge the TDB, overwrite terrain and overwrite Terrtex with the merged route's data.

[docmartin]

Eric, Thanks for the latest improvements to TSRE. However, did you forget that you were going to try to disambiguate the color of the signal arrows so that the arrow does not show red for both signals that don't need links as well as signals that need links but where they are not set correctly? I still see red arrows on signals not needing links.
Martin

[eric]

That change was put in based on what's available to check in the editor. When there's only one signal head, the indicator should be green.

What type of signal are you using, and are there more than one sub-object on the ones showing red?

[kapitaen]

Here are pictures of the swiss signals. Only the switch signals are green. All others have open links which are only needed for variants.
So for me everything is green. 😀😎

Screen Shot 02-22-25 at 03.16 PM.jpg

Screen Shot 02-22-25 at 03.17 PM.jpg

Screen Shot 02-22-25 at 03.19 PM.jpg

Jan

[docmartin]

This is what I have got.
Signals.jpg
There are two signals here, seen from the back. The two gray discs are color lights, home and distant. The black box is a theater box route indicator. The color lights do not need links. The theater box, of course, does.

The arrow for the theater box is green, which is as it should be, since it is linked correctly. The color lights arrow is red. This is confusing because it could mean that no linkage is needed or it could mean that linkage is needed but is not set up correctly. Here no link is needed so in this case you suggested in a previous post that the arrow could be displayed with a different shade of green from that showing for a correctly linked signal.

[kapitaen]

I have noticed that almost all Hazzard are listed in the _missingShapes.txt. However, the shape files for the hazzards are not in myROUTE/Shapes but in GLOBAL/SHAPES.

skydome.s
spotter_01.haz
spotter_02.haz
spotter_04.haz
spotter_05.haz
spotter_06.haz

Is it actually possible to bocome these unknown skydome.s to improve the sky, just a thought?

Jan

[davebridges]

Sorry, to sound naive, but where can I download TSRE Version8?

[eric]

The testing version is available in the first post of this thread. The stable version is available in the file library as file 88791