Many thanks for bringing this to our attention, MSGSapper. It seems that uploading a route to the DLS is more trouble than it's worth, thanks to the devs. I'm with RW912, though I've used a few 3rd party assets, I've tried to document them carefully to make them easy to find, but this issue puts the kibosh on it. Maybe send it to a few friends, leave it at that. It never ends, does it.
Thanks Again, MSGSapper,
smyers
What makes this situation worse is that:
a. I am upgrading my 14 existing U.S. based T:ANE routes. These routes all had content that was
all previously either in T:ANE or on the DLS.
b. A number of the items that were in those routes has been moved out of TRS19 and the DLS to the DLCs.
c. The regional editions won't be able to to use my U.S. based routes because some of the content, that was previous in TANE or on the DLS, will now be in the free European DLCs, which I have been told some regions will not be able to access.
For us freeware route developers to be successful we need to be able to count on location stability for the content items contained in our route. Constantly moving them around to different platforms does not help us. The ideal situation for us route developers would be to have the content
only on the DLS. That way there is no question of where content items are located and regardless of Trainz version you can still get what you need. When someone purchases Trainz they should be given a 30 day FCT so they can get whatever they need from the DLS. That would be a lot easier for N3V to deal then the current situation.
I sometimes wonder if N3V goes out of there way to make things more difficult for us content/route developers with each new major version of Trainz. Of all the major versions I have had to upgrade my routes to, TRS19 has been the
worst experience so far, and caused me the most headaches. As an example I spent
all yesterday dealing with tech support issues for one of my TRS19 routes that were caused by this problem and some problems in TRS19.
Bob