Doug Duthie
Premium
Hi,
Found a small bug on session tab. On spa and silverstone (both version 2018, 2019), result for a SP hotstint gives a total time smaller than selected duration .
small example :
"Total Time" column shows 0:13:38 for a 15 minutes hotstint with Camaro at Silverstone 2019
0:14:35 for a 15 min hotstint with BMW GT3 at Spa 2019
This doesn't happen with tracks other than spa and silverstone except one result at barcelona that gives 14:59 for 15 min session but it could be a rounded error. And looking for very old session doesn't show this error. First occurence in my database results start on july 24.
Hi,
Yes...that definitely looks to be a repeatable error. IIRC, I changed the way session durations were calculated in about 1.6.5/1.6.6.
Bit of a long boring explanation follows...
Previously they included the rather random time before you crossed the start line. Now it should get the timestamp when you cross the start line and record that as the starting timestamp. Each time it detects you crossing the line after that, it records the timestamp again. The total session should should be the last lap timestamp minus the initial timestamp.
The timestamp comes from the UDP real time update (SessionTime). This should be grabbed every refresh interval (by default every 100ms). I use this SessionTime, rather than a real timer so if the session is paused, the time should still be accurate.
There is a lap completed event, but there is a lag with this as it is an async event so the timestamp here would be inaccurate unfortunately so I can't use that.
So that's how it should work...however:-
You're right, Spa and Silverstone do appear to have issues. I haven't seen the issue on Barcelona (yet). If you look at the database, you can spot the issue as laps.real_timestamp appears to be repeated on at least one lap, or the first lap timestamp is the lap_zero_timestamp
I'll run some tests to see if I can identify the source of the issue
Last edited: