harryadkins wrote:I have one suggestion...your concerns need to be voiced to RSC in the form of an email. My experience has been that they do read and respond to emails. We can debate for days on the forums, but RSC wants to hear from us personally. Several changes and improvements over the past few months have resulted from user response. It's the best way to get results.
Harry
Harry,
I understand your point, but what do we do in the mean time? Do I continue to move forward updating my route and adding new updates to the file library only to find out the updates I've added do not conform to the new EULA, or do I wait? Realize I could still be waiting until this time next year for clarification on the EULA? We have reached a damed if you do, damed if you don't situation

Like I stated earlier, can I still upload what was once default assets with my route, or can I only upload my route in rwp format and let the end user try and figure out what he/she needs to run the route? Also remember I do this as a hobby, if it's going to take me numerous hours to create a readme file that lists every asset used by the route and where that asset can be located, then I'm done as well. I already have a job, I do this for fun and I don't feel like making my hobby my job. And lastly the fly in the ointment, what happens if RSC decides for some unknown reason my route would add to their bottom line? According to their current EULA, they can take anything we create and use it for their own gain. In other words, they can take my route, created a few pieces of rolling stock and locomotives for it a couple of scenario's and sell it as DLC and all I can do is sit back and watch it happen. Will it happen to my route I doubt it, but it could and with that thought I have to ask myself why I should continue to create anything for Train Simulator 2013. One last point, RS Derek does read these forums, maybe not on a daily basics, but I'm pretty sure the folks at RSC know what all the buzz is about.
Rich S.