Why do these things happen?

[Janine]

After a few months of not touching the Scenario Editor at all, I thought I could make a simple 15 to 20 minute long scenario simulating the red trolley from Old Town to San Diego. Everything worked fine (except for a few dumpfile crashes, even though I saved literally every minute or after every change, even a simple one) and I was able to do a few testruns. After adding a couple of AI trains (one Surfliner, one BNSF freight and three other trolleys), all time tables were set up and still everything worked properly. Then I simulated the entire thing by playing it at 4x speed through right in the editor. Everything looked lovely, so I saved once more and decided to postpone the departure of the BNSF freight by 5 minutes, so it would overtake me a bit later on.

And then ... BANG ... two timetables were completely gone, my own train was suddenly at the final station instead of the first one (even though the timer was reset to start) and another AI train (the Surfliner) was at a completely different location. Too bad I saved BEFORE I noticed all the changes. I couldn't revert them obviously, and when I tested the entire scenario, it was over (successfully) before I could even depart, since I was already at the last stop.

Now my question to you guys: Why do these things happen? Did that happen to you as well sumtimes?

~ Meow

[artimrj]

Not sure why it is happening to you. One thing though I do not use the VCR mode to check the thing and then save. That could very well be your problem. Save before VCR, then quit and come back to the editting. The VCR mode thingy has been a culprit of a lot of things over the years.

[OldProf]

I second Bob's comments about the dangers of using the "VCR". It will not show you how your scenario will run with any degree of reliability and is extremely likely to lead to editor crashes such as the one you described. The only way to really know how a scenario will behave is to run it yourself in real time, no matter how tedious this may seem. Above all, never touch the "VCR" without having saved your scenario at least twice immediately beforehand. Why twice? I've learned through experience that when TS crashes, the latest save (while running a scenario or while editing) will be lost. To save a scenario twice in a row in the editor, save it once, make some tiny and insignificant change (such as moving a train a miniscule distance), then save a second time.

Writing even the simplest scenarios requires a good deal of patience and a lot of caution. Good fortune!

[Chacal]

Confirmed. I lost several hours' work because of the VCR controls.

[Toripony]

I'm glad this topic came up. I've just gotten back into scenario work and have been having some weird saving problems... and I've been using that "VCR" thingy. I didn't know it was a problem but I'll be wary now.

[Bananarama]

In addition to what was mentioned above, if you're creating scenarios for the default Pacific Surfliner, the track database is out of sync, including the northern section of the trolley line (just north of the last crossovers). The errors can cause all sorts of issues, including TS crashing without warning. This was fixed in the ScaleRail version, however.

[xcrosswitch]

Using the VCR safely.
I have been making scenarios since version TS2012 and using the VCR without any problems. I have found the best way to eliminate the OP's problems is save the scenario
using the save icon in the timetable view then preview the scenario using the VCR at your preferred speed setting. Now importantly, press the VCR stop button and hit the VCR back key( |<< ). The
scenario should shut down then restart back to your origin point with your train sittting at the start point.
If you play the VCR and your train travels part way through the route, a 'Save' at that point will result in your scenario starting at that point, and not what your original start point.
I hope I have explained this clearly enough.
By the way, don't count on the station stop times with the VCR, it is very inaccurate compared to the times you will encounter in actual game play.
As an example. I am getting a 38 minute difference between VCR and actual play in Stevens Pass. If you are setting up on coming AI from the various sidings along the route, it creates locked AI junctions and
a lot of frustration.
Anyway, good luck with your scenarios

Rob K

[artimrj]

Thanks Rob, that cleared it up for me. I might even use it again now.

[Janine]

Sorry for the long wait for my cunfurmation, butt it's actually correct what has been said above. VCR works how Rob explained, and since then I have had no further issues (except the screenshot thingy when publishing which I mentioned in another thread). Thanks! :)