F1 23 UDP Specification

Thanks, @Hoobiechoobie ! Also updated our diffs to see changes between 2022 and 2023 https://github.com/hotlaps/f1-game-udp-specs/tree/main/diff_2022-2023

Thank you @Hoobiechoobie, and thank you @cgfdoo that was useful.

Also, I see that starting from 127, the driver ids are inconsistant compared to F1 2022, is that intended ?

For example, Jake Hughes is 127 in 2022 and 129 in 2023, and mostly every ones after that.

Thanks @Hoobiechoobie!

Is there any chance we could get all of the PacketMotionExData published for both player cars in split-screen mode?

In previous versions (where this data was wrapped into the Motion Data packets), only the "extra" data from Player 1 was available in splitscreen.

Second question. 🙂

In PacketMotionExData, what units are the tire forces in m_wheelLatForce, m_wheelLatForce, and wheelVertForce?

@cavalier-racing
I would expect wheel forces are G-Force components, same as for CarMotionData

(so 1g = 9.8 m/s2, same as gravitational acceleration)

Ok one more, and I apologize if this is a dumb question.

Is it possible to get the track limits (inner boundary and outer boundary) as a set of XYZ points expressed in whatever coordinate system is used in the motion data packets for the "worldPosition" fields?

@cavalier-racing   I would expect that to be hard-coded in game files as it isn't something that changes over time. @Hoobiechoobie  can you pls confirm?

I'd say there is a way to collect such data, just drive over the white line and get car coordinates from packets 😉

If this was added to telemetry, I'd expect an event for a track limit violation instead.

Does anyone know which team ID 138 is? I can't find it in the team ID appendix.