F1 24 UDP Specification

Hi @Hoobiechoobie 

In looking to find a reason for a very random bug I found out the following in F1 24 (PC Steam, on Win10).

There is a very random occurrence, where sometimes when moving from one sector to next, the laptime reported is "out of sync", i.e. it is lower than the laptime in previous packet. All other data is correct, i.e. frameId increases, lapdistance + total distance increases. Below is a LapData snippet from the trace from P3 in Abu Dhabi.

Time Frame OverAllFrame PlayerID Last Cur S1 millis S2 millis dist total dist
294.07635 11381 11381 19 … 90436 56177 18294 0 … 3535.6104 8815.972
294.09872 11382 11382 19 … 90436 56210 18294 0 … 3537.0645 8817.426
294.10992 11383 11383 19 … 90436 56205 18294 37910 … 3538.5186 8818.88
294.1323 11384 11384 19 … 90436 56238 18294 37910 … 3539.9727 8820.334

Above you can see the session time and frames increasing. the prev lap time is stable, as is th eS1 time and S2 time, when the sector changed. Also the lapdist and total dist increase. Only in that one step, the laptime changes from 56210 to 56205 to increase then again.

If your devs want to look at the trace, I have one from Abu Dhabi, where this was taken.

Cheers.