Duplicates of "Subscribed" Workshop Routes in StoreThem

[OlPaint]

Mike

I just realized that the Steam/Railworks server loads another second copy of a "Subscribed" Workshop Route when I launch TS2014. (for example: Majestic Falls Railroad). This is even after I have Stored all the Available Routes including that "Subscribed" Workshop Route with all my other Routes into the StoreC directory with 'Store Selected' command. As a result, I end up with a copy of the "Subscribed" Workshop Route in both the /Content/Routes/ folder (when it should have remained empty) and also a copy of the "Subscribed" Workshop Route in the /RailWorks/StoreC/Routes/ folder. Then, when I either do a 'Store Selected' or 'Restore Selected' action on the selected "Subscribed" Workshop Route, I end up with a double listing of the "Subscribed" WorkShop Route in either the "Available Routes" or "Stored Routes" listing depending on the Route and action I have chosen. I have to physically delete one of the copies from the /RailWorks/content/routes/ or the /RailWorks/StoreC/Routes/ folder to return the listings back to normal and remove the duplicate in the listing.

OlPaint

[mikesimpson]

Hi OlPaint,

It may be that Steam checks every time you start TS2014 for 'Subscribed' routes and if they are not there then it downloads it again. I will have to check that. I did not have any of these subscribed workshop routes, so never thought about it.

Mike

[artimrj]

Hi OlPaint,

It may be that Steam checks every time you start TS2014 for 'Subscribed' routes and if they are not there then it downloads it again. I will have to check that. I did not have any of these subscribed workshop routes, so never thought about it.

Mike

I think your right Mike as I have a separate bare bones install of RW I use for testing and it has all the subscribed routes, that I keep deleting and they keep coming back.

[OlPaint]

So far, the only work-around that seems to work to prevent Steam/RailWorks server for downloading a duplicate route file is to keep each of the "Subscribed" Workshop Routes stored in the Available Routes listing. But you still must, at least once, 'Store Selected' for that route and immediately 'Restore Selected' to the Available Routes so that the StoreThem utility can restore those Assets that the "Subscribed" Workshop Route needs to run.

OlPaint

[mikesimpson]

Yes, I can't see any way around this, it is not as if all the workshop routes had the same name, I will try to find out why they keep getting downloaded.

Mike

[gkbaldwin]

A possible solution

I use the workshop and download and install routes, scenarios etc. I fined that if subscribed too, then Railworks will check each time you start it to synchronize all subscribed items. I found the way around this is once the route or scenario(s) is installed and present. I temporarily change the content and asset folder names, ie, Content.dev and Asset.dev (I keep a standing copy of both in my Railworks), start Railworks, go to Collection, Workshop , where it will list all subscribed items (and start downloading again. I then unsubscribe (delete) said subscribed items and exit Railworks. I delete Content and Assets folders if present and change back the Assets and Content folders I had temporarily changed earlier, which still contain the subscribed items and then restart Railworks. You will now have the subscribed route or scenario, but Railworks will not download a new copy since you have unsubscribed to it.

I know this sound a little convoluted, but it does work and I don't see why the steps couldn't be automated. The downside is if the items you unsubscribed too get updated in the workshop you won't automatically receive the updates unless you subscribe to them again, which means you will need to repeat the above steps again. As always make sure you have a backup before you do a new subscribe so not to accidently over-write something. I have done this for a ton of stuff and have not lost any items and continue to expand my library of routes and scenarios.

Regards, Gerry

[OlPaint]

gkbaldwin

Your possible solution does not work for me. After renaming Content.dev and Assets.dev folders, I crash to desktop when attempting to launch Railworks.

OlPaint

[gkbaldwin]

Sorry, I left out an important step. Once you rename your content folder to content.dev and assets folder to assets.dev then you need to replace them with dummy folders of content and assets. I use a copied set of default content and asset folders that I then change back to content.def and assets.def. The reason it crashes it looks for the core files upon loading and if missing will crash. Insert this step before going on line to unsubscribe and all should work okay. So basically you have a duplicate set of the content and assets folders that you swap places when doing the unsubscribe and then change back when completed.

Sorry for missing that part.

Here are the steps again.

1) Duplicate a set of the Content and Asset Folders with different extensions eg. Content.def, Assets.def to use for the swap. It can only contain one route in the content folder and a minimum of Kuju and RSC in the Assets folders I believe as I use my copy of the default content and asset folders (Plain vanilla) for mine.

2) The other set of content and assets folders will be you current in use folders installed.

3) Start Railworks with current production content and assets folder (no extension) and go to Collections, Workshop and subscribe to the routes, scenarios, etc. you want. Once subscribed they should download and install. Some exception require you once subscribed to exit and restart Railworks before they are fully available. I always do a test to validate that they are fully available. Then exit Railworks.

4) Once verified available change the content and assets folders to content.dev and assets.dev These contain the subscribed files.

5) Using your duplicate folders from step one, change the Content.def and Assets.def to Content and Assets (dropping the extension)

6) Start Railworks and go to Collection, Workshop...you should have a screen showing all subscribed items. Unsubscribe or delete them and the exit Railworks

7) Now swap back to your original set by reversing the steps.... change Content and Assets to Content.def and Assets.def and the change back the Content.dev and Assets.dev to production by dropping the extension.... Content and Assets respectively.

8) Start Railworks....you should now see the newly subscribe items (verified in step 3), but if you go to Collections, Workshop you should show no subscribed items listed. This way Railworks will not download these items again if stored and not present when Railworks does its synchronization.

Again the downside to this is maintaining duplicate sets of Content and Assets folders, and if the subscribed items are updated later you will not automatically get them since in effect you have turned off synchronization of the subscribed items. You would manually have to go through the above steps again to re-subscribe to the items repeating the above steps. However, getting items from Workshop I find in most cases I only get complete (no beta) items so updates are usually not common.

Again, the swapping part could be automated and make the process more easy to do, but not my area of expertise.

Hope this clears up the missed steps from my original post.

Gerry

[OlPaint]

gkbaldwin

Now that works. Great information. I was able to bring my Workshop Scenarios collection up to date with no real problems by swapping the content and asset folders as described above. Neat. The duplication of Routes issue has been eliminated in my installed version of StoreThem.

Mike

Can you add a routine to StoreThem that will accomplish the Content and Asset folder swapping that gkbaldwin has described?

There must be a "Subscribed" Workshop Routes and Scenarios list that Steam/RailWorks maintains for the local content and assets update processing. This content and asset folder swapping that seems to work must defeat that scheme.

OlPaint