Then, I tried running the shortest of the four included scenarios: "Working in Altoona Yard" according to the manual (which I had downloaded manually from Steam), but simply "Altoona Yard" in TS2014. All went well until I was just a few feet from the final stop point and -- blam! -- an AI train wreck brought the scenario to a crashing halt.
Curious, I tried opening the scenario for editing, only to run into one of RSC's absurdly locked routes [
]. Determined now, I went through the unlocking process and, finally, dragged the scenario into the editor. Once there, I opened the "VCR" for one of its very few useful functions: following an AI train's progress. The culprit, No. 1525, ran directly into the hinder of a rack of freight cars parked on a siding. The fix, of course, was simple: move those cars to an adjacent siding.The point is that we users should not have to clean up RSC's messes. It's one thing when someone uploads a faulty scenario to Steam Workshop, but quite another when a scenario included in a DLC package, therefore, a paid for scenario, hasn't been tested properly.
At my standard scenario repair rate of $200 per hour (hey! why shouldn't I make as much as a plumber?), RSC owes me $172.33. A check will do just fine, folks, but credit toward future (faulty) DLC is not acceptable.
