This has bugged me right from the start. It was one the very first scenarios I played after buying TS2016. And it was impossible to make it on time. Why? Because the scenario expects the Turbine to be running from the start, which it does not. So you lose a lot of time waiting for it to start up or crawling with Diesel power only... If you know how to use a hex editor, here's the trick to get the official highscore. And it's not a cheat, it's just playing it as it was intended. And it will still be a challenge. 1. Open the archive Railworks\Assets\DTG\UPTurbinePack01\UPTurbinePack01Assets.ap (7zip recommended) 2. Inside, navigate to RailVehicles\Turbine\UPTurbine\Default\Engine folder. 3. From here, copy the file Turbine_A_Unit_Script.out to your desktop and remove write protection. 4. Open it with your hex editor and change the byte at offset 0xB43E from 0x73 to 0x71 (ASCII: "s" to "q"). Save. 5. Now as it's never good to overwrite original content, and with introduction of the .ap files it is not even necessary anymore, we'll put the patched file in its own place next to the .ap file. Open the folder Railworks\Assets\DTG\UPTurbinePack01. 6. Create a folder named RailVehicles in there. Open that folder, inside create another one called Turbine, inside another one named UPTurbine, inside another one named Default, and inside finally a folder named Engine 7. Finally copy Turbine_A_Unit_Script.out from your desktop into that Engine folder. Upon starting the scenario, the turbine will be at full RPM. Flip the sander switch and off you go! Note that this fix is made just for this scenario. Background is, the state of the turbine is defined in RailVehicle's number field. The first letter sets the state of the turbine. If it is "s" then the turbine will be on. Any other character will have the turbine off at start. In our scenario the RVNumber is "qxh18b18". So all we did is patch the engine script to have the turbine running when encountering "q". That means for scenarios which have the turbine running at start, it will be off there. To disable, simply rename it to Turbine_A_Unit_Script.out.scenario15 for example I'm off for a nostalgic run to Cheyenne now folks. It is still a challenge and never go faster than 50 mph even if the track limit is higher...
Finally after 6 years... an absolute joy to drive this flawless, vibrating beast of a loco with a perfect braking script!
