Different Versions of Global TSECTION.DAT for Different Routes

[advut]

I don't want to debate about whether Train Store actually writes too much or not but because excessive disk writing hurts SSD drives more than HDDs I will play it safe and not use it when using SSD drives.

[derekmorton]

I have yet to wear out an ssd.
I currently have 3 ssd's in my system.

1. os win7
2. msts/or
3. backup drive

Which one would you think would wear out first?

1. os drive
2. backup drive
3. msts / or

I use train store as a diagnostic, it picks up faults that other programs don't pick up, so it gets used all of the time.
It does one other thing that I use, it isolates just the rolling stock for the activity, that I modify BEFORE I run the activity.

So my experience is that MSTS / OR is less likely to wear out an ssd that an os drive.

[derekmorton]

Excessive driving of your car hurts it too.
Does that stop you driving your car?

[dforrestc]

Thank you Goku, you are so helpful!

I tested the Valladolid-Ariza V4 route. This route supplies a tsection.dat file. I can play this route either by putting this tsection.dat in the default global folder or by putting it in the "openrails" folder that's inside the route folder. If I don't do any of this I get errors in ORTS.

Back to the subject of the thread.

advut and Goku, are you saying that when you are running MSTS it reads the tsection.dat file in default global folder and when are running Open Rails it reads the tsection.dat file in the route's "openrails" folder?

[ebnertra000]

Back to the subject of the thread.

advut and Goku, are you saying that when you are running MSTS it reads the tsection.dat file in default global folder and when are running Open Rails it reads the tsection.dat file in the route's "openrails" folder?

I believe when running OR it reads the global tsection and the OpenRails folder tsection, using them together. Then there's the route's tsection for dynamic track

[GokuMK]

advut and Goku, are you saying that when you are running MSTS it reads the tsection.dat file in default global folder and when are running Open Rails it reads the tsection.dat file in the route's "openrails" folder?

Yes. Open Rails will read global tsection.dat from route/openrails/tsection.dat file if exist instead of global/tsection.dat.
Route dynamic track tsection.dat is always loaded after global tsection.dat.

You can do more with OR. You can use include statement in route/openrails/tsection.dat file to include global/tsection.dat and then specify only route specific additions.

Of course all of it works in TSRE too.

---

For me there is no need fot Train Store when using OR. MSTS was loading too long when you had lots of routes and trains but OR has no such problem. Also OR handles custom tsection.dat files.

[dforrestc]

Yes. Open Rails will read global tsection.dat from route/openrails/tsection.dat file if exist instead of global/tsection.dat.
Route dynamic track tsection.dat is always loaded after global tsection.dat.

So, for us MSTS and Train Store users who have a bunch of MSTS route-specific tsection.dat files with names referring to the specific route folder, am I correct in saying that we can copy these to the route's "openrails" folder, give them a tsection.dat name, and OR will use these. MSTS will continue to use the one in the global folder.

From there further modifications can be made as noted by Goku

[GokuMK]

Yes.

[advut]

Sorry for late response. I assume I won't need to say anything else as Goku has explained the situation clearly and earlier than me. Just be aware that, non standardised route specific global tsection.dat files may not be compatible with routes that use standardised global tsection.dat. So, for maximum compatibility you can keep the standardised global tsection.dat in 'global" folder and when playing non standardised tsection routes in MSTS specify the non standard tsection.dat from Train Store interface as obviously MSTS won't read from "openrails" folder.

[geepster775]

It does beg the question as to why there are routes with non-standardized tsections. Just what unique features do those routes have that required the route builders to go rogue in the first place?

[derekmorton]

Non standard tsections probably started with language difficulties.
I have just been through a process getting part of the Italian community onto the standardised tsection.
There are a number of European routes that still use unique tsections.