We’ve made some changes to the UDP data based on your feedback. This has resulted in multiple changes to the packet structure, so please check against the latest spec on the first page of this thread to see what has changed. The intention is for this to be the final 2020 specification now – we don’t plan on making any structural changes unless a serious issue is found. We can obviously still fix bugs if the data isn’t working correctly, so please let us know if you spot anything wrong.
The changes that have been made are:
Beta 2: Added m_secondaryPlayerCarIndex into the PacketHeader to identify the second player in splitscreen mode
Beta 2: Updated the comments in the ersDeployMode of the CarStatusData packet to show the correct ERS values
Beta 3: Added the MFD panel index to the PacketCarTelemetryData to identify what HUD screen the player is currently viewing
Beta 3: Added best sector times and lap numbers to the LapData packet to allow tracking of the best sector times in the session. Note: all sector times have been changed to milliseconds (uint16 instead of float) to reduce the packet size to make room for the extra data
Beta 3: Added m_drsFault to the CarStatusData packet to show when DRS has been disabled due to a technical fault
Beta 3: Added a Speed trap triggered event (“SPTP”). This provides the vehicleID and speed of the fastest car to pass through the speed trap. Note: the intention is to change this so that it triggers whenever a car beats its own speed trap record, rather than just showing the fastest car.
Beta 3: Bug fix to correctly show front wing damage as 100% in the UDP data when wing is removed
Beta 3: Bug fix to only show data for active cars
Beta 3: Updated driver ID table in the appendices as some drivers were missing or using incorrect IDs
Beta 3.1: Added m_drsActivationDistance to CarStatusData to indicate whether the car has passed detection and when it will be available in the subsequent activation zone (next patch)
Beta 3.1: Suggested gear added to the car telemetry packet (next patch)
The final two points may result in a data mismatch until the updated beta patch comes out with these new fields added. I decided to post the intended final spec rather than changing this multiple times in the same week.