Failing Standard Scenarios, Is There A Fix For This?

Has anyone experienced failing standard scenarios when picking up passengers at a station a few seconds late? Below are 3 standard work shop scenarios I appear to keep failing

Metro North Hudson Line
1. Evening Semi Express to Croton Harmon
2. Metro North 720
3. To Grand Central from Poughkeepsie

I have career scoring turned off and enjoy running career scenarios in this fashion so I don't worry about getting penalized points no matter if speeding or running behind schedule

It appears with the above 3 Hudson Line standard scenarios along with many others, if you arrive to an objective station 5 or more seconds behind schedule, the task is marked as incomplete, ultimately causing you to fail the scenario. Is there a way to get standard scenarios like these passenger runs to work properly without failing. For now, I just enjoy career scenarios with career scoring turned off due to this bug in standard scenarios

 

It's not about exact seconds. If the minute part of the ETA matches the schedule upon stopping, you are good.
For objectives like 16:59:59, you have to be on time, not a single second late.
Some scenarios have a massive leeway, might be something about departure time.

It's not a bug, technically. The task is to be (also: leave) there by then, and you weren't.
I agree that having separate ETA clock, and having varying leeway are inconvenient.

Career scenarios are actually more forgiving than standard for leisurely driving.
When a workshop scenario cannot be completed, I downvote them. Of course, I might succeed on 2nd run by using more effort.
And I only ever look at the ETA.

 

I tried the 720 scenario again, unfortunately late by a few seconds when arriving at Ardsley on Hudson, which rendered one of the tasks as a fail. I wonder if there is a way to program TS to not mark the task as a fail whilst stopping at the station. It seems in TSW in timetable mode, the task is marked as completed even though your train may arrive late.

So far with standard mode, it's a race against the clock, often having to operate at full throttle and ensuring as many cars are at the platform as possible

 

You normally only have this problem with a Career Scenario that comes with the routes

If you are having to do this in a Standard Scenario its possible its a Timetable Scenario
Unlike a Career Scenario you can edit a Timetable Scenario and relax the timings

 

Just to clarify, you can add timed objectives to any scenario type. (Except maybe QD.)
There are conventions, though, encouraging more leisurely gameplay in Standard.
Most workshop stuff is Standard as not getting XP could be confusing for Career and Timetabled used to be filtered out.
Real timetables I played were all impossible. Trier-Koblenz with a 442, or the NEC with M8.

The last line is critical, though. Good point! If you like a scenario conceptually but find it too strict, go into the editor and adjust it.
There is a miniscule risk of messing up the surrounding trains.
I find it's typical in TSC to expect 100% throttle usage.

 

If it's Timetabled, go into Scenario edit and change it.

 

Thank you for the advice everyone. I found in the route scenarioproperties.xml file, you can change the "estandardscenario" to "etimetablescenario" but it appears that did not make a difference. I modified the departure time for the first objective to allow me to leave Croton Harmon a minute ahead of schedule and I made Ossining a non timetabled stop. I made it further along the route until I failed a station stop at Hastings on Hudson due to being a few second behind schedule. Even though I did not fully complete this standard scenario run, it is interesting to learn what can be modified. I compared this run with an actual timetable of train 732 for this week and it appears the timetable in TSC is a bit more forgiving. I am sure after a few more runs, I can successfully complete this run. I find that making some stops a non-timetabled stop may help since there is no time involved but that may throw some things off with how the AI functions I assume. Anywho, I appreciate everyone's input. I was about to give up since I kept failing this scenario but realize there is alot of room to modify, tinker and create stuff with TSC

 

"modify, tinker and create stuff with TSC"
The best thing about the whole package.

 

If it's not a timetables scenario there is no reason to change it to one.
Go in to the editor for the train and change the timings you are having a problem with.
Normally the train is set at 75% but when on 100% you have to drive like an idiot