Using RW_Tools in the scenario creation process
Posted: Thu Jan 11, 2018 12:13 pmA couple of days ago, while editing a complex switching scenario for the nth time, I ran into an all-too-familiar problem: player train (PT) instructions that had worked just a few minutes before suddenly turned red in the Timetable Editor because "no final destination" existed -- this despite the fact that a correct final destination marker sat there right before my eyes. I had followed all of the familiar edit & test procedures that all experienced scenario makers know and that I will not list here.
Having seen this before, I knew the drastic solution: delete all of the PT's instructions and start over, but this time a sort of rescue system occurred to me. After shutting down TS, I opened RW_Tools' scenario editor and selected the correct route and scenario. Without opening the scenario for editing, I clicked on the "Display Work Order" button. This opens a new window containing all of the information regarding the PT, including text messages (but not LUA messages) contained in those instructions. There's a "Print" option, but I chose instead to copy everything and paste it into a word processing document (I prefer Word, but any notebook program would work as well.
I then opened my scenario again in the Timetable Editor, after having set RS2018 to run in a window, so I could Tab back and forth between RS and the text I had copied from RW_Tools. Bravely now, I deleted all of the instructions from my PT. Without saving and restarting (although hindsight tells me that might be advisable), I re-entered all of the instructions, including the Final Destination that supposedly did not exist previously. Presto-Change-o; Abracadabra: all was well again and continued to be so. NOTE: I do not recommend copying and pasting instruction texts from the word processing file to the scenario editor, which sometimes self-destructs in reaction to this time honored practice.
This is a bold move, but employing Mike Simpson's miracle-working gift to all of us at least makes it manageable.
Having seen this before, I knew the drastic solution: delete all of the PT's instructions and start over, but this time a sort of rescue system occurred to me. After shutting down TS, I opened RW_Tools' scenario editor and selected the correct route and scenario. Without opening the scenario for editing, I clicked on the "Display Work Order" button. This opens a new window containing all of the information regarding the PT, including text messages (but not LUA messages) contained in those instructions. There's a "Print" option, but I chose instead to copy everything and paste it into a word processing document (I prefer Word, but any notebook program would work as well.
I then opened my scenario again in the Timetable Editor, after having set RS2018 to run in a window, so I could Tab back and forth between RS and the text I had copied from RW_Tools. Bravely now, I deleted all of the instructions from my PT. Without saving and restarting (although hindsight tells me that might be advisable), I re-entered all of the instructions, including the Final Destination that supposedly did not exist previously. Presto-Change-o; Abracadabra: all was well again and continued to be so. NOTE: I do not recommend copying and pasting instruction texts from the word processing file to the scenario editor, which sometimes self-destructs in reaction to this time honored practice.
This is a bold move, but employing Mike Simpson's miracle-working gift to all of us at least makes it manageable.
