Not sure of problem with using TSRE-5

[bootednancy]

Greetings:

I have been using TSRE5 for a little time, mainly for altering Activities and related files, but I took a jump to editing a Route, but I am not sure what I am doing is right or wrong ????

I have the MLT "Cascades Crossing [Wilamette Pass]" and running an activity, I notice they are a "bit skimpy" when they designed the route that there are a few (too many for my liking) of unnamed sidings.

I finally "braved" the Route Editor to find out the functions and method to place additional yellow siding markers in the route.

Before I started, I remember from previously editing something, I had gotten the advice from another reader to "go to TSRE5 SETTINGS and change the question "Write TDB from False to True"", but has to be changed back to prevent changing it at other times when not needed.

I placed my Siding Markers, saved the changes, then went back and changed the SETTINGS file back to False.

When I started the activity over, I was getting errors that track sections are missing from the route. I then looked at the "Tsect" file and discovered it had been wiped cleaner than Hilary Clinton?? I had a back up copy of the original Tsect file from the download program to replace the corrupt one, and route activity then ran fine.

Question.....WHAT HAVE I DONE WRONG that caused the Tsect file to lose all the data???? The "TDB file" was fine, showing the new
siding markers I had just added

Thanks for the help.......any of the manuals for TSRE5 are extremely vague when it comes to procedures in Route building / Object placement, not exactly detailed as Rich Garber's Route Editor MSTS manual.

[kapitaen]

Hi Doug,

if the local tsection.dat looks like Hilary Clinton after editing in TSRE, then the local tsection.dat does not match the global one.
Say - your route was either built with XTracks; but you are using the original tsection.dat in the Global folder from 05/08/2001 -- or -- your roue was built with the original tsection.dat from 05/08/2001 and there is an XTrack tsection.dat in your Global folder.

If you look into the local tsection.dat you can see what belongs to your route. If the entries start at "SectionCurve ( 0 ) 40000" you need a XTracks tsection.dat, at "SectionCurve ( 0 ) 376" the original tsection.dat from 08.05.2001 must be active in the global folder. So Hilary Clinton will not bother you anymore.



Greetings Jan

Translated with www.DeepL.com/Translator (free version)

[derekmorton]

Hi Doug,

If you look into the local tsection.dat you can see what belongs to your route. If the entries start at "SectionCurve ( 0 ) 40000" you need a XTracks tsection.dat, at "SectionCurve ( 0 ) 376" the original tsection.dat from 08.05.2001 must be active in the global folder. So Hilary Clinton will not bother you anymore.

Greetings Jan

Translated with www.DeepL.com/Translator (free version)

Hi Jan,

I have the Cascades Crossing and I see 376 in the local tsection.dat
I also have global tsection.dat v57beta and the route runs fine for me?

[kapitaen]

@ derekmorton,
yes, that is correct, the routes are running fine.
Open the route in TSRE5 and change something in the track database. What does your local tsection.dat look like now?

Greetings Jan

[Vince]

Hi Doug, If I may

Attempting to edit a route CREATED with the old default \GLOBAL\tsection.dat and the users editing installation is the Standardized \GLOBAL\TSection.dat (that's the XTracks compatible version) will absolutely trash the ROUTE Tsection.dat

The route will run properly but do not attempt any editing involving track or roads.

The routes Tsection must be re-indexed by way of either the HORACE or ARCHIBALD utilities.
I believe there may be a writeup on this at the Steam4Me website but not sure of this.

regards,

[dcarleton]

We're talking Cascade Crossings from MLT, correct? That uses the default MSTS TSection. The first time you opened it in TSRE it should have offered to re-index the route-specific TSection into one compatible with XTracks. But the message doesn't exactly explain that that's what it wants to do; so many users just click past that step, thinking that it's not important. But it is important because TSRE doesn't know how to save a route-specific TSection unless it's compatible with XTracks. So you get errors instead.

Should point out also that if TSRE is allowed to update the route-specific TSection, then there's no need to run Horace or Archibald.