MSTS Train Store lets you select global tsection.dat versions on route by route basis. As Train Store doesn't work with ORTS, what's the way to do this in Open Rails? I think this can probably be done by making mini-routes and adding their folders to ORTS but that's inconvenient.
-
Last edited by advut; 01-30-2018, 10:05. -
Unless a route will not work with the latest tsection I do not use an older version in ORTS. If the route will not work with the Tsection in the Train Simulator folder I will make a mini just for that route and add it to the OR profiles list. It is not really inconvenient unless you are short of disc space. All the mini needs for OR is Global, Routes, Sound and Trains with consists and trainset in it, all the rest is unused baggage.Beer is not a matter of life or death, it is much more serious than that. -
You can just put tsection.dat file in route "openrails" directory. No need for mini routes in open rails.Comment
-
Charles,
The tsection.dat files that sit in your route's folder govern dynamic track. I suspect that the tsection file they're referring to here is not the route-specific tsection, but the global one. According to the manual from X3997, section 15.7, a 'supplement' to the global tsection can be added to a route using an OpenRails sub-folderComment
-
As Train Store doesn't work with ORTS
If you keep the msts directory structure and msts registry settings, train store works fine?Comment
-
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.
Yes mini-routes are inconvenient and by using them your choice of rolling stock gets limited.
Train Store doesn't work with ORTS as easily as it does with MSTS, it will move all the other unnecessary items but won't launch ORTS. I also think Train Store shouldn't be used when using SSD.Last edited by advut; 01-31-2018, 09:18.Comment
-
Too much disk writing reduces SSD lifespan.Comment
-
uh, too much disk writing will reduce any drive's lifespan, SSD or traditional....If you like what you see here at Trainsim.com, be it the discussions and knowledge in the forums, or items available in our library, I hope you'll consider a paid membership to help support keeping the site operating.... Thanks!Comment
-
Is that applicable to using Train Store? I do not believe that storing and un-storing files with Train Store actually moves them. I believe that it is only the internal Windows allocation that references them as being at a different folder location.
Please correct me if I am wrong.Comment
-
It most certainly does.
Check the trainstore folder after you have stored a route, or run an activity.Comment
-
Hi Derek,
Apologies, but I'm not certain which part of Dennis' question you've answered!
Several websites offer answers to the Copy/Move question, but I think this puts it in plain English :
When moving to a new location on the same drive, the file's data doesn't actually have to be moved. In this case, a move operation is simply a change to the drive's directory or file listing.
- The directory of the target folder is updated to include the file being moved in.
- The directory of the folder where the file used to reside is updated to no longer list the file.
That's it. And because the actual contents of the file are never touched, it's pretty quick.
As the TrainStore instructions specify that the storage folder must be on the same partition (ie drive) as the MSTS installation, it's almost certain that MOVE is used instead of COPY. To the user, the files will appear to be stored in the target folder, but, in fact, haven't been physically moved.
Cheers,
Ged
Comment
-
Hi Ged,
I agree that only the pointer to the file in the MFT is changed.
This level of discussion is of no use to users, it will only confuse them.
The user will see that the file has moved, even though it hasn't.Comment
Comment