One can hardly say that it is "asking to much of RSDL" to add functionality (timetabled scenarios, and all the features necessary to make them work properly) that there can be no doubt was specifically planned, and was clearly and unequivocally promised as one of Rail Simulator's key defining features.AdamsRadial wrote:It might be asking too much of RSDL to add that sort of scripting capability to their product, but we do not know what sort of hooks have been left in the code to allow for future enhancements.
I don't think that anybody ever suggested that "crying over" the deficiencies is productive: that was certainly not the point of the thread. Either the problems are fixed in time, and all is well, or they are not fixed, and I and many others like me will cease to have an interest in using Rail Simulator (much as I hardly ever use Train Simulator), and the commercial viability of Rail Simulator will be at stake.I think we should be drawing these sort of things to their attention, but equally, if the sim can't handle it, what's the point in crying over it?
No doubt the 3d exporter is a very high priority, higher even than the signalling and operational deficiencies, but that is irrelevant, since it is being developed by somebody other than RSDL. Apart from fixing the major stability issues/bugs, I can't imagine what could possibly be a higher priority for RSDL than fixing the seven critical operational issues (that is, the six identified at the beginning of this thread, and one of the two (route locking) from the "objective criticisms" thread, the other one being duplicated in the list from this thread).But, as far as priorities go, I'll put scripting well down the list; I agree with BigVern, until content creators are able to add new items to the game, it's very limiting. I don't want to populate my small plot of North Kent with uprooted Somerset items, much as I would have been loath to have filled it full of the Settle and Carlisle stonework.
Bear in mind that different people specialise in different things, and one cannot, for example, sensibly have the artists working on coding or vice versa, so priorities only make sense in so far as they are priorities for a particular person or team. The fact that Derek is working on an 08, for example, doesn't hold up people working on the signalling because Derek would never work on the signalling, and the signalling people (if there are any of the original people from Kuju who did signalling left) wouldn't know how to do 3d models and textures.

