Re: F1 22 UDP Specification
@chuschus
I understand your case and it's what I assumed as well.
But you don't want to inflate packets to unreasonable size so CM may choose what info is stored in them.
Forum Discussion
1 Reply
- @P4st3l1ak
Yes, maybe it would be possible to put it in the TyreStintHistoryData from the Session History Packet, it would be 3 bytes/second/driver, or it could use bit encoding using 1 byte/sec/driver .
I don't see any other way to implement the commutator wheels.
