Scenario timing issues

[DanSSG]

Hi,

maybe somebody can tell me why these timing issues appear in my scenario.

As you can see in the screnshot below it's 12:15:26 and I'm just ahead of my go via task which I have to reach until 12:18.

timing1.jpg

And just a few seconds later I get a timeliness penality.

timinig2.jpg

Can someone explain me why this happens and how I can prevent this? Here is the timetable.

timetable.JPG

[BoostedFridge]

Please post a screenshot of the full instruction screen for the 'go via' for '1 mile east of Laramie'

[DanSSG]

The current timetable differs a bit from the last one because in the meantime I reduced the performance on several tasks to keep the schedule.

timetable.JPG

[BoostedFridge]

Okay, that instruction looks fine. How about the instruction screen for the 'Laramie Track 4' instruction

[DanSSG]

It's just a simple stop instruction. After that the scenario ends.

Stop at track 4.JPG

[BoostedFridge]

Strange.

Make a backup of the scenario folder. Then delete the initialsave.bin , and initialsave.bin.md5 files. Clear your cache, then try running the scenario again. This definitely counts as grasping at straws.

[Chacal]

Still grasping at straws...
- This is the very last instruction and it is at the final destination. I vaguely remember (goes back a long way) having problems in such a case. Try adding some unimportant instruction between it and the final destination, such as a pop-up message.
- Try deleting the stop instruction altogether. Scenario should end without requiring a stop.
- Another hint that the last instruction is special: here's a quote from the manual. Maybe there's a hint in there.

Note: On the final instruction disc, the achievement text successful/unsuccessful behaves slightly differently. The success message is displayed if all previous instructions have been successful. The unsuccessful message is displayed if one or more of the previous instructions were unsuccessful. Thus the text in the final instruction disc should be more general as it relates to the success or failure of the scenario as a whole. Trigger instructions do not distinguish between success or failure so it is not recommended to use a trigger as the final instruction.

In your trial run, were ALL instructions successful?
- I notice a few clock icons in your task list. This means timetabled instructions. Quoting from the manual:

By default, instructions do not have to adhere to a strict timetable. If you wish the scenario to fail if the calculated timetable is not met, click on the alarm clock icon to clear the cross. The player will fail the scenario if the timetable target is not met

.

Hope this helps.

[DanSSG]

- This is the very last instruction and it is at the final destination. I vaguely remember (goes back a long way) having problems in such a case. Try adding some unimportant instruction between it and the final destination, such as a pop-up message.
- Try deleting the stop instruction altogether. Scenario should end without requiring a stop.

The scenario ends successfully but I lose points for beeing late. But I'm not to late as you can see on the screenshots.

- Another hint that the last instruction is special: here's a quote from the manual. Maybe there's a hint in there.

Note: On the final instruction disc, the achievement text successful/unsuccessful behaves slightly differently. The success message is displayed if all previous instructions have been successful. The unsuccessful message is displayed if one or more of the previous instructions were unsuccessful. Thus the text in the final instruction disc should be more general as it relates to the success or failure of the scenario as a whole. Trigger instructions do not distinguish between success or failure so it is not recommended to use a trigger as the final instruction.

In your trial run, were ALL instructions successful?

I know. The instructions are all completed successfully so I also get the successfully message at the end (when I stop at track 4). But after the sceanrio has ended, I see that I have lost points for being late.

- I notice a few clock icons in your task list. This means timetabled instructions. Quoting from the manual:

By default, instructions do not have to adhere to a strict timetable. If you wish the scenario to fail if the calculated timetable is not met, click on the alarm clock icon to clear the cross. The player will fail the scenario if the timetable target is not met

.

That applies to standard scenarios but this is a career scenario where I only lose points if I'm behind the schedule on a go-via instruction (if it's timetabled).

Strange.
Make a backup of the scenario folder. Then delete the initialsave.bin , and initialsave.bin.md5 files. Clear your cache, then try running the scenario again. This definitely counts as grasping at straws.

I have already created the scenario new from scratch with the same settings in the timetable, but also with the same result.

In the version that comes with the route I have loosened the time table even more so that I didn't lost points at the go-via 1 mile east instruction. But right now I have no idea when the route will be in the file library.

[Chacal]

Ah. I don't know much about career scorekeeping.
I can only suggest you edit a working career scenario, and see how they've done it.