F1 22 UDP Specification

[CanTQuiT]

LapHistoryData / LapData data package:

uint16 is a little bit too small for m_sector(X)TimeInMS data for slow drivers, when they need more than 65,535 seconds per sector? (e.g. safety car phases)

We have then an overflow value problem.

Please spend some more bits for that.

[prime_goose]

@CanTQuiT at least lap history packet should have 32bit sector times

[chuschus]

Hi

Would it be possible to obtain the array of available (  new & used)  tyres at the beggining of the session? (agelaps & compound for each tyre)

[mantazzoLTU]

After analyzing the document, I have a potential suggestion.

Now, it's nice that we're getting SOME identification for drivers this year, however I feel like some of this is questionable - considering Cross-play should be arriving later, how would you differ between an Xbox driver and, let's say, a PS driver? Both would probably just show names... And not to mention that even PC will be releasing on multiple platforms this year (Steam, Origin, EGS) which brings the question of how would you identify between them.

My suggestion - implement a new platform identification field, potentially in "Participants" section, something like this:

uint8    m_platform;    // the platform driver is racing on: 0 - unknown, 1 - PC Origin, 2 - PC Steam, 3 - PC Epic, 4 - Xbox One, 5 - Xbox Series, 6 - PS4, 7 - PS5

// NOTE: if it's possible, maybe also differentiate different types of consoles, if it's worth it?

Hopefully this suggestion would not be difficult to implement and it would be useful. Also, I don't think it should be "Restricted".

[BernoAUS]

Will we get an updated doc with Driver and Team ID's in the appendix?

[Hoobiechoobie]

We'll update the doc with some of the suggested amendments and additional info ahead of release.

[cgfdoo]

For whoever prefers a better experience when viewing changes between versions, I've put up the diffs for packets that seemed to have changed on our GitHub https://github.com/hotlaps/f1-game-udp-specs/tree/main/diff_2021-2022

[Ultrasonic_77]

---

@CanTQuiT wrote:

LapHistoryData / LapData data package:

uint16 is a little bit too small for m_sector(X)TimeInMS data for slow drivers, when they need more than 65,535 seconds per sector? (e.g. safety car phases)

We have then an overflow value problem.

Please spend some more bits for that.

---

65,535 seconds is over 18 hours?

[ThibaudPHP]

same for Lap Data Packet

uint16 m_sector1TimeInMS; // Sector 1 time in milliseconds
uint16 m_sector2TimeInMS; // Sector 2 time in milliseconds

[up100]

---

@Ultrasonic_77 wrote:

65,535 seconds is over 18 hours?

---

Assuming your country uses commas to separate large numbers, he meant 65.535 seconds 🙂

https://en.wikipedia.org/wiki/Decimal_separator#Usage_worldwide