Railworks America

I have a drivable backup of TS2014, but in it's protected folder I can't use the Workshop etc. I'm wondering how to get new Workshop scenarios in there.
I tried to copy some last year, from 2014 to 2013 as an experiment but that wouldn't work. (I had thought I could download them into the current version of Train Simulator and then copy them into the older application. NOT!)

AFAIK, workshop scenarios are not version dependent yet. TS2013 and older version might not properly recognize workshop scenarios, since these were introduced in TS2014.

I have just fired up one of my TS2014 backups with the Steam service running and it seems to sync and download my subscriptions as usual.
I have taken out a lot of subscriptions since, so this takes quite some time unfortunately. Eventually you'll see the Downloading bar turn blue, Decompressing, Installing Workshop Items and other messages pass by.

Perhaps when scenario writers start to include TS2015 exclusive features, such as 3D weather, there might be compatibility problems with TS2014.

I have one virgin TS2015 install in the Steam\steamapps\common folder which I keep updated daily, and separate working/hacking copies outside the Steam folder, on another drive even.
I maintain three working copies: Europe, UK and USA, and keep routes and assets more or less apart. Less routes and assets per install means easier scenario selection and fewer items in the route editor menus. And less chance of total freeze in case DTG/Steam mess up asset delivery, which does happen.

With the Steam service running, I can start any of the external installs, but not automatically update them. So when I acquire a new DLC or when Steam pushes out an update, I'll have to search for the new/updated files and copy them to the appropriate external install. With the increased use of complete asset packs in .ap format, this is relatively easy nowadays.
And to make modding/hacking easier, I have packed all assets into .ap files, after first thoroughly verifying them in the virgin Steam install. Any mod I make is to a copy of the file that resides in the correct folder under the provider's folder. When something goes terribly wrong, I delete my file or folder and the asset is back to virgin again.

If you use RW_Tools a lot to swap stock in scenarios you'll find that RW_Tools doesn't find any stock because of the .ap asset packs. So if you don't hack your engines and wagons, you can expand just the RailVehicles folders from the .ap packs, or expand them completely and be done with them. Any asset with the same path and filename outside the .ap pack takes precedence. The .pak caching takes care of the actual asset allocation, so make sure to 'clear the cache' when changes have been made.

IIRC once a workshop scenario has been played once, it is copied from the "temp" folder into a proper scenario folder, after which you can copy it as any other scenario.
The only difference remaining is that it is still identified as a workshop scenario, maybe this is why it doesn't work for you. But you can change that to standard. RW-Tools has a function for that.

Ericmopar wrote:I have a drivable backup of TS2014, but in it's protected folder I can't use the Workshop etc. I'm wondering how to get new Workshop scenarios in there.
I tried to copy some last year, from 2014 to 2013 as an experiment but that wouldn't work. (I had thought I could download them into the current version of Train Simulator and then copy them into the older application. NOT!)

Here's another question. How do you set up a drivable backup that will sync and instal Workshop items, without Steam finding it and updating automatically?

I put my TS 2014 Railworks folder into a new folder named TS2014bak and then created a shortcut to F: TS2014BAK/Railworks/Railworks.exe

I created that shortcut through Steam's window in their "Add a non Steam Game or Shortcut" listing.

I'd just update everything on my TS2015 and then copy over just the files I want to TS2014.

Actually - I was thinking about this, and there may be at least one version issue due to the introduction of the new Silverlight weather. Or will Railworks simply fallback to something else?