Codemasters Team
@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.
Unless it's a short race, or a track like Belgium.
It's purely an educated guess, or hardcoding it. Just having the session type different would make sense. That would also let you know whether a pitstop is required or not.
It wouldn't require any extra data to be sent.
e.g. if it's a race and 5 laps, or sprint, then a pitstop isn't required.
@RJ80F1 wrote: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.
From what I remember what the custom HUDs do, you could potentially check the weather forecast packets to find Sprint Weekend and Normal Weekend - for sprint weekends, there should be sessionType 10 and 11 described (with 10 being Sprint and 11 being Main, which converts to 10 later on because logic). Otherwise, there is no real way to differentiate between Sprint Race and Main Race.
Regarding mandatory pitstop, I could see some potential for the UDP value in the future here - especially useful for F2 when they have mandatory pitstops also and whether they count or not.
Hopefully the answer makes sense as I am writing this at 2 AM.
Yeah makes perfect sense. I had the same exact thought yesterday morning about that, but hadn't got round to proving it. Same possibly with tyres packet, as that has recommended session I think.
Not really raced F2 myself, so not sure on the rules, but it would make sense to have an overall packet that told you sessions coming up in the weekend with lap count and rules etc.
