Weird timing problem

[HornetMaX]

@Piboso:
one strange problem I've noticed on track Monzabike v1.1: the last split seems to be taken way before its correct position.

From the tracks .rdf file I have:

Code Select Expand

finish_line
{
long = 404.894012

split1
{
long = 2150.573975

split2
{
long = 3905.693848

split3
{
long = 5660.813477

Track is 6995.13m, the fPos*tracklength of the last split should be at 5660.81 - 404.89 = 5255.92m (the two other respectively at 1745.68m and 3500.80m).

Now I have coded in my plugin something that when a split or lap event is received shows a string with some info, including the last known _fPos * tracklength (last known _fPos being updated at every RunTelemetry event).

I did a lap (from the pits) in 2:08.607 (lap 7 in the screenshot below) and I've recorded it live (while riding).



http://youtube.com/v/5-Ui5FSB8VQ

So what I see is:

• The timings reported by GPB (sector times) corresponds to the rough measurement I can do on the video, no issue there.
• Split 1 and 2 happens at (respectively) 1741.92m and 3498.03m, to be compared to their theoretical position from the .rdf of 1745.68m and 3500.80m: pretty close, no problem. On the video they are at 0m 44s and 1.20s (lap strarted roughly at 0m10s).
• Split 3 happens at 4828.84m (1m44s on the video, look at the line on top of screen change from "event 3" to "event 4"): this is way before the theoretical position of 5255.92m
• You can see the difference between the two positions on the track map: split 3 is the last of the 3 green dots but th eplugin receives a RunSplit signal at 1m44s, when the bike (red dot) is still very far from split 3.
• The position of the green dots on the map seems correct (it matches what I see in TrackEd for that track).

I was testing (offline) but I've seen it happen identically online.

MaX.

[HornetMaX]

Bump.

Any chance for a look at the above ? It may be nothing or a track issue, but there's a little chance it may be something more interesting to dig into ...

MaX.

[HornetMaX]

Bump. Still happening in beta6c on Monza v3.0 (NDS or not).

MaX.