F1 23 UDP Specification

"Have some way of being able to link lobby drivers with the drivers once in the session.
Response: We added the player name opt in last year which will hopefully achieve what you need for any players that permit access to their player name. For players that don’t opt in, we are not permitted to have a system that links directly to a players online ID without their consent, so are at the limit of what we can provide here."


Thanks for the response. I understand why player names aren't there by default, but it's a way to link a lobby user with the driver once the session starts. This could be a random number as the user joins the lobby that is passed across to the session, or even keeping the index the same between the lobby and the session, which last I checked, I don't think it did.

Or it might've even suddenly randomly re-adjusts the indexes while in the same lobby.

---

@Hoobiechoobie wrote:

 

Need More Info

• Allow "public" telemetry for AI drivers.
  Response: The AI already show Public data, with the exception of car setup data. This was intentionally disabled due to it being used as an exploit in multiplayer sessions when a  player would pause or exit the game and the vehicle would go under AI control and their setups could be observed by other players. Please could you clarify what you mean here?

---

Yes, I was referring to car setups. I wanted to know their setups in Career modes (DC or MT).

Can it be enabled only in these modes?

---

Won't Do

• Generate Lap Data and Final Classification after retiring from a single player race due to failure or crash, or when skipping sessions and accelerating time.
  Response: Unfortunately, we can’t easily extract this information from these game systems and into the UDP output  due to how and where that this data is created. As such, we won’t be able to take a look at this one.

---

That's a pity because game generates this stuff to show on timing screen and then at session end. so I guess it should be feasible to send such information by UDP as well.

• When there is a Yellow Flag, send in the data what sector the Yellow flag is (so Sector 1, 2 or 3).
  Response: We provide info on which marshal zone this occurs in. This has a finer granularity than sectors, so might be more appropriate depending on your use case. However, I don’t think we provide data within the UDP output to map marshal zones to sectors. Do you have more info on how you intend to use this?
  There is indeed no information in the UDP what marshal Zone is in what sector. I now calculate it by divide the total Marshal zones by 3, and give a message in my Displays when there is a yellow flag in sector 1,2 or 3. Would be nice to just have a output "Flag color sector 1,2 or 3)

• Include the following information in the fastest lap data: Fastest Lap Time, Fastest Lap DriverID, Fastest Lap TeamID, sector times of all drivers per sector, current Sector 3 datapack.
  Response: This additional information can be worked out from the Session History packet with some extra processing.
  But this processing is the thing that costs performance. You have to compare the fastest lap to the lap times of all players, and when you have found it, you have to store that data in a new output. And in times it happens, that you have a glitch (a few MS) where the Fastest Lap data is wrong, and then everything of the calculation is wrong. So a pure output of these values would mean a lot less calculation and more pure data.

And what's the status about the question I had as addon for Time Trial Data?

it would be way much better if they could make seperate data points.
1) personal data
2) personal ghost data
3) rival data
4) nr 1 best data

and that we can get these data from the above 3 items
- teamid
- best lap
- sector 1, 2 and 3
- tc (off, medium, full)
- abs (off or on)
- equal performance (off or on)

Hi folks, I'm working on a telemetry app. I have finished parsing the incoming packets successfully. However, I am a bit confused on how to identify which of the lap times belongs to the player. Let's say I'm playing the game, there are 20 cars lap times sent out. Which one of these corresponds to the player, and not the opponents (be it AI, or online opponents).

Which packet type do I look into for this info?

Thanks

Nevermind, I see that its in PacketHeader

@Hoobiechoobie 

Is it also possible to get the Corner number, and also a output if it's to the left or right (with, low, normal, medium or hard corner).

The Saftecar in this lap would be great to get as a UDP message.

And would be great to get the Event String Codes as a pure UDP code. Like a REDFLAG, TEAMMATE IN PIT, DRS ENABLED and DRS DISABLED. These are now Event String Codes, but a UDP code with output 0 or 1 would be better,

@Raymond-Smits If you look back up this thread, there is a nice way of getting the track layout from somewhere that isn't the game that lists corners.

But once you have the track map and where the car is at the time, you could look at which way most people are turning the wheel thus knowing what way the corner is, or if you're better at maths than me write something that understands the track map better.

Difficulty could be down to how often people make a mistake?

This is probably a dumb question. Does the UDP send rate (default 60 Hz) apply only to those devices on the same LAN/loopback as the sender? Or does this apply to other players in an online lobby as well?

In other words, if I have my send rate set to 120 Hz, will other online players get my car's data more often?

@ragekumar666  no. each user gets their UDP data sent to them at the rate they specify for themselves, your settings don't effect other users or what rate of data they receive from your car.