Codemasters Team
Codemasters Team@TPMillo I think it just uses "Player".
and for ps / xbox racer, we will have a steam id or something to identify who is who ?
@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:
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?
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.
Codemasters Team@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
Codemasters TeamIs 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?
