Codemasters Team@chuschus, It's also the option but it will waste 22*16bit for each PacketLapData.
I believe that's why for sectors time we have
uint8 m_sector1TimeMinutes;
uint8 m_sector2TimeMinutes.
@BobaFed25 wrote:@chuschus, It's also the option but it will waste 22*16bit for each PacketLapData.
I believe that's why for sectors time we have
uint8 m_sector1TimeMinutes;
uint8 m_sector2TimeMinutes.
OK, maybe we could let m_deltaToCarInFrontInMS come out of the packet, since we can get it from m_deltaToRaceLeaderInMS (my delta to leader - nezt car delta to leader), that would leave the packet the same size.
@Hoobiechoobie Meanwhile, I would propose that if the difference reaches the maximum of 1:05.535, the value should not be reversed and remain at 65535, which would at least allow us to know that the value is at its maximum. Now once at the maximum it goes back to 0, which completely falsifies the data if the time exceeds one minute and 5 seconds.
Is there anyway of telling the difference between a Sprint and a Race.
Both are m_sessionType of 10, and you can't really tell that I've seen which it is apart from hardcoding the lap count vs track and telling from that as long as none of the race %ages overlap.
Or at very least whether a pitstop is required in the race or not if it stays dry.
It would also be useful being able to tell in practice sessions what the following sessions are going to be.
