Lopensky

Thanks man, this is so important.

Any news?

I want to point out this problem. It does not seem to me it has been reported to date, although it is very critical for those who are going to use the game for organized online leagues. When this bug occurs, both the player who has rejoined and other players in the lobby (even if they haven't had any problems up to that point) may find themselves having it. Players whose game is bugged in this circumstance will no longer receive warnings. I could only see the problem on PS4, not having other consoles. But I assume it is likely to occur on other platforms as well. 1.09 Multiplayer Online, Unranked Lobbies Not with absolute certainty. It doesn't happen every time, and when it does it happens randomly to one or more drivers. The bug seems to happen quite frequently when - during a race - one of the players disconnects and then rejoins the lobby. Honestly, I don't know how to solve the problem, also because the drivers affected by this have no interest in solving it, but rather exploit it to their advantage against the others. Often and willingly they don't even report it for the same reason. I use the Logitech G29, but I know it has also happened to drivers who play using the gamepad. I don't think the peripheral has anything to do with it. Not at the moment, but if I can find some material I will post it.

Hi! After the new patch, the game shows some useful informations related to pit stops in the "Pit Stop" tab of the menu during the races. Is there any way to get this info out (like we already do for other similar events) now that it has been added? That would be really useful. Thanks!

Yup, now it finally works! Thank you for the help, you saved me really a lot of time! ❤️❤️❤️❤️

EDIT Sooooo THAT is the problem. uint is 4 byte and not 1.... THANK YOU. I'll try this right now!

Really sorry man, i was taling about the trackLength field, but copied the wrong one. Is this a 2 bytes data? Cause i have some problems reading the data. About the calculation i have this: 20 bytes Header + 21 bytes (other data in Session Packet) + 21 * 5 = 105 bytes (marshal zones) = 146 bytes I'm quite sure thre is something i'm missing.. but can't sort it out.

Con someone please explain me how this field works? Reading this field as stated just wreaks the sequence, wrecking out all next read data. I made a try with a field size of 4bytes (float) and this ust made all next data came out corrrectly, but still have a wrong read value in this field. I noticed also that the session packet is reported with a size of size: 149 bytes , but looking at the documentation you provided i find it out of 146 bytes. Can someone tell me what is wrong in the struct or in my tests? Thank you..

Can someone please make a quick sum up of the main differences between F1 2018/2019 UDP packets? As i can see there should be a change in some fields (car tyre compounds, exhaust damage, yourTelemetry) and in the maximum size of the packet (from 1341 to 1347 if i'm not wrong). Something else big to add something usefull? Did i forgot some field who has changed since last year structure?