Codemasters TeamHere is the current specification for the UDP telemetry output system for F1 24.
To report any bugs with the UDP system, please add a new topic into the bug reporting section of this forum and our support team will ensure that this finds its way to the dev team.
If you have any questions about the UDP specification then feel free to post in this thread and a helpful member of the community will respond when possible.
Thanks, haven't really checked 'result status'. I'll take a look.
Andy
I might be being blind and just not seeing it, is there any way in the telemetry to know which of the drivers correspond to the player on the local machine in a network game?
I've checked 'm_spectatorCarIndex' in the PacketSessionData but this always seems to be zero (and participant zero isn't the current player).
Thanks
Andy
Doh, thanks @Marchesee , didn't think to look at the header!
Andy
These new forums really aren't designed for this thread. Just had to scroll down for 20 minutes, clicking Show More to get to the bottom. Bring back the page numbers!
Any chance in 25 the Time Trial packets can be relooked at. It's really confusing how it works with the participant list. Multiple Personal Bests, the rival data filling up the rest of the packets and not really being able to get your rivals sector 3 time as it resets as soon as they finish their lap etc.
The Time Trial and personal best keys are a useful addition, but the participant list is a mess.
Probably makes sense to always have the current user to be 0, the personal best to be 1, then the rest filled up as a new rival is used.
e.g. Rival in index 2, next rival in index 3 etc and adding drivers like that. Admittedly it's still slightly confusing as a rival can do 10 laps identical, so the current lap should always be 1 and the history lines up with that.
