Atomic Systems

could anybody tell me when I put in tsection in the global folder and it overrides and I have to say yes, how can I keep the others for the different routes without effecting them. Naming them differently does not work.

It goes in the main global folder.

Zip up the old one and keep it in the same folder.

how can I keep the others for the different routes without effecting them. Naming them differently does not work.

That's exactly what you can do with the Train Store TSECTION.DAT swapping facility. Useful for specialised TSECTION.DATs sometimes needed by route developers, or for optimised TSECTION.DATs as produced by Route_Riter.


Tony

thanks for reply, but if the KB's are less then wouldn't it affect the other routes? as the one for the other routes would be changed

glenwood4 wrote:thanks for reply, but if the KB's are less then wouldn't it affect the other routes? as the one for the other routes would be changed

Hi
I've only come across two routes that required a "special" Tsection (One Italian one Czech).
The whole idea of a global tsection file...is it works for all routes, past and present.
So unless you have some strange route...just get the latest one.
Cheers
Jon

thanks for reply, but if the KB's are less then wouldn't it affect the other routes? as the one for the other routes would be changed

I'm not quite sure what you are saying, but Train Store gives you several options as to how TSECTION.DATs can be used. all the way from 'use any TSECTION.DAT', to 'use this TSECTION.DAT only'. Normally you are only unstoring 1 route at a time so inter-route conflicts are not possible. If you do want to unstore more than one route, then Train Store examines the options you have chosen, checks for any conflicts, and if there are any, gives you the option of removing one or more routes from your selection to achieve a compatible selection for this unstore. See 'TSECTION.DAT File Swapping' P 67.

I've only come across two routes that required a "special" Tsection (One Italian one Czech).
The whole idea of a global tsection file...is it works for all routes, past and present.

Yes, that is generally true, for simulation, but more care is needed if you are going to use the Route Editor. However, with the increasing size of the standardised TSECTION.DAT there is more interest in using optimised TSECTION.DATs from Route_Riter which are optimised for a specific route. If you use this facility, you have to have a method of swapping TSECTION.DAT files. Train Store will do it for you automatically, once you have set up TSECTION.DAT swapping.

Concerning the question of routes which do, or do not, require a special TSECTION.DAT, Okrasa's XTracks site has a very good page which lists most problematical routes. See Route notes. I don't know about the Italian route, but the Czech route, I believe, also is problematical in that it has modified some of the standard TSECTION.DAT shapes. so, it is not just a question of a modified TSECTION.DAT. Another route which unfortunately does this and ignores the TSECTION standards is L&PS. A pity.


Tony

Hi Tony
Your correct , I'd forgotten about the L&PS...but I think that installs as a mini-route by default...well it did on mine.
I've seen talk on using route specific Tsection, but personally I've not witnessed any benefit...although I do tend to use region specific separate installations these days.
As a basic user, I would still recommend just using the latest global Tsection..less to go wrong or get confused about.
Cheers
Jon

PS The latest version of RR has proberbly been fixed, but earlier versions kept making corrupt versions of Tsections.......that was a whole afternoon wasted a while back.

Hi Jon,

Why would RR producing an invalid tsection.dat mean a whole afternoon wasted?

When you run RR to produce a compacted tsection.dat file, it renames the original file as Master_tsection.dat, so if the new one does not work, all you need to do is rename Master_tsection.dat back to tsection.dat and you are back where you were?

Or am I missing something here.

Mike.

mikesimpson wrote:Hi Jon,

Why would RR producing an invalid tsection.dat mean a whole afternoon wasted?

When you run RR to produce a compacted tsection.dat file, it renames the original file as Master_tsection.dat, so if the new one does not work, all you need to do is rename Master_tsection.dat back to tsection.dat and you are back where you were?

Or am I missing something here.

Mike.

Hi Mike
Only because I thought I was doing something wrong...so persevered with it.
Later, reading on the forums it had been a discovered fault, on some routes. Is it fixed now?
Cheers
Jon