Change 'Train Simulator 2013' labels - Proposal/poll

[Juanillo99]

Would you like that the 'Train Simulator 2013' labels of the thumbnails in the 'Newest Files' will be replaced by 'Train Simulator 2016'?

Please, give your opinion and vote in the poll.

[gptech]

If we have a TS2016 section you can bet your bottom dollar that we end up explaining to folk that earlier addons will work in TS2016---far better, in my opinion, to change the label to "TS2013 onwards", or similar.

[atlasduff47]

If we have a TS2016 section you can bet your bottom dollar that we end up explaining to folk that earlier addons will work in TS2016---far better, in my opinion, to change the label to "TS2013 onwards", or similar.

Agreed!

[maxtedrw]

How about just leave it as Train Simulator and for the asset author to identify if it is suitable. To be honest most freeware authors will only know it is suitable for the version tey had at the time and will have no idea about forwards or backwards compatibility. Rather than sort of imply it why don't we just mark the file with the generic version.

I have no idea of my assets work in Rail Sim, or if some work in Railworks - and no way of establishing this.

[Springer6]

If we have a TS2016 section you can bet your bottom dollar that we end up explaining to folk that earlier addons will work in TS2016---far better, in my opinion, to change the label to "TS2013 onwards", or similar.

I agree with this.
However, we must bear in mind that later addons do not always work in earlier TS versions. Not every route or item of stock made for ts16 ( or mods of them such as repaints etc.) will work in ts13 or ts14 and even ts15 ! E.G.s. dB br155 (& repaints) does not work fully in ts15 and Miami route (& therefore scenarios for it ) does not work in ts14.

A bit difficult to have an entirely accurate label perhaps?

[davep]

If we have a TS2016 section you can bet your bottom dollar that we end up explaining to folk that earlier addons will work in TS2016---far better, in my opinion, to change the label to "TS2013 onwards", or similar.

I agree with Gary.

[gptech]

bear in mind that later addons do not always work in earlier TS versions

True, but there are also addons/reskins in the library that don't work on the version they were written for!! ---- or at least not without having to change file paths to suit a *standard* set-up of the game, or work out which textures folder also needs copying.....
We're talking about a generic label here, if a reskin or whatever was produced for an earlier version of the game than the current one then the author should make that clear in the download description if they're unsure whether it'll work across versions.

[johnrossetti]

I havn't yet grasped what will (or not) make a newly written scenario NOT run on an earlier version of TS.
If there is an action within a scenario that only allows it to run on TS2016 then the writer should say so, otherwise as has been said earlier it will need a lot of explaining if a scenario appears in 2016 because it's newly written but it runs ok in TS2013 etc
So I'm happy to keeps as is but rely in the writer to state exceptions.
Cheers

[Springer6]

I havn't yet grasped what will (or not) make a newly written scenario NOT run on an earlier version of TS.
If there is an action within a scenario that only allows it to run on TS2016 then the writer should say so, otherwise as has been said earlier it will need a lot of explaining if a scenario appears in 2016 because it's newly written but it runs ok in TS2013 etc
So I'm happy to keeps as is but rely in the writer to state exceptions.
Cheers

I think that it's more that some routes will not run in earlier versions. Therefore any scenarios posted for those routes would not run in TS 2013 say, even though the "label" will currently read TS 2013.

As you say probably best to keep as is with the author stating exceptions when known. All will change post ts16 anyway.