F1 22 UDP Specification

UDP actions can be mapped as buttons in game. When a user pushes that button the UDP action will activate. This can be useful if you're building a custom application. Let's say you want a driver to mark specific on track events to look at later. You can use a UDP action here. Then when looking at the telemetry data you'll know when they pressed that button and know to look for something interesting in the rest of the data.

 @BrokenHypocrite Thank you very much for your answer, although I still do not understand it very well the utility. Perhaps it is good for some commercial wheels that have their own developments where they can incorporate interesting functionalities. In my case, as a Simhub user, it doesn't bother me that the game informs me by activating one of those UDP Actions than by achieving the same by detection by Simhub itself of pressing the key, button, or axis that I assign inside of the game...or not.

I would prefer more shortcuts to actions available within the game. I mean, for example, shortcuts to the information offered from the pit wall: weather report, race report, info on the car behind or in front, repair front wings in the pits, pitting this lap, hard tire selection, medium,...

Especially if playing on a console this would be very useful as I understand that with macros this could be achieved on PC.

Therefore, I still do not understand why so many UDP Actions, unless it is a requirement or contribution to the manufacturers of steering wheels with their own information displays

I have a cupple of suggestions for the development team.

1. Would it be possible to obtain the available tyres? We have data about used tyres, but no data about which tyres are available.

2. and the selected front wing adjusmention selected in the next pit stop?

Theese would help to select them via mfd from the wheel custom buttons.

Completely agree with point 1. Do we know if each track always uses the same "actual" compounds every time?

It's difficult to build a tyre strategy until the first car goes out on track and you can compare the actual and visual compound being used.

@RJ80F1
No, compounds change for each race, e.g. Bahrain uses C3/C2/C1 while Australia has C5/C3/C2.

You can see the compound in Tyre Allocation.

It could be a bit better if we had more immersion, like this: https://answers.ea.com/t5/General-Discussion/Expected-features-for-F1-23/m-p/12342686?attachment-id=673765#M19354

You would be able to extrapolate tyre life based on compounds and abrasion and stress. Or at least collect data for later estimations 😉

(if you so hardcore, of course, but I guess when you collect telemetry ... 😉 )

@chuschus
I think it depends on what Tyre Allocation option you choose before the race weekend.
There are three options: Softer/Balanced/Harder and that defines how many of each you have available.
Also, if you consume all Softs during quali sessions, you end up with one new Soft set for race.

@P4st3l1ak I actually meant does each specific track always use the same compounds. E.g. Does Bahrain always use C3/C2/C1 and Australia always uses C5/C3/C2?

I think your comment actually answers that question, but wanted to confirm. At least it'd be a way round (albeit hardcoded to an extent) to build a tyre strategy before the race starts from past data if that's the case.

@RJ80F1
I don't think there is a compound variation for same race between seasons in game.
AFAIK CM sticks to what Pirelli recommends for real-life races.

@P4st3l1ak
No, it's not stored. That's the cause it would be great to have it in car status packet o at least in car setup. The fp1 could be done one day and the race another one.
The wheel can be used by multiple users, so it doesn't store that data.

@chuschus
I understand your case and it's what I assumed as well.
But you don't want to inflate packets to unreasonable size so CM may choose what info is stored in them.