#[✓2.3.21] Late trains don't show warning in contract list's improvement column

27 messages · Page 1 of 1 (latest)

jolly flint
#

I was trying to track down 4 late trains per hour, and none of the trains with a red [i] in the contract list were running late. Instead, it turned out to be a set of 4 intercities that were running late enough to be penalised (I can see the grey 0 train icon when they finish), but not late enough to trigger the [i] warning in the improvement column.

By the by, all of the trains that do have the [i] in the improvement column are fine, and don't get late penalties, which is confusing. I first tried fixing these trains, but it turned out that fixes were unnecessary as they are not causing the penalties.

Game version: 2.3.17
OS: Win

Steps to reproduce:

  1. Open attached save

Wrong behavior:
Contract is penalised for being late, but it's very hard to discover which train, because it doesn't show up as late in the contract list.

Expected behavior:
Presence of the [i] in the contract list at least is guaranteed if the train is penalised for being late. Better would be that there is a 1:1 mapping, so that only trains that are penalised for being late get the [i].

Map:
https://steamcommunity.com/workshop/filedetails/?id=3372739717

Screenshots:
In the first, you see all the contracts with [i] - these are all not getting penalities. In the second you see the penalised contracts, which look like they are fine in the contract list.

Save:
https://drive.google.com/file/d/1NpkcJf9vApU6cM2tbk5C4inE7QjwYg03/view?usp=sharing

Log:
attached

2025041.JPG 2025042.JPG 📎 Player.log
Steam Workshop::Eulenburg Endless
Google Docs
3372739717_Autosave Eulenburg Endless_12-06-17_autosave.mp.lz4
tawny pivotBOT
oblique quarry
#

I was about to make a post for the same issue: the trains that actually do run late do not show in the improvement column, while some that aren't late do. And only very few that can be improved by tightening their schedule show that in that column either,

opal yacht
opal yacht
#

From your 802* trains, two are indicated as delayed and two are not for now

#

Those two that are not are just a little bit faster

obrazok.png
jolly flint
#

I think there's another edge case: even if it arrives with 3:59 at dürsel, because of the min stop time this would cascade into a delay at eulenburg hbf because the train would not leave until 4:26 or so, which doesn't leave enough time for the 3:34 trip to hbf.

#

i.e. it's not sufficient just to look at the durations of each leg; you also need to look at the departure/arrival times

opal yacht
#

May be

#

the delay propagation beyond a stop...
but there is no clear visualization for this aspect in the scheduling tool

opal yacht
#

Let's have this example

obrazok.png
#

You can see that delays of 56 resp. 34 seconds are not causing penalties per se

#

But as the train departs 26 seconds later, it arrives 60 seconds later to Altstadt, actually causing a penalty

#

So the Delay Risk is correctly indicated.

#

When I prolong the Furstnsitz stop to 2 minutes, the warning disappears

jolly flint
#

Nice 🙂

opal yacht
#

Because now the stop is long enough to accomodate the delay

#

Needed to say: The indication is present even if the delay does not cause green point loss because the Com and Urban trains are less strict

#

You are still getting the monetary penalization when the train is delayed for more than 1 minute

#

The actual list of red-flagged trains is here

obrazok.png
tawny pivotBOT
opal yacht
#

@jolly flint @oblique quarry

FIX: Red flag (possible delay warning) in Active Contracts was wrongly calculated - total time over passed stations & accumulated delay overflowing to next segment was not taken into account
BUILD: 2.3.21