Matej Pacha, on 07 February 2014 - 06:05 AM, said:
Sometimes it's necessary to have many MSTS (with route and global) folders, what can be easily linked to ORTS using "Installation profiles" - Add button in the menu. But what about trains? Sometimes I use the same trainset for all the routes, so I have to copy or move all the data to the MSTS folder in use. It would be great to have one Trainset folder for all routes. Or, just the option to consider one Trainset folder in more than one "Installation profile".
Matej, I've thought about that problem for a long time and I think I now have a suggestion that would help. You know how Libraries make it possible to logically insert many directory trees (each of which "lives" on different branches of the tree) into a library making it look like they're all "living" there? And how, in the consist file, on the last value on each WaagonData line is the directory where the .wag is found?
Well if the construction of the consist path (in consist.cs) could accept multiple directories concatenated into one value when it goes for that directory name then people could do this:
End users set up new directories that organize their roster they way they like. Could be things like "Locomotives_New_1939-1954" and "Locomotives_New_1954-1974" and so on. Put their .wags and .engs into those new directories. The way you do that doesn't have to be the way I do it. Then junction those new directories into how ever many different \trainset folders they want. The OR code comes along to construct the Wagondata path and it finds "Locomotives_New_1939-1954\3dt_Southern Pacific F7" and because of the junction, it can find the right .eng file.
It's conceptually just like the MS Library concept.
You could name one of those new directories "Use Everywhere" and junction it into all \trainset folders. Whatever .wag and .eng directories you put in there would then be available, well, everywhere. :wallbash: