Here is the current specification for the UDP telemetry output system for F1 22. 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. EDIT: Updated doc to v14 with latest infringements types Version history: v9.1 - original doc v13 - added latest team and driver IDs plus updated event packet sizes v14 - updated infringement types v16 - updated teams and drivers

@IkoRein wrote: @Hoobiechoobie As this is the first time there is F1 Beta under EA, I have the following questions in my mind: 1) If one gets approved for the Beta, will there be special forum for the beta testers, like there was earlier in the old forums? 2) If yes, will the UDP spec will be posted first there or will it also be posted here? Cheers. Hi @IkoRein (and @Kafumanto as you asked the same question) - there will be a private beta forum for beta users where we can post this spec. I am just confirming when users will be able to access this and then will post the UDP spec in that beta forum. Once the UDP spec is locked down then I will create a new F1 23 UDP thread in this open forum section for everyone to view it.

Here's a summary of the UDP output changes that we've got lined up for the next product: Added game year to packet header – apps can identify which F1 game data is coming from Temperature and speed units choice for players sent in session packet Platform of players added to lobby info and participants packets Added flag to say whether a player has their “Show online names” flag set in participants packet Added whole minute part to sector times in lap data and session history packets Damage packet now updates at 10/s Separated corner cutting warnings in the lap data packet Added new tyre sets packet to give more detail about tyre sets for each car Added time deltas for cars in the lap data packet Added overall frame identifier to packet header to help deal with flashbacks Added Safety car, and VSC counts to session data Added more physics data in the motion packet Added Overtake event Added power outputs readings for the engine We can provide more details in the UDP thread that we create for the next product / beta.

@cjorgens79The mail will be out at some point between now and before beta starts in the morning.

I'll reply to myself 🙂 I wasn't reading 21 marshal zones, but the number provided in m_numMarshalZones, so I was shifted for the rest.

Hi All - the F1 23 spec can be found here: https://answers.ea.com/t5/General-Discussion/F1-23-UDP-Specification/m-p/12632888.

F1 22 UDP Specification | EA Forums

382 Replies

Franck0675
4 years ago

@Hoobiechoobie
I have a question regarding UDP data output documentation which is essential from my point of view to know, but concrete declaration completely missing even in most recent doc :
- unit definition for all "m_localVelocity" (assuming it should also be "m/sec")
- polarity for those velocity values missing (like positive to right / front / up direction or vice versa) also those may be still possible to evaluate
- polarity for all angular velocity components which is from my point of view most important since it is hard to evaluate
Also it would be for sure helping everybody who wants to involve in some application using this telemetry to define which direction in world space / local space should be meant
(like e.g. X corresponding to lateral movement / sway, Z = longitudinal etc.).
I know this from our racing simulation who clearly define those from the start. Makes it really much easier :-)
Just to explain where such question comes from : I am currently translating telemetry provider (software plugin) for a DIY motion simulator project (existing one for previous F1 sim already existing) and it is working well yet for all standard effects (which can directly be derived from standard telemetry data values) but to add more sophisticated effects like traction loss etc. it is necessary to dig much deeper into existing tm to be able to proceed further motion calculation.
Thanks in advance for your help :-)
CanTQuiT
4 years ago
Do you mean the driver IDs?
Please correct me if I have missed out something.
DriverIDs.txt5 KB
CanTQuiT
4 years ago
@CanTQuiT wrote:
Do you mean the driver IDs?
Please correct me if I have missed out something.
+ ID 138 / Mika Hakkinen
lucviery
4 years ago
Hi
how to calculate the delta for the car in front?
I found the attribute that returns the delta for the safetycar "m_safetyCarDelta" in Lap Data Packet.
lucviery
4 years ago
Hi,
How can I filter lane cutting warnings in the m_warnings attribute? There is no warnings type attribute in the lap data package.
lucviery
4 years ago
@navarreitor

Hi,

You resolved this problem? How can I filter lane cutting warnings in the m_warnings attribute? There is no warnings type attribute in the lap data package.

How can I filter lane cutting warnings in the m_warnings attribute? There is no warnings type attribute in the lap data package.

RJ80F1

New Traveler

4 years ago

How does the frame identifier and session time work in the header packet?

If I have a load of Motion Data packets, how can they be ordered correctly? I presume I'm missing a variable, or maybe it's not actually possible and have to just take it as it arrives.

Here's a mini example (only using one drivers positions), ordered by Session Time in the header

Session Time	Frame Identifier	Position X / Y / Z
3.867813	181	232.0837 -76.7756 -68.2224
3.918861	68	258.303, -76.78932, -110.066
3.927231	182	231.1686, -76.77332, -66.63441
3.978508	69	258.3039, -76.78921, -110.0651
3.985825	183	230.2413, -76.77075, -65.00995

Here's some other data ordered by Frame Identifier

Frame Identifier	Session Time	Position X / Y / Z
54	3.149101	258.3048, -76.78924, -110.0643
55	0	258.8972, -76.78119, -110.4691
56	0	258.9001, -76.78107, -110.4662
56	3.209719	258.3057, -76.78911, -110.0633
58	0	258.8981, -76.78116, -110.4681
59	0	258.8969, -76.78119, -110.4693

As you can see the position x, y, z jump depending on what the session time is / frame identifier is.
I'd expect the Z, for example, to be linear and show the path of the car as it happens, but you can probably see it jumps seemingly between two linear lines.

Example console log
packetQueue.packetMotionData.Header.m_frameIdentifier + " - " + packetQueue.packetMotionData.Header.m_sessionTime + ", " + packetQueue.packetMotionData.m_carMotionData[5].m_worldPositionX + ", " + packetQueue.packetMotionData.m_carMotionData[5].m_worldPositionY + ", " + packetQueue.packetMotionData.m_carMotionData[5].m_worldPositionZ

RJ80F1
New Traveler
4 years ago
You have to work it out yourself as nothing in the UDP tells you the delta between cars.
I think I stored m_lapDistance (or at least rounded it off to the percentage of the lap completed) and m_sessionTime for each car, then looked at the time when the car in front passed that m_lapDistance / percentage, and did the calculations.
@lucviery wrote:
Hi
how to calculate the delta for the car in front?
I found the attribute that returns the delta for the safetycar "m_safetyCarDelta" in Lap Data Packet.
lucviery
4 years ago
@RJ80F1 wrote:
You have to work it out yourself as nothing in the UDP tells you the delta between cars.
I think I stored m_lapDistance (or at least rounded it off to the percentage of the lap completed) and m_sessionTime for each car, then looked at the time when the car in front passed that m_lapDistance / percentage, and did the calculations.
@lucviery wrote:
Hi
how to calculate the delta for the car in front?
I found the attribute that returns the delta for the safetycar "m_safetyCarDelta" in Lap Data Packet.
@rj_whitehouse

I found other possibilite: (distance (car in front) * 3.6) / "m_speed" = time difference in second

It is correct?
RJ80F1
New Traveler
4 years ago
Interesting. I'm not the best at maths, but that, on first reading sounds like it'd work for Indy Car oval where speed doesn't have much variation.
If the car behind is on a straight, at 200 mph, and they have a slow chicane in between, surely that time would be off.

But of course it probably works better if the car ahead has a spin etc.
What we are each building probably doesn't need to be exact, so whatever works for you. Each variation has negatives.

Forum Discussion

F1 22 UDP Specification

382 Replies

Featured Places

F1® Franchise Discussion

Recent Discussions

My F1 Suggestion

F1® 22 BETA program update

Bring Back F1 mobile racing

F1 22 weekly warrior

DLC APXGP