Codemasters TeamCan we please get an updated UDP Documantation ASAP?
Car IDs got changed I am absolutely NOT in the mood to check every car by hand!
Thanks.
@Hoobiechoobie
I have a question regarding UDP data output documentation which is essential from my point of view to know, but concrete declaration completely missing even in most recent doc :
- unit definition for all "m_localVelocity" (assuming it should also be "m/sec")
- polarity for those velocity values missing (like positive to right / front / up direction or vice versa) also those may be still possible to evaluate
- polarity for all angular velocity components which is from my point of view most important since it is hard to evaluate
Also it would be for sure helping everybody who wants to involve in some application using this telemetry to define which direction in world space / local space should be meant
(like e.g. X corresponding to lateral movement / sway, Z = longitudinal etc.).
I know this from our racing simulation who clearly define those from the start. Makes it really much easier :-)
Just to explain where such question comes from : I am currently translating telemetry provider (software plugin) for a DIY motion simulator project (existing one for previous F1 sim already existing) and it is working well yet for all standard effects (which can directly be derived from standard telemetry data values) but to add more sophisticated effects like traction loss etc. it is necessary to dig much deeper into existing tm to be able to proceed further motion calculation.
Thanks in advance for your help :-)
