Standard scenario freezes after reaching final destination

[dick8299]

I am trying to get back into creating, and am having trouble with a simple standard scenario that I created for practice.

The player locomotive has only one instruction and that is the final destination which is a siding my test route.

After the player stops at the siding, the red ball scrolls across the F4 HUD, and then the HUD displays a message about no current destination.

Neither the esc key, or the F4 HUD pause button produces results. The only way to end the scenario is to ctr alt del to bring up the task manager and then exit Rail works.

Anybody have an idea what I am missing or done wrong?

[robbit]

try clicking the message or put a final message in the instruction

[artimrj]

I
After the player stops at the siding, the red ball scrolls across the F4 HUD, and then the HUD displays a message about no current destination.

I had this happen when I would go to the world editor and change stuff while running a scenario. Never had it happen while just playing, only after editting. Also sometimes for an unknown reason my keyboard will quit. None of the keys will work but the mouse will still move the levers. I have heard quite a few people state this. Sometimes if you ALT TAB out and come back the keyboard is live again. Not sure if any of this will help you but it is the only thing I can think of even if slightly related.

[robbit]

Sorry I think I misunderstood the issue

[OldProf]

You may be missing a nearly invisible message in the upper-right corner of your monitor, which also says that the scenario has been completed and contains a boxed X to click. Doing so should return you to the main program. To avoid this situation, insert a "Drive To" (or is that "Go To"???) instruction before the "Final Destination" instruction. While the "Final Destination" instruction does not allow for a message to the player, the "Drive To" instruction does have a message space. Closing the message box ends the scenario and returns the player to the main program.

Don't feel bad about not knowing this: RSC's scenario writers frequently make the same mistake.

Personally, I also would avoid entering the scenario through the world editor. The "game engine" isn't the brightest kid on the block and easily becomes confused by unexpected maneuvers, such as saving a scenario more than whatever number of times is sacred that day. As in most cases, follow the KISS rule.

[robbit]

You may be missing a nearly invisible message in the upper-right corner of your monitor, which also says that the scenario has been completed and contains a boxed X to click. Doing so should return you to the main program. To avoid this situation, insert a "Drive To" (or is that "Go To"???) instruction before the "Final Destination" instruction. While the "Final Destination" instruction does not allow for a message to the player, the "Drive To" instruction does have a message space. Closing the message box ends the scenario and returns the player to the main program.

Don't feel bad about not knowing this: RSC's scenario writers frequently make the same mistake.

Personally, I also would avoid entering the scenario through the world editor. The "game engine" isn't the brightest kid on the block and easily becomes confused by unexpected maneuvers, such as saving a scenario more than whatever number of times is sacred that day. As in most cases, follow the KISS rule.

This was my thought as well