F1 22 UDP Specification

So er... Will this be updated tomorrow morning (BST) on release time?

I've not checked it fully yet, but one issue I saw briefly was the packet version in the header came through as '2020' initially, even though the game UDP format was set to 2022. I went into the game settings, selected a different year for the packet, then re-selected 2022 and it worked fine. May have been an anomaly on my console (PS5) but just something to be aware of.

---

@ericmaia90 wrote:
@TheMillsyHappened to me too. It is a bug. It shows 2020 on the header unless you change and select it back to 2022.

---

Thanks for confirming. What platform were you on out of interest?

@ericmaia90 Thanks, might just be a PlayStation issue then but too early to be sure.

---

@TheMillsy wrote:

@ericmaia90 Thanks, might just be a PlayStation issue then but too early to be sure.

---

For what it's worth, we've seen problems with PS4/Xbox a lot on hotlaps.io over time, might just be due to the nature of UDP, local network gear or the console or a combination of all of it, but we often have users where the telemetry data from a console arrives essentially as garbage in our client app. Whenever we tried to debug it, it worked fine for us (did someone say "works on my machineTM"?).

Of course this is just anecdotal evidence and might well be something on our side, but we've been observing and tracking this for a long time already, in particular for PS4/5 users.

@TheMillsy - Good spot! It looks like this is indeed a bug that affects the console versions. We've lined up a fix for a future update, but the workaround you suggested where you set this to something else and then back to 2022 should work in the meantime.

Edit: sorry, still getting used to this new forum and thought I was quoting your original message in my reply. I was responding to your earlier post where you indicated that the data format was coming out as 2020 when viewing the UDP output on a PlayStation.

Hello @Hoobiechoobie , is it possible to know if the bug of the PS UDP default version is fixed with the last patch?

thanks

Is there a specific list of time penalties that can be given by the game? I think I've seen 2, 3, 5 and 10 seconds but is this a finite list or could the time penalty be any amount (i.e. I could get a 7s penalty)?

hi guys, 

I understand this is not really the correct forum but I have to ask a Python Question as I am kind of stuck. 

I started to toy around with python and the f1 2022 telemetrie data but I got stuck with reading the header. 

I tried this:

What dont I get? - nearly any comments are appreciated!! 

Hey, @Hoobiechoobie, i have one bug for you, can you check this please? Grid position is sent with values 0-19.... not 1-20. For example: the driver has a pole position have gridPosition value "0".  Anyone has this bug?

Is it possible to grab the UDP Data with an Arduino connected to a ESP8266 WiFi module? Can not use Simhub because of PlayStation. if there's already something simple I can build on that would be great. Appreciate any Tipp. 

@Hoobiechoobie  Since the update my dash is not working under the 'Warnings' section

I had it created so it showed me the track limit warnings so I know how close I am coming to a penalty, now it is showing ALL warnings such as collision warnings (which for the dash are necessary as you can get them frequently at a start online)

Has something changed or is it possible for you guys to change the UDP code so track limit warnings are a separate piece of data such as .limitwarnings

It was working great only showing the track limit warnings before 

---

@FG44141 wrote:

@Hoobiechoobie  Since the update my dash is not working under the 'Warnings' section

I had it created so it showed me the track limit warnings so I know how close I am coming to a penalty, now it is showing ALL warnings such as collision warnings (which for the dash are necessary as you can get them frequently at a start online)

Has something changed or is it possible for you guys to change the UDP code so track limit warnings are a separate piece of data such as .limitwarnings

It was working great only showing the track limit warnings before 

---

This was actually a bug where the other warnings weren't coming through properly. Now that this is fixed you should be able to filter these results by penalty and infringement type if you only want to consider specific types of penalty or warning.

@Hoobiechoobie Thanks for the reply.

Any idea on how I can get this working again to only show track limit warnings. I've tried to get infringement type etc working but I just cut seem to do it. Im using SimHub. 

I cannot figure out how to make a line of code to use for F1 22 to only flag track limit warnings, even using the F1 22 UDP guide i'm still unsure  

---

@tmillo wrote:
@Hoobiechoobie Hi Hoobie, since the patch my "fastest lap" part isn't updating. Any idea why this is the case?

---

The fastest lap event hasn't changed in the UDP output. However, we did correct the packet size for the event packets as this was incorrect in the original doc, so worth checking that you are reading the packet sizes in correctly.

---

@FG44141 wrote:

@Hoobiechoobie Thanks for the reply.

Any idea on how I can get this working again to only show track limit warnings. I've tried to get infringement type etc working but I just cut seem to do it. Im using SimHub. 

I cannot figure out how to make a line of code to use for F1 22 to only flag track limit warnings, even using the F1 22 UDP guide i'm still unsure  

---

We can't really comment on specific code. However, each warning or penalty should generate the following event:

    struct

    {

        uint8 penaltyType;               // Penalty type – see Appendices

        uint8 infringementType;          // Infringement type – see Appendices

        uint8 vehicleIdx;                // Vehicle index of the car the penalty is applied to

        uint8 otherVehicleIdx;           // Vehicle index of the other car involved

        uint8 time;                      // Time gained, or time spent doing action in seconds

        uint8 lapNum;                    // Lap the penalty occurred on

        uint8 placesGained;              // Number of places gained by this

    } Penalty;

Depending on what you are trying to do, you should be able to read in the penalty events ("PENA") and discard any events that you aren't interested in. The appendix contains info for the different penalty types (warning, time penatly, etc.) as well as the infringement type. There are a lot of different infringement types, including 6 specifically for corner cutting, plus some others about unfair ways of gaining a time advantage, so it's worth checking through the list to see which ones you care about.

@Hoobiechoobie 

About warnings

This could be a bug but for all the people that uses Simhub right now your solution is the proble

Simhub does not access the event packet, so we can't read penalization codes.

Moreover, what is the point to count warnings if it's not as a prelude to penalties. 

The bug you think you had was the best way to approach this matter. No one cares how many other warnings have, only the ones that precede a penalty.

Please, reconsider this point