[DISCUSSION] F1® 25 UDP SPECIFICATION

Would like to know this too. EA_Groguet​ can you update us on this?

Hi folks, in the participants packet, m_numActiveCars description is 

Number of active cars in the data – should match number of cars on HUD

When I was testing out in my team mode, I observed that this is matching the number of cars that have not DNF'd. 2 cars DNF'd in my race and m_numActiveCars was reported as 20 (when 22 was expected, since even DNF'd cars are present on the HUD).

Am I misunderstanding this, or is this a bug and is 22 the correct and expected value in the above situation?

I wouldn't say it's an issue. There's a difference with these penalties, the first group of 2 and 3 second penalties can't be served in a pitstop, while the 5 and 10 second penalties can. It makes more sense to keep these 'serveable' penalties as events.

Hello,

The m_penalties data in the Lap Data packet still only accounts for 2 and 3 seconds penalties. 5 and 10 seconds penalties are not added to the total in the data, so if a driver has a 3sec and a 10sec penalty in a race, the m_penalties will be 3 instead of 13.

It looks to me like there are no other packets that contains the 10sec penalty data, other than having to parse a penalty event and adding it manually (/by code) to the focused driver. Could you confirms it's a known issue or if I'm missing something here EA_Groguet​ ?

Thanks in advance !

The m_frontAeroHeight and m_rearAeroHeight is in mm, and represents the height of the plank from the ground. I verified this in MoTeC I2 Pro with data I collected from F1 24 when these values were added last year. Hope that helps!

For front and rear ride height - what is the scale for these two? Thanks

Hi TMillo​, from what I understand from the UDP spec doc, the game packs everything including the tyre temp fields into C style arrays, and their array indices have been documented clearly in page 19

All wheel arrays are in the following order:
0 – Rear Left (RL)
1 – Rear Right (RR)
2 – Front Left (FL)
3 – Front Right (FR)

If you have written the parsers by hand, then please share the parser code for CarTelemetryData struct.

I'm unable to figure out which framework/language this code snippet uses and how exactly the object is parsed from raw bytes

GameRawData.PlayerCarTelemetryData.m_tyresInnerTemperature02

If you are using some library or building for some existing platform, you might get better mileage by posting in their forums

Hi ragekumar666

GameRawData.PlayerCarTelemetryData.m_tyresInnerTemperature02 is the code snippet. I'm trying to work out which tyre the 01/02/03/04 ending relates to.

Hi EA_Groguet​ , 

I would first thank you for sharing us the document and the ability to let users have the udp specifications, also caring about us. That kind of availability is very rare and i recognize that could be very demanding. 

I was wondering if there could be a value in the F125 UDP specifications which shows the Delta time that appears on the steering wheel or either on the time trial mode up in the right box. That would be VERY useful. If there is none, is there a possibility to get it anytime soon?

Thanks,

Mattia

TMillo​ 

Hi there, according to the spec, tyresInnerTemperature in the car telemetry packet is an array of 4 uint8's. If you parse the incoming packet as an array of 4 uint8's, the documented numbers are the indices in the array representing those tyres. So I'm not sure what you mean by 01/02/03/04 packets (assuming they are not packet ID's, since those do not correspond to the car telemetry packet).

Please share a code snippet/screenshot so I can understand better. Also, is this something you're trying to build for simhub? If so, you might want to ask around on simhub forums/discord.