So this is a bit of a technical report on the Donner Pass route. I just recently decided to tackle the four heavy-duty long scenarios that come with the pack. The result is a very interesting report on technical issues with the scenarios themselves. Sure, I had a faulty signal here and there in the first scenario, but my report covers a major aspect of the scenarios: the Career versions were written with the wrong track timings in mind. Seriously, stay with me on this. 1) Donner Pass The first scenario can be summed up in two screenshots. I ran the standard version of the scenario because I can't see why anyone would subject themselves to a 215 minute Career scenario willingly. Here is a summary of the two images you are about to see: it is expected you will complete a run that requires over 3 hours in 167 minutes to score any points. First image is end of the Standard run, second is the start of the Career one. I think you can see the problem here. 2a) Getting Involved Sadly, my recording of this did not take, so I'm going to have to rerun this and thus have no pictures. However, this scenario has the same problem. The timings on this scenario are equally impossible. Even the initial 3 minute timing at the very start is impossible. I sped into that siding over 20 MPH (unrealistic) and came to a stop at the train, quickly changed cabs, let sand fly, and would up nearly a minute late. After that, the next timing (going the speed limit, FYI) dropped me into the negatives. I quit the scenario at this point. I think I have the Career video to provide this for DTG's purposes. I ran and completed the standard version way later than the expected finish time. Note I did not run the "bad weather" versions of this or the third scenario, so "Powering Up" was not attempted. EDIT: Due to footage not being recorded for some reason, I decided to record "Powering Up" as my eventual video footage after all. If replaying it, might as well get another checkmark! 3a) Together As One Looked at the Career timings. Immediately realized they were flawed. Went to Standard Mode to find that the timetable WAS BEING APPLIED FOR SUCCESS OR FAILURE. Seriously? I succeeded by speeding at 30 MPH most of the way. The scenario cannot be completed legit. This scenario needs wholesale replacement. Got the video where I repeatedly say I don't care as I go. The hilarious bit is, after rescuing the train, it detached halfway along (likely would have had the dreaded "you got railroaded" bug I've seen twice if I went to pick it back up) and stayed on the mountain anyway. Was still good enough for the driver to say he owes me a beer. As with the above case, "A Joint Effort" was not attempted. 4) Cold Play So I went into this scenario with a sense of dread as I noticed the timetable was showing again in Standard Mode. However, I noticed a quirk this time. The track from Truckee to Colfax was shown as 30 MPH. On the first three scenarios, I was traveling on a track designed to run at 25 MPH. It was a classic "there's your problem" scenario. The timings in the first three scenarios are impossible because they were timed for 30 MPH track, and the timings in the last scenario were apparently applied for a 25 MPH track. Don't believe me? Look at this: First image: goat is to arrive at 11:54 a.m. Actual arrival time, even accounting for missing setting the switch and having to seek permission to reverse back onto the track: 11:22 a.m. Analysis This is a technical problem with the scenarios. As I said, I found a couple of buggy signals, and I'm sure they can't be fixed without possibly wrecking something, but come on DTG. These scenarios need to be replaced. I can give you timings for the first one from my Standard run to aid with this, and I'll have to retape the second; the third, meanwhile, will require me to rerun it at 25 MPH to get proper timings. I can also give when I arrived at each point on the last scenario. My suspicion is both tracks are supposed to be 30 MPH. Alternatively, Colfax-Truckee might be 30 MPH and Truckee-Colfax might be 25 MPH. Meaning that the scenarios took the wrong direction into account IN EVERY CASE. I would argue that you can change the speed limit to 30 MPH on the route, but again, this could wreck something and this would need testing. I maintain that scenario modifications SHOULD NOT NEED TWO WEEKS TO TEST and should be easy to replace. SO REPLACE THEM. These scenarios keep this DLC from being a 10/10 in my books. Such an easy fix. I'm even prepared to modify my review. Recommendation My easy fix for the first three scenarios is to make the Colfax-Truckee track a 30 MPH track to match that of the final scenario. Sadly, I don't think this will get done as it would need testing, and this route would still take two hours to drive for each test. So I'm not holding out hope for those. That is still, however, one fix. The other is to rewrite the timings for every single scenario, or convert them to "start with 1,000 and be penalized" format. This would also fix the final scenario being done 35 minutes early. Conclusion Unfortunately, I can't see DTG giving a rip about this technical report because I already reported Sherman Hill scenario issues - even replacing all of the cars in Introduction to Sherman Hill with a successful run - and it hasn't been fixed for a year since. So I don't predict this will get fixed, either. That's sad, because these are very clearly scenario issues. They should be run as the standard 'start with 1,000 points and lose points for speeding, etc." format. These can easily replace what's in the pack. Because DTG thinks that changing out a scenario will break something in the Workshop (HOW?), it'll never be fixed. Can't wait until I get a maximum score of 600 on PDL for one scenario.