Railworks America

Finally, a first edition of Part II of my Scenario Authors Guide.

Part I is a starter tutorial, Pat III is about LUA scripting. Part II covers everything between these two parts.

It is not finished yet, there still is a lot to discover, even for me ...

Download it here: https://drive.google.com/open?id=0B5xmS3GoYKV1UjBJeHhIOFlOSzQ
Note: The document is included in the setup files for LuaCreator as well.

Thank You, Rudolf.

Well done, Rudolf!

Rudolf, your guide is now in the RWA file library here.
I have merged your 3 tutorials into a single zip file, along with the example scenarios.

I've been looking through your guides, based on the belief that I can always learn something. At one point, you wisely recommend not testing a scenario in progress by running it directly from the editor, However, I cannot agree with the alternative you suggest: using ESC to stop the scenario as soon as it opens and then clicking Restart to test it. One of the most obvious signs that a scenario has been launched from the editor is that switch stands do not appear until the switch in question has been changed by some means. The same is true after "restarting" the scenario as you suggest, which leads me to suspect that the freshly edited scenario remains undigested, so to speak. In my opinion, the only really safe and sure way to test a just-edited scenario is to use ESC followed by a complete stop, followed by shutting down and restarting TS and, for good measure, rebooting the computer doesn't hurt at all. In fact, if the process didn't take so much time, I would even recommend a cache verification between editing and test driving.

One thing I've learned from running, writing, and editing scenarios is that our beloved simulator is inherently unstable and that it constantly shoots itself in the foot (when not in some vital organ). The number of faults reported by each verification has convinced me that nearly every file is damaged or at least altered in a potentially damaging way every time that the program stumbles and shuts itself down, producing one of those delightful, unreadable DMP files.

Here more than ever: better safe than sorry.

In general, however, I salute you for a job well done. You've filled most of the information gaps left open by RSC/DTG's floundering users' manuals.

OldProf wrote:I've been looking through your guides, based on the belief that I can always learn something. At one point, you wisely recommend not testing a scenario in progress by running it directly from the editor, However, I cannot agree with the alternative you suggest: using ESC to stop the scenario as soon as it opens and then clicking Restart to test it. One of the most obvious signs that a scenario has been launched from the editor is that switch stands do not appear until the switch in question has been changed by some means. The same is true after "restarting" the scenario as you suggest, which leads me to suspect that the freshly edited scenario remains undigested, so to speak. In my opinion, the only really safe and sure way to test a just-edited scenario is to use ESC followed by a complete stop, followed by shutting down and restarting TS and, for good measure, rebooting the computer doesn't hurt at all. In fact, if the process didn't take so much time, I would even recommend a cache verification between editing and test driving.

One thing I've learned from running, writing, and editing scenarios is that our beloved simulator is inherently unstable and that it constantly shoots itself in the foot (when not in some vital organ). The number of faults reported by each verification has convinced me that nearly every file is damaged or at least altered in a potentially damaging way every time that the program stumbles and shuts itself down, producing one of those delightful, unreadable DMP files.

Here more than ever: better safe than sorry.

In general, however, I salute you for a job well done. You've filled most of the information gaps left open by RSC/DTG's floundering users' manuals.

Thanks for your comments. I will check if I can verify this (should be possible in principle). I agree the whole game lacks stability. Complete hangups that require to log out of your account as they happen sometimes, should never occur. We also know about the extremely poor testing capabilities of the DTG team, especially TS2015 never should have been allowed to release with the bug most customers detected within a day. I'm afraid not much can be done about it, except for flagging the game at steam and hope steam will stop sales because of this. At the moment it is workable but not great.

Thanks RudolfJan. These guides have become my go to advice for friends who ask me anything about scenario editing. In truth I am terrible at making scenarios and the last person anyone should go to for advice, but these guides make me look like a genius.

Thanks Rudolf!