Update to version 50.5a coming on 26th February.

[Bradforth]

Hi all,
I have only got TS 2015 to run ok on my setup in the last few weeks, can anyone see anything in the list of updates that we need to be concerned about.

Regards,
Pete.

[gptech]

Nothing to be concerned about by the contents of the update Pete, but it would be prudent to make a backup of your existing installation 'just in case'. This is usually a waste of time, as updates generally run smoothly and every time we recommend it there are lots of posts saying "don't bother backing up, it's not needed"----unfortunately there's always the chance of something going awry and many of those who said "don't bother" were left rather upset and stuck after the *less than perfect* initial upgrade to TS2015.
If the backup isn't needed you've lost a few minutes of your life, but if you do it the smart way and leave the backup process running when you go to bed you don't miss the time anyway!

If you haven't the disc space for a backup just disable auto-updates from within the Steam client, take Steam off-line and wait till you read the reports that will be posted in here before deciding to allow the update.

[Bradforth]

Hi,
Thanks for your reply Gary, I have already got a backup of TS 2015 and 2014 on an external Hdd.
Regards,
Pete.

[bri2808]

Folks

While we are on the subject of back-ups I always back mine up to an external hard drive

But here is the point I never know whether or not I am doing the thing correctly...

When I transfer over the assets folder, should I click YES to merge and YES to copy and replace or should I be clicking NO

I always do yes to all questions but maybe I have been doing it incorrectly

Thanks

Brian

[ashgray]

Clicking YEs to merge folders and YES to copy and replace will restore your backed up files, overwriting those in your current main installation.

Ash

[bri2808]

Clicking YEs to merge folders and YES to copy and replace will restore your backed up files, overwriting those in your current main installation.

Ash

Thanks Ash, but will this overwrite any updated files

[ashgray]

The answer to that is YES, which is why it's important to be aware of exactly what you're overwriting. Restoring backups, whilst undoubtedly useful in some circumstances, can also mean that you end up overwriting an upgraded file. There are two ways of avoiding this potential pitfall:

1. Back up your TS2015 installation on a daily basis, but we all know how much hassle that would entail and how long it would take...
2. Note the date of the most recent DTG update to your TS2015 installation. Then, when running your Restore operation, ensure that any files that have been updated by DTG since you made your backup are not overwritten. This will of course mean that you'll have to sit there and constantly answer YES or NO to the overwrite question....

Ash

[gptech]

Brian,
when you say

When I transfer over the assets folder, should I click YES to merge and YES to copy and replace or should I be clicking NO

do you mean when copying over the files to your backup copy, or from your backup to effectively restore the game to a previous state?

[smartie38]

Thanks for the heads-up Matt.
I wonder if they've tweaked the TIR settings at all, I seem to recall they said they were going to revise it slightly, guess we'll soon see anyway.

Don't know why they'd need tweaking, my TrackIR worked flawlessly in the beta.

The only thing I found was the outside views were a bit awkward until you got used to it. Worked well in cab though. Did you think the settings were a touch oversensitive? I didn't bother to fiddle about with it as it was only beta, but it is good to see this supported fully in the game now (well, tomorrow).

Using the outside view with the TIR did take a little getting used to I admit but not to the point where I thought anything needed tweaking, I actually thought the sensitivity was spot on, didn't find it oversensitive at all, perhaps your settings in the TIR software was the cause, I was using the default profile.

[bri2808]

Brian,
when you say

When I transfer over the assets folder, should I click YES to merge and YES to copy and replace or should I be clicking NO

do you mean when copying over the files to your backup copy, or from your backup to effectively restore the game to a previous state?

Hi Gary

I meant when i return folders back after and update so things dont need reinstalling, things like soundpacks. However, i think Ash has answered the question (Thanks Ash) but if you have anything to add I would be grateful

[Mr395008]

Received a 46.7MB update and now my version is at v50.5a

[Juanillo99]

Documentation included with the update:

• HOWTOUSE_TS12Tech.pdf
• HOWTOUSE_TS13Tech.pdf
• HOWTOUSE_TS14Tech_P1.pdf
• HOWTOUSE_TS14Tech_P2.pdf
• HOWTOUSE_TS15Tech.pdf
• HOWTOUSE_TSEngineScripts.pdf
• HOWTOUSE_TSScenarioScripts.pdf

This documentation is in the ...\Steam\SteamApps\common\railworks\dev\Docs\.

[gptech]

Hi GaryI meant when i return folders back after and update so things dont need reinstalling, things like soundpacks. However, i think Ash has answered the question (Thanks Ash) but if you have anything to add I would be grateful

Yes, Ash covered that quite nicely but it was possible to read your original post both ways which also brings a certain degree of 'attention to detail needed' to proceedings.

Backups are great, the more the merrier---as long as they're of the right files, so a little care is needed if you overwrite an existing backup. In other words be 100% sure that what you're backing up isn't replacing good files with (possibly) corrupt ones. It's dead easy to delete, or move, a file/folder without realising, edit files incorrectly with intentions of fixing it tomorrow and forgetting, and probably dozens of little errors we all make without realising. If you've the disc space a pair of backups makes sense, so if you do mess it up you have a (hopefully) good earlier copy, even if it doesn't include any newer additions.

As this is primarily an update to the game core then assets and routes are unlikely to be changed but good assets and good routes are useless if the game core is corrupted so for this type of update making a backup of the core files (basically those in the RailSimulator directory) is of equal importance. Going back to the upgrade to TS2015, many wished they could revert back to TS2014 but because they only had assets and routes backed up didn't have that option. Admittedly that has really been the only time a core update/upgrade has had so many big problems, affecting so many people so the chances of a repeat seem quite slim.

[bri2808]

Hi GaryI meant when i return folders back after and update so things dont need reinstalling, things like soundpacks. However, i think Ash has answered the question (Thanks Ash) but if you have anything to add I would be grateful

Yes, Ash covered that quite nicely but it was possible to read your original post both ways which also brings a certain degree of 'attention to detail needed' to proceedings.

Backups are great, the more the merrier---as long as they're of the right files, so a little care is needed if you overwrite an existing backup. In other words be 100% sure that what you're backing up isn't replacing good files with (possibly) corrupt ones. It's dead easy to delete, or move, a file/folder without realising, edit files incorrectly with intentions of fixing it tomorrow and forgetting, and probably dozens of little errors we all make without realising. If you've the disc space a pair of backups makes sense, so if you do mess it up you have a (hopefully) good earlier copy, even if it doesn't include any newer additions.

As this is primarily an update to the game core then assets and routes are unlikely to be changed but good assets and good routes are useless if the game core is corrupted so for this type of update making a backup of the core files (basically those in the RailSimulator directory) is of equal importance. Going back to the upgrade to TS2015, many wished they could revert back to TS2014 but because they only had assets and routes backed up didn't have that option. Admittedly that has really been the only time a core update/upgrade has had so many big problems, affecting so many people so the chances of a repeat seem quite slim.

And your spot on, it didnt touch my assets (pardon the pun) and everything is all good. But it cant hurt and I will remember next time to also back up the core files.

Thanks again to both you and Ash for your help

Brian

[ashgray]

Hi Brian

I'll reply properly in 1/2 hour once i get home, re a good backup strategy that works well for me.

Ash