Railworks America

Can anyone out there tell me how to eliminate the 20 second timeout on a 0 mph Stop instruction? I can change the timeout to 0 seconds on a 1 mph Stop instruction but not a 0 mph stop. The editor simply ignores a 0 second duration in a 0 mph Stop. I'm using the timetabled view, by the way.

Thanks

What is the purpose of stopping 0 seconds? It is no stop anymore. Sorry, but I don't understand this. Maybe I'm just too narrow-minded.

It could help to adjust your settings through selecting the stop at icon above the locomotive. Here you might be able to change it to 0.

The purpose would be to display the 'Achievement Text Successful' message immediately upon stopping instead of waiting out the 20 second delay. You could still stop as long as you wanted to but you would get the message right away.

If it was set at 1 second, I personally wouldn't even notice the tiny delay. Sometimes I'm not even sure if the train is completely stopped for a sec or two, by then your message would already have popped up.

Tori

I'll try to be more explicit. Let's go to the Scenario Editor (for any pre-existing scenario) and select the Tool Box in the upper left corner. There, select 'Timetable View'. In the Timetable View, add a 'Stop' command. Click on the new 'Stop' command and enter any siding destination in the 'Set Destination' field. Now, four fields are filled in for you and can be altered. 'Duration' (of 20 seconds), 'Performance' (75%), Speed (0mph), and 'Allow Reversing' (checked). The only field in question here is the 'Duration' field. Change it to 0 seconds. Now run the scenario and come to a complete stop (0mph) at the destination entered. This is what I always see...I have to wait for the red progress bar to reach 20 secnds before it displays the 'Achievement Text Successful' message. The 'Duration' can be increased (for whatever reason) but it cannot be reduced to 0 seconds to permit the 'Achievement Text Successful' message to be displayed immediately upon stopping. I consider this to be a major pain and would like very much to find a way around it.

Pop, I'm sorry, but it's not really a huge issue to wait 20 seconds in a one hour scenario, is it? I wait a lot longer in line at McDonalds for coffee! (don't go ballistic, it's just a comment) Just sit! It's part of the game, always has been!

I am just starting to write scenarios myself and have not worked in the timetable view, but I have found that most "issues" like this in scenario writing turn out to have legitimate reasons for being the way they are in the game (usually something to do with AI interactions). It does sometimes prevent me from doing exactly what I want, but I find that most players are already familiar wih such compromises and don't care nearly as much as I do. Personally, I would set it for 1 second (you said that works, right?) and move on to the next "compromise" (headache!) that you WILL encounter. Heck, sometimes, after finishing the writing of a scenario I come back to these issues and for some reason I then CAN do what I wanted. The scenario writer has a bit of a mind of its own... it has to... that's the "dispatcher" talking... so, when writing, we have to "play along nicely" to see what it will give/allow us.

Thoughts from the apprentice corner,
Tori

Toripony wrote:I am just starting to write scenarios myself and have not worked in the timetable view . . . .

You should try Timetable View, Tori - you will love it once you do.