Last km

[Alkworld]

During the last week we had two races with interesting results on the last km:
1) GP Cerami (10am): Double attack with two riders at km 182 of 201 with 61-86 and 64-86, both with good form. Got some seconds first, then started losing time, last kms the gap was after the respective km about the following (as far as I remember):
197 (+1): 0:08
198 (+2): 0:06
199 (-2): 0:04
200 (0): 0:01
201 (+3): 0:01
Until the last km everything looked normal, the two riders had about 500-600 energy, many 80+ flat riders in tempo in the back. On the last km even more riders went into tempo, a fit 76-81 tried to attack, but couldn't get away because of the last km blocking, but still, the group hasn't been caught. Now the tempo not being enough to get a 64-86 doesn't make much sense already, but a 76-81 at the same time not getting away, but the group still not getting caught gets weird.
2) Brabant (9am):
192 (-2*): 72-79-78, 69.7 pave (no form according to the manager) gets away by 0:01 against 68-79-74, 79.0 pave + other riders, weird already, but maybe possible as I don't know the guys' energy
193 (4): a lot of riders in tempo, among them a 69-83 with average form and about the same energy, others I don't know: Rider in front keeps 0:01

The second race might have still been ok, but I'm mentioning it because it's a similar profile on the last km and it still might have been buggy. The first one doesn't make any sense at all, the escape should definitely have been caught. And if 1) is buggy, 2) might be the result of the same bug.

[Team ART]

May its helpfull for the analysis: Energy was about 970 or something like that.

And i don´t want to call this a bug - i would call it destiny

[Buhmann]

I can only say to this, that you have to accept such a result. It is not usefull to analysize every situation. If there were a few weak rider sin tempo in peloton such a situation is possible. Okay, it looks strange, but you have to accept this.

[Robyklebt]

Mmh..

With responses like that you have to accept it too if people will not report any bugs anymore. Even if the bugs are something like cheats.
Nobody here is claiming to annul the result. Only that you check if there could be a mistake..... Saw the first race and that result looked impossible. Not strange, impossible.

[Buhmann]

Maybe weak riders in tempo which make the peloton slower?

[flockmastoR]

if a 76-81 is unable to escape on a +3 the peloton couldn't be too slow

[Buhmann]

It is a different if an attack does not work or if the peloton is fast enough.

[flockmastoR]

hm dont really get your point: he didnt attack and didnt got away because there where simply too many riders in his wheel, he wasnt able to get away

Km: 201, Steigung: 3
Reinhold Möller (Steinz) schafft es nicht auszureissen

so you mean the group was fast enough to block a 76-81 (66sprint - clear captain in team), but not fast enough to get 1 second to a group that lost 2 seconds on +1 and +2 already? well its your game you have to know if this is possible. I just think this should be impossible

[team fl]

hm dont really get your point: he didnt attack and didnt got away because there where simply too many riders in his wheel, he wasnt able to get away

Km: 201, Steigung: 3
Reinhold Möller (Steinz) schafft es nicht auszureissen

so you mean the group was fast enough to block a 76-81 (66sprint - clear captain in team), but not fast enough to get 1 second to a group that lost 2 seconds on +1 and +2 already? well its your game you have to know if this is possible. I just think this should be impossible

Too many riders in tempo can be another reason at the last km (maybe Buhmann can write something that does not lead to wild guesses?). But of course, the result seems very unlikely. Anyway, Alkworld's riders had not the worst form and 60+-86 is are not the badest skills for a +3, even the rider's energy was not that high anymore.

As far as nobody seems to have a screenshot of that last km (who whas in tempo), it will be hard to do something else than just to speculate.

[Alkworld]

As far as nobody seems to have a screenshot of that last km (who whas in tempo), it will be hard to do something else than just to speculate.

I'd say that a fresh 76-81 rider not being able to get away is good enough to act as an argument that something is wrong here. If this is treated as a bug or as a feature doesn't matter in the end. I would still propose to have it checked. As we know that the last km is treated differently from all the others, the behaviour seems not to be consistent at the moment. At least not on weak climbs like this one. On real steep or flat kms I haven't seen any behaviour like this.

[Zentaron]

As far as nobody seems to have a screenshot of that last km (who whas in tempo), it will be hard to do something else than just to speculate.

I'd say that a fresh 76-81 rider not being able to get away is good enough to act as an argument that something is wrong here. If this is treated as a bug or as a feature doesn't matter in the end. I would still propose to have it checked. As we know that the last km is treated differently from all the others, the behaviour seems not to be consistent at the moment. At least not on weak climbs like this one. On real steep or flat kms I haven't seen any behaviour like this.

I had. Not on a last kilometre, but during the last 10 or 5 or something like that.
I remember a race where the group finished with one second in front of the peloton, cause there was a single kilometre where the game wanted to bother the sprint teams. The whole kilometres before and after the peloton got 2 seconds to the group, but right in the middle, without any reason, it was only one. The one second which was missing in the end. And it was impossible at all. The direct kilometres before and after had the same ascent/descent whatever and there were, in front and in the peloton, the same riders in tempo.

[Alkworld]

... The whole kilometres before and after the peloton got 2 seconds to the group, but right in the middle, without any reason, it was only one...

Let's speculate some more
This could be explained, if we assume that RSF internally works with 1/10s and rounding. Example with a group losing 1,8s each km:
km1: 0:20,0 -> displayed as 0:20
km2: 0:18,2 -> displayed as 0:18
km3: 0:16,4 -> displayed as 0:16
km4: 0:14,6 -> displayed as 0:15
km5: 0:12,8 -> displayed as 0:13
km6: 0:11,0 -> displayed as 0:11