Genma Saotome, on 11 December 2021 - 03:08 PM, said:
Q: Will it be possible to separate the activity files from the rest of a route package while sharing the route package into several locations? Something like this:
/ one moniroute <--- miniroute specific activity folders
route package
\ a different miniroute <--- other miniroute specific activity folders
Hanging a loaded zip of .con files and another one of .wags and .engs into each of those mini-routes would make the idea complete. I've long wanted to have era-specific equipment referenced in the activity files w/o having to physically duplicate the route itself.
It is possible with two different vfs-config files, e.g.:
C:\packages\MSTS1.2.zip /MSTS/
C:\packages\route-package.zip /MSTS/ROUTES/
C:\packages\first-activity-package.zip /MSTS/ROUTES/ROUTE-IN-QUESTION/ACTIVITIES/
C:\packages\MSTS1.2.zip /MSTS/
C:\packages\route-package.zip /MSTS/ROUTES/
C:\packages\second-activity-package.zip /MSTS/ROUTES/ROUTE-IN-QUESTION/ACTIVITIES/
And both of these files can be added as "profiles" in the options, so they are selectable (one or the other). This can also be done with the con, wag, eng packages. One has to create as many vfs-config files as many different combinations of them are needed, and all of them may reference the same commonly needed zip files, while referencing only their own specific ones. The vfs subsystem will merge the contents of all the zip files mentioned in a config file to one common virtual directory structure where the game will run as if they were residing on a disk in uncompressed form.
Genma Saotome, on 11 December 2021 - 03:08 PM, said:
A potential problem to look at: What happens when two different .zips provide an identically named file (or folder) to a location where the duplicated file came from two people unaware of the duplication. This could very easily happen in \global\shapes and anywhere in \]trains.
The order of the rows in the vfs-config file does matter: the latter wins. If a zip contains a file, and another zip contains the same file with different contents, then the later standing zip in the vfs-config file will "overwrite" the prior's corresponding files. Exactly as if they were unzipped in the written order with overwrite-all option.