Apologies if wrong thread I usually don't post about TSC but I feel like im missing something. Im using the WHL Merge route from Workshop, no issues with the install the route is looking and running fine. All of the speed limits look correct to modern timings, Im following train 1Y42 as its real schedule, Im using a single 156 so no weight issues, its a beautiful, dry, summer morning and I'm driving borderline speeding yet I still cant keep to time. I've just 'failed' a 6 hour scenario because I was 2 minutes late into a stop 1 hout into the journey. What could I be missing?
Have a look in the Scenario - Editor and look at the timings for your train. If any timings are in Red they are not achievable
Yes that is what I'm trying to figure out. I know the timings calculating engine isnt 100% accurate but for the type of stock I'm using identical timings so I don't know where it thinks it's unreachable. I have been troubleshooting and did notice that adding set timings to match IRL was causing a lag in the trains arrival to Fort William, but leaving the timings to run early then worked out ontime further along. But there are no pathing issues all the way from Mallaig to Rannoch (over 2hr 45m into the trip)
Just because a Class 156 on the real line will run to point to point timings it does not mean you can do that in the game. The speeds and gradients in TSC won't be the same as the real line. As I said - open the scenario in the editor and check the timings for you train If any are showing red the it won't keep time - you need to adjust the timings so it works
I appreciate your help, but I know the red timings. I was wondering if anyone knew of any tricks or niche info about the route or stock, I will of course have to adjust but that's a shame as it is a little unrealistic now. A few minutes won't hurt I guess.
Just the way the game is - you could change 1Y42 to make it run earlier as you are not going to see it .
The scenario author should probably have tested them to make sure they were player achievable, then adjusted accordingly. I’ve mentioned before it’s an odd and annoying quirk of TSC if you miss one arrival/departure time on a Standard Scenario you fail the whole thing, but on a career scenario the same late running will still get you a green tick albeit lose about 3000 XP (if the author didn’t dial down the penalties).
I thought that is was just Timetabled Scenarios that caused that You have to run to a Timetable that the Author can pre set even if unattainable
It's a common misunderstanding Timetabled as noun is a scenario type where the player has the option to switch between multiple trains. It may not even require timetabled objectives. For a long while it was considered unsupported. Eventually it is available again, which is helpful as many early add-ons make use of it. (Typically, a train arrives and you take it over. Occasionally there are multiple trains, you pick any one of those.) Timetable is supported by all scenario types - including Free Roam and Standard. Career has scoring and thus acts as described, but Standard always failed the scenario entirely. For a long time it was exacerbated by issues with the dual clock system, where players thought they're on time, but they were usually late, failing scenarios for seemingly unexplainable reasons. Most old scenario packs - Oxford-Paddington, Portsmouth Direct Line - use timetabled standard scenarios and to make matters worse, often come with tight stops scheduled for the very last second of a minute, causing scenarios to fail. I also recall some scenarios are flat out impossible. So as an adjective, any scenario type can be timetabled. There is a weird thing with old TSC, I've come across scenarios with mismatching player and AI timetables. Not only does Oxford-Paddington have a scenario where an AI train casually blocks the station until after the player is supposed to arrive (and leave), but a Black Forest Journeys scenario has AI for the express version but the player is supposedly running a passenger train - and on a different track. Thus, the scenario ends in a collision. Given TSC's history, the best thing you can do as a player is learn the basics of the editor. I could fix both of these scenarios easily. You don't even need to interact with the world, just alter something tiny in a timetable - rather obvious when the intent is to delay the player.
I gave up trying to complete many many scenarios. I just keep my own track of what I have done. Sure I have played with the editor and changed times. I have also experienced this line. Lots of undulations and speed limits. If it is Standard then any lateness will mean a miss so just go faster than the speed limit for completion on Steam. If Career then just enjoy the scenario and don’t try to always get a high score ( some are impossible). If you don’t care about getting completion then ignore any penalties and just enjoy driving.
I beg to differ. Timetabled mode never went away. It works the same way as Standard mode apart from the extra feature of being able to switch between drivable trains. Provided the scenario starts in the cab of a locomotive, the scenario will be listed as "Standard". As I understood it he reason it became classed as "unsupported" was because if you don't start in the cab of a locomotive, the scenario was no longer listed there after a change in the way the menu system displayed. The term "unsupported" is often misused or misinterpreted and personally I feel it would be better never used. But generally it means a feature continues to work but the developer will not offer any support on the matter. Best regards, John
