[DISCUSSION] F1® 25 UDP SPECIFICATION

Thanks for providing us the document again! And thanks for all the hard work you are putting in the UDP data!

Can you confirm, that the bug we had in F1'24, when you used the formation lap, the data at racestart was corrupted, that this is fixed?

Would be nice btw to have mini sectors per sector in de current lap of each driver, as well as in the history lap. F1 timing also has 6 mini sectors per sector. Would be a great addition! 

Hi EA_Groguet​ , thank you for sharing it.
I see C0 compound is still there (m_actualTyreCompound), I guess it has been replaced by C6, waiting for the new ingame code to prepare my dashboards... 😃

Raymond-Smits wrote:

Can you confirm, that the bug we had in F1'24, when you used the formation lap, the data at racestart was corrupted, that this is fixed?

Hey there,

Yeah, the formation lap data corruption should be fixed.

However, there are no plans to add the mini sectors at the present time. If this changes in the future, I will let you know.

-Groguet

Nuvolarix wrote:

Hi EA_Groguet​ , thank you for sharing it.
I see C0 compound is still there (m_actualTyreCompound), I guess it has been replaced by C6, waiting for the new ingame code to prepare my dashboards... 😃

Hey there,

We will update the documentation in due course. The C6 tyre has Id 22.

-Groguet

Thanksss :)

We will update the documentation in due course. The C6 tyre has Id 22.

Ops, this added ID was unexpected. I see that now the "reverse tracks" have new IDs, thanks.
Since we have to plan the updates of our apps with the new provided information, when the new version of the documentation will be released with the official content?

Just some feedback for next year. In the past we also had an official thread (even during beta) that allowed us to be more up to date with your changes. This year, however, there has been almost no "open" communication, and this is causing some issues (for example, all this new information will not be available on day-one in our app). I hope that next year we will return to the previous communication model.

Kafumanto wrote:

when the new version of the documentation will be released with the official content?

Documentation has been updated now 😁

-Groguet

As last year, I put here the delta between 24 & 25, for information, please feel free to comment things I missed/misunderstood :)

• A new packet id:

ePacketIdLapPositions = 15, // Lap positions on each lap so a chart can be constructed

• A new packet type (with the packet it above, obviously)

The lap positions data indicates which position each car was on at the start of each lap. Using this
information a lap positions chart can be constructed. Note that only a maximum of 50 laps will be
transmitted in a packet. If more than 50 laps have occurred then two packets will be transmitted, with
different m_lapStart parameters. The whole lap position history can be recreated merging both of
these.
Frequency: 1 per second
Size: 1131 bytes
Version: 1

struct PacketLapPositionsData { PacketHeader m_header; // Header // Packet specific data uint8 m_numLaps; // Number of laps in the data uint8 m_lapStart; // Index of the lap where the data starts, 0 indexed // Array holding the position of the car in a given lap, 0 if no record uint8 m_positionForVehicleIdx[50][cs_maxNumCarsInUDPData]; };

• On Retirement event, reason added :

uint8 reason; // Result reason - 0 = invalid, 1 = retired, 2 = finished, 3 = terminal damage // 4 = inactive, 5 = not enough laps completed, 6 = black flagged, 7 = red flagged // 8 = mechanical failure, 9 = session skipped, 10 = session simulated

• New event "DRSDisabled", containing the reason :

NEuint8 reason; // 0 = Wet track, 1 = Safety car deployed, 2 = Red flag, 3 = Min lap not reached

• In event "StopGoPenaltyServer", added the stop time :

float stopTime; // Time spent serving stop go in seconds

• Participant's name max length goes from 48 to 32 (size goes from 1350 to 1284 bytes)
• Participant data now includes information about the livrery :

// RGB value of a colour struct LiveryColour { uint8 red; uint8 green; uint8 blue; }; (...) uint8 m_numColours; // Number of colours valid for this carLiveryColour m_liveryColours[4]; // Colours for the car (...)

• In CarStatusData, C6 tyre are now available in actualTyreCompound as value 22
• FinalClassificationData now includes resultReason field (growing the bytes size of the packet from 1020 to 1042 bytes)

uint8 m_resultReason; // Result reason - 0 = invalid, 1 = retired, 2 = finished, 3 = terminal damage // 4 = inactive, 5 = not enough laps completed, 6 = black flagged, 7 = red flagged // 8 = mechanical failure, 9 = session skipped, 10 = session simulated

• In LobbyInfoData, name goes from 48 to 32 chars length, dropping packet size from 1306 bytes to 954 bytes
• In CarDamage Packet, added tyreBlisters field (packet size goes from 953 to 1041 bytes)

uint8 m_tyreBlisters[4]; // Tyre blisters value (percentage)

• In PacketMotionExData, added 3 new fields (size goes from 237 to 273 bytes)

float m_chassisPitch; // Pitch angle of the chassis relative to the direction of motion - radians
float m_wheelCamber[4]; // Camber of each wheel in radians
float m_wheelCamberGain[4]; // Camber gain for each wheel in radians, difference between active camber and dynamic camber

Guys, can someone explain to me how to insert telemetry on f1 25 with SF1000 steering wheel on xbox?

If you don't use the Telemetry for anything else, just send from F1 25 the Telemetry in F1 23 format to the SF1000's IP address.

If you use some telemetry application too, then the app should send the data either in F1 23 or in F12021 format. My Tool can do this (see https://www.telemetrytool.com). Support for F1 25 is there, I just need to do new trackmaps + do general testing. I expect to have a version out tomorrow, but latest on Friday evening (European time).

Cheers