F1 22 UDP Specification

---

@ThibaudPHP wrote:

and for ps / xbox racer, we will have a steam id or something to identify who is who ?

---

Crossplay isn't enabled at launch. It's a feature that's TBA (to be announced).

The restricted telemetry option will include 'Show online ID / Gamertag' - this won't affect the in-game display but it will affect the received telemetry (AIUI it will be missing and say 'Player')

So as it stands there is nothing to stop gamertags from differing platforms to be in conflict, but the game will understand the difference from the unique participant ID / network ID.

Quote

Participants Packet

This is a list of participants in the race. If the vehicle is controlled by AI, then the name will be the driver name. If this is a multiplayer game, the names will be the Steam Id on PC, or the LAN name if appropriate.

N.B. on Xbox One, the names will always be the driver name, on PS4 the name will be the LAN name if playing a LAN game, otherwise it will be the driver name.

Does the UDP in this allow use of multiple devices? For example in prior years games I could only run either my display or shakers but not both. There had to be convoluted hacks to try and get them to both work at the same time.

---

@F1Aussie wrote:

Does the UDP in this allow use of multiple devices? For example in prior years games I could only run either my display or shakers but not both. There had to be convoluted hacks to try and get them to both work at the same time.

---

As far as I understand, this more-so depends on the implementation by the software used, rather than an inherent problem with the current system

In many cases, the issue may come from the listener not allowing multiple binds to the same port. This seems to be the default behaviour on .NET languages, which can then be overwritten with SocketOptionName.ReuseAddress

Although I need to admit I haven't looked into this too much (my software doesn't even allow different ports to be used!)

---

@up100 wrote:

---

@F1Aussie wrote:

Does the UDP in this allow use of multiple devices? For example in prior years games I could only run either my display or shakers but not both. There had to be convoluted hacks to try and get them to both work at the same time.

---

As far as I understand, this more-so depends on the implementation by the software used, rather than an inherent problem with the current system

In many cases, the issue may come from the listener not allowing multiple binds to the same port. This seems to be the default behaviour on .NET languages, which can then be overwritten with SocketOptionName.ReuseAddress

Although I need to admit I haven't looked into this too much (my software doesn't even allow different ports to be used!)

---

FYI the info there is not quite correct.

Re @F1Aussie 's question, they asked about "multiple devices". Multiple device support is really dependant on the game's output of the telemetry. The F1 games have supported outputting to multiple devices for a long time, there is a "Broadcast" mode flag in the telemetry settings that will do just that. For most people it should just work, however some networking hardware can be a bit problematic with broadcast data and either cause lag, or not relay it at all. Usually this can be solved with settings changes to the router, or it is possible that using a subnet broadcast IP (with broadcast mode off) may also work (i suspect F1 uses a global broadcast and subnet broadcasts are slightly better supported, but I have never bothered to actually confirmed this for sure).

@up100 's response only really applies to using multiple apps on a single device with them all being able to receive telemetry. The socket binding settings can lock a port to a single app, so unless the telemetry app allows socket reuse then other apps on the same device cant also listen for telemetry.

@cjorgens79I don't think there is necessarily anything incorrect with what I've said, other than my comment included an example in which two devices would both have their commands or data passed to them through two programs on the same machine, rather than having the devices themselves have the capability to deduct what to do with the F1 games' UDP data

Thanks for the replies guys, I don't understand the technicalities of it all but I could never use my fanatec displays and simhub for my shakers together, it was always one or the other but never both. The f1 series are the only racing games I have ever had this issue with.

Simhub have a relay function to transfert the udp packet to another adress.

Can someone confirm how the sprint race session_type will work for F1 Grand Prixs in F1 2022? 

From F1 2021, my understanding is this:

• F1 races --> session_type 10 (R)
  
  
• F2 races:
  • Sprint --> 10 (R)
  • Feature race(s):
    • If there is just one --> 12 (R3)
    • If there are two (which I admittedly don't know why that is an option?) --> first one has 11 (R2) and second one 12 (R3)

Since F1 2022 is the first game that supports sprint races for F1 as well, what is the race session_type logic? Will the main ("feature") race always use 12 (R3)? Or will it be 10 (R) for Grand Prixs without sprint, and 12 (R3) for GPs with sprint (where sprint would get 10)? 

Thanks in advance for the help!

---

@ThibaudPHP wrote:

Simhub have a relay function to transfert the udp packet to another adress.

---

Okay, may look into that then, thanks for the heads up

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