Forum Discussion

EA_Groguet's avatar
EA_Groguet
Icon for Community Manager rankCommunity Manager
7 months ago

[DISCUSSION] F1® 25 UDP SPECIFICATION

Hey drivers! We have posted the current specification for the UDP telemetry output system for F1® 25 here. Use this thread if you have any questions about the UDP specification. -Groguet
mantazzoLTU's avatar
mantazzoLTU
Rising Scout
7 days ago

As I'm working on an overlay package, and working with a NPM package that supports reading F1 25 UDP data, I'm fairly certain some improvements could be made, hopefully with F1 26 DLC as well.

  • Session Packet (ID 1) could also have a some sort of array for DRS zones data - detection point location, DRS zone start, DRS zone end (should be distance in meters, same as m_lapDistance in Lap Data packet (ID 2) - I think it could still be implemented for 2025 cars since you guys already have m_packetVersion in the Header for packets, so you could just increment that field and add the data for this packet; something similar could be implemented for the areas where we can use the active aero (or however it works...), if it's implemented properly with the 2026 DLC of course. We do have locations where Sector 2 and Sector 3 begins, so having DRS zones data would be nice as well.
  • Would be nice to have some sort of "m_maxSafetyCarPeriods" and "m_maxVirtualSafetyCarPeriods" variables (and maybe m_maxRedFlagPeriods too) in Session Packet as well, since the number differs between race lengths and we don't have a clear number anymore (we used to have a rough number posted in the old forums, back years ago). Or at least it would be nice to also have a "remaining" number of Periods alongside the number of Periods that we already had.
  • Having "m_bestLapTimeInMS" in Lap Data packet (ID 2) as a uint32 would be nice - faster updates, and we can immediately get the data for all cars, instead of waiting for Session history packet to come through for all cars.
    • Though, honestly, we might likely need a "Lap Data Extended" packet in the future, similarly executed to MotionEx...
  • Event packet (ID 3) improvements:
    • FastestLap struct - change the time from float to uint32 and give the result in MS instead (consistency with Lap Data packet is better, IMO)
    • StopGoPenaltyServed struct - change stopTime from float to uint16 and give the result in MS instead? (better precision)
  • Participants packet (ID 4) improvement:
  • Add a "m_numTotalCars" field, so that way we could track how many cars have data in total (even inactive ones), and how many cars are still active (while others have retired for reasons)

And there is still a bug in my data in Session History (ID 11) packet that if you start a Time Trial session with a Personal Best Time already set, the History for your car has wrong detail - the fastest lap number for fastest lap and each fastest sector becomes "199", which is impossible. 

I hope that at least some of this can be implemented. :) 

Recent Discussions