simmo413 wrote:Hi
I'm the original builder of the Eagle Ridge Railroad route (which Pike's version is based on - he made one small modification to the track plan).
Marc
Clears up that question, thanks, I was beginning to think this was like the chicken vs. egg as to who was first
I've been thoroughly enjoying your route though I had to get Pike's for the scenarios...this is some really lovely designing, you did fine work on it. Congratulations, Marc!
Speaking of scenarios-
Totally not your fault or concern, so this is more of a general audience question:
I'm annoyed to distraction by the AI doing silly things to end or block a scenario's progress!
I've encountered this several times...like RudolfJan's neat scenario for the Challenger, in which a rogue AI train runs a closed turnout 5 minutes in and ends it, Michael Stephan's 'Lumber Emergency' (Castle Rock Scenario 1) where a suicidal AI train smacks another AI train just preparing to depart also just a few minutes in, and lots of scenarios included in Pike's route.
In Pike's, A1-A3 are a set of coal drag scenarios, but I can't run 1 or 3; in the first, an AI train apparently crashes elsewhere just as I'm getting into that Lytton yard (across from the infamous trestle y'all have been discussing), and in 3 an AI train that's supposed to stop and move on just stays there, blocking my exit from the reverse loop my tasks are taking place on. Even in A2, I could complete it, but only because the AI didn't crash or block my path when it flaked out.
A4-A9 are scenarios dealing with a local freight and I'm in the midst of A7 now. All's been okay except for a tense moment in A6 (IIRC) where I had to quickly move my loco out of the way of an oncoming passenger train and switch a turnout so it wouldn't derail! That leaves A8 to hopefully run, though A9 is a lost cause so far...I went through every scenario individually fixing broken consists before I could even run them (something like 70 that had to be fixed!) but A9 didn't even give me a clue what was wrong, it hard crashed on loading, and the same when I tried to edit it.
A note to Rudolf about his scenario answered the reason all this is happening. Evidently the AI protocol changed somewhat when Railworks became Railworks2, so older scenarios are sometimes iffy.
My question is, is there some way to remedy these AI shenanigans without having to be a maestro with the editor or RW Tools? I'm still quite the noob at this stuff and though I'd eventually like to write routes and scenarios (or fix busted ones like these) I can tell I'm a long way off from gaining enough skill to be able to do so.
I'm also a bit concerned whether regular RW updates will bollix up more scenarios...an awful lot of work goes into them and I hope they aren't ruined!