F1 23 UDP Specification

Hi folks,

I am building a telemetry app for F1 23. Let's say that my app misses the event message for Retirement (i.e.) a driver DNF'ing. This could happen if the app was not running at the time of the event announcement. Is there any way I can look at any other packet and determine that this driver has DNF'd. I see that in PacketParticipantsData, there is an m_numActiveCars. This will be 19 if one person DNF's. However, lets say there are only 19 people in the lobby. I cant distinguish between the case where 20 started and one crashed out vs 19 started and are still driving.

Is there any way this can be solved using the existing telemetry packets?

@ThibaudPHP Yep you're exactly right. I checked after I posted it and noticed it was when I pitted, but didn't get round to pointing out my stupidity. :-)
Bit annoying that all the assists get turned on, but can just ignore any settings when the car is in the pits or in AI.


Thanks for the reply!

@Hoobiechoobie in '23 the UDP team was able to add a single Ride Height variable, which does look to be the Ride Height at the center of gravity. I originally asked for Ride Height of the Plank of the car, both Front and Rear values, but they said at the time that the single Ride Height value was the best they could do. Would it be possible to get Ride Height for the Front and Rear of the Plank in '24?

Otherwise, I am very happy with the current structure of the UDP data. The only other thing I would ask for is a unique identifier for drivers/user accounts. I totally understand that we can not have the player/EA name if the user does not turn on Show Player Names. What should be possible though is assigning a unique string or number to each account and sharing that in the UDP data. I imagine EA, PlayStation, Origin, and XBOX might all have a different format for this unique identifier, which would be fine if it always remained the same. This would be helpful for many of the League related features in our App, and I can imagine many other developers would also welcome this, and it would not compromise user's privacy.

Lastly, I'm curious if there's the possibility of us receiving Beta access again this year. It was extremely helpful for us App developers and we hope it was also helpful to the UDP team and the other development teams. As always, I appreciate what you do for us!

@Hoobiechoobie, sorry one more thing, can we get a unique way to identify Sprint Races? Currently session type only has the following:
0 = unknown, 1 = P1, 2 = P2, 3 = P3, 4 = Short P, 5 = Q1
6 = Q2, 7 = Q3, 8 = Short Q, 9 = OSQ, 10 = R, 11 = R2
12 = R3, 13 = Time Trial

Where a sprint race has the same Session Type as a standard Race, I believe it uses 10 for the sprint then 11 for the Race (R2)... but this is confusing, since 10 can now either be a Sprint or a Race, depending on if you include a sprint or not. Having the Sprint Races have their own session type value would be very beneficial.

@BrokenHypocrite I mentioned the same thing earlier. You can look at the weather / tyres to see if session 11 is mentioned thus knowing it's a sprint weekend, but it would be cleaner to be able to have it as a session type by itself.