Here is the current specification for the UDP telemetry output system for F1 22.
To report any bugs with the UDP system, please add a new topic into the bug reporting section of this forum and ou...
Hi @Hoobiechoobie , one of our users asked for a clarification since some data are related in an "unexpected" way.
The user lowered the values of "m_frontSuspensionHeight" and "m_rearSuspensionHeight" (structure CarSetupData), from 11-8 to 9-6, with the expected behaviour for the car to stay "lower" on track.
But the "unexpected" result is that the values of "m_suspensionPosition" (structure PacketMotionData) increased instead. E.g. - in the example highlighted below - the FR increased from 300mm to 362mm. The increased values are clearly consistent on all the suspensions during all the lap.
The expectation was to see a lower number for the "suspensions position", assuming it was related to its length and its attachment point to the vehicle. But since its value increased instead, it's not clear what this value is reporting.
Could you please provide some details on what the values in "m_suspensionPosition" are measuring, and how they relate to "m_frontSuspensionHeight" and "m_rearSuspensionHeight"?
Could you please provide some details on what the values in "m_suspensionPosition" are measuring, and how they relate to "m_frontSuspensionHeight" and "m_rearSuspensionHeight"?
This value measures at what point of the travel of the suspension you are at at that moment, so a lower number = higher in the suspension and vice versa. Hopefully that answers your question.
it's clearer now, thanks a lot. One last question: could you confirm the unit of measure for "m_suspensionPosition"? it seems in millimetres, is it right?