We seemed to have diverged a bit from what I intended here in this thread, although I am finding that it is a good discussion.
The strategy I intend to use:
Currently I have 14 layouts that are TANE specific versions and all of which have ProTrack. I also have TRS2012 specific versions also of those same routes and they don't have ProTrack.
It will be the TANE specific versions that I will basically clone and turn into separate TRS2018 versions assuming that I don't find that I have too much of the old content on those routes which is no longer functional under TRS2018 to make it practical. As I produce TRS2018 specific versions of each layout I will no longer provide tech support for the older versions.
This strategy is basically the same one I used when I went from TRS2012 to TANE. Keeping separate TRS2012 specific versions and allowed for some backward compatibility for those choosing NOT to move to TANE at the time. It turned out to be fairly successful although a bit of a pain to implement, as content for the TANE versions had to be changed (mainly the track). I expect the same will happen here although it may turn out to be much more work in the end.
I have never been happy with the available sub-par 2D ground textures and moving to 3D textures, something I recommended years ago to N3V, is a big move and a good one. The devil of course will be in the implementation details.
The big problem will of course be HOW MUCH of the older content will be found to be no longer functional under TRS2018, and how difficult in practice fixing that content will be.
Bob
The strategy I intend to use:
Currently I have 14 layouts that are TANE specific versions and all of which have ProTrack. I also have TRS2012 specific versions also of those same routes and they don't have ProTrack.
It will be the TANE specific versions that I will basically clone and turn into separate TRS2018 versions assuming that I don't find that I have too much of the old content on those routes which is no longer functional under TRS2018 to make it practical. As I produce TRS2018 specific versions of each layout I will no longer provide tech support for the older versions.
This strategy is basically the same one I used when I went from TRS2012 to TANE. Keeping separate TRS2012 specific versions and allowed for some backward compatibility for those choosing NOT to move to TANE at the time. It turned out to be fairly successful although a bit of a pain to implement, as content for the TANE versions had to be changed (mainly the track). I expect the same will happen here although it may turn out to be much more work in the end.
I have never been happy with the available sub-par 2D ground textures and moving to 3D textures, something I recommended years ago to N3V, is a big move and a good one. The devil of course will be in the implementation details.
The big problem will of course be HOW MUCH of the older content will be found to be no longer functional under TRS2018, and how difficult in practice fixing that content will be.
Bob