Codemasters TeamCodemasters TeamHere's a summary of the UDP output changes that we've got lined up for the next product:
We can provide more details in the UDP thread that we create for the next product / beta.
Delta!
What good news with UDP data. Hopefully the game will also include some much-needed improvements to its stability. And please, the option to choose the immersive pit button in the menús.
Hyped
Some really good changes! Is there going to be anything added that lets us know when the plank is striking the ground? (Or have I missed that?)
Hi, great changes. Is it possible to get more UDP data in Time trial? When you now read the data, the normal fields like DRIVER.POSITION01, 02 and 03 are used. It would be great if we could have fixed values lik:
- Observerd Driver (Team, Name, LastName, Sector1time, Sector2time, Sector3time)
- Personal Best (Team, Name, LastName, Sector1time, Sector2time, Sector3time)
- Rival (Team, Name, LastName, Sector1time, Sector2time, Sector3time)
And If we can see in the data what kind of Assists the rival uses, and if he uses a setup. We can see that in the menu, but would be great to get it out of the data to.
And for all sessions, is it possible to get the data of the Fastest Sector Drivername and Team? Per sector?
@Hoobiechoobie Thanks for the heads-up, it looks like there are some nice improvements in there. Any idea when we can expect the UDP spec to be published?
I was wondering if anyone on here could offer some insight into any good tools that could be used for leagues, I've seen quite a few people who have spoken about their tools but haven't been able to find any more info. Would love to be able to test out some of these others as alternatives to big ones such as Iko Reins and TAS. Feel free do drop some suggestions or any links to my dms, not too sure how this thread works so if you are allowed to post here then doing that also!
I love your tool and think its amazing but I don't have the budget to use it unfortunately
Hi. I'm newbie here, but need some help. I'm trying to get the UDP data from telemetry for a school project, in which one we need f1 car telemetry data. Is there any forum or disc to discuss?
My problem is about getting the PacketCarTelemetryData. I'm trying (on python) to print the struct formated to bytes of the packetID = 6, but the info it shows is always the same:
Packet ID: 6
Car 1 - Velocidad: 239.01 km/h, RPM: 23644
Car 2 - Velocidad: 282.52 km/h, RPM: 0
Car 3 - Velocidad: 168.22 km/h, RPM: 0
Car 4 - Velocidad: 0.65 km/h, RPM: 48640
Car 5 - Velocidad: 0.0 km/h, RPM: 16830
Car 6 - Velocidad: 0.0 km/h, RPM: 0
Car 7 - Velocidad: 0.0 km/h, RPM: 0
Car 8 - Velocidad: 0.0 km/h, RPM: 128
Car 9 - Velocidad: 0.0 km/h, RPM: 256
Car 10 - Velocidad: 0.13 km/h, RPM: 0
Car 11 - Velocidad: 0.31 km/h, RPM: 31
Car 12 - Velocidad: 79.36 km/h, RPM: 23808
Car 13 - Velocidad: 239.01 km/h, RPM: 23644
Car 14 - Velocidad: 282.52 km/h, RPM: 0
Car 15 - Velocidad: 168.22 km/h, RPM: 0
Car 16 - Velocidad: 0.65 km/h, RPM: 48640
Car 17 - Velocidad: 0.0 km/h, RPM: 16830
Car 18 - Velocidad: 0.0 km/h, RPM: 0
Car 19 - Velocidad: 0.0 km/h, RPM: 0
Car 20 - Velocidad: 0.0 km/h, RPM: 0
Car 21 - Velocidad: 0.0 km/h, RPM: 0
Car 22 - Velocidad: 0.0 km/h, RPM: 0
It's so weird. I'm trying in chrono sessions, but in Race occurs the same.
Looks alike to me you do not well read (or convert to) bytes as you refer to / or possibly your byte-wise read length for struct is too less / too long. It seems already
to happen on car no.1 after you reasonably read car's speed but engine's RPM is already "kind of non-sense").
As you can review from F1 2022 UDP API description sheet complete CarTelemetry data package should have overall length of 1347 bytes and single car's data
is always 60 bytes long; which means in sum that on F1 2022: 22 cars x 60 bytes(=1320bytes) + 24 bytes (header) + 3 bytes (panel's index of active driver,panel's
index for secondary driver, suggestion gear; those are the end of whole data package) = 1347 bytes.
Hope is obvious that you in here always need to read out full package (60 bytes) for each car in sequence before you can access next car's data.
This is what I would (if I were you) in detail review in my readout code.
Hi,
If you still have issues with the stuff, google 'f1 2022 udp python'. I found immediately several repos on github, which might be of help for you.
Cheers.
@ThibaudPHPwell, my code and code from two other projects that I got from github. In my computer I set driver names and telemetry and my player name didnt comr to me!!!
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.
Codemasters Team
@IkoRein wrote:
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.
I’ve done the same, but not really sure if it’s correct.
@Hoobiechoobie 👍🏻 sounds good - if relevant, i would have a look at the telemetry as well
