Codemasters Team
Codemasters Team
@Fi7i wrote:
Thank you @Hoobiechoobie, and thank you @cgfdoo that was useful.
Also, I see that starting from 127, the driver ids are inconsistant compared to F1 2022, is that intended ?
For example, Jake Hughes is 127 in 2022 and 129 in 2023, and mostly every ones after that.
This was not intentional - we try to add to the existing list where possible. Unfortunately, this looks like a byproduct of multiple teams working in parallel on similar parts of the game, so they all thought that they were adding to the list!
Great updates. Havent tested any of it yet, but very happy with all the new data. Last few months I've been working on a app, especially aimed at racing leagues. The idea was to have some sort of driver rating per race. At the end of the race a card is generated for each driver based on laptimes, throttle & breakinputs and overall race result. A 50% race would generate a database file of 2 MB. That's it.
However, there are some issues that I've run in to I've had to hack myself. For example:
Safety cars.
We have a new SC counter right now in the session packet, but I'd think it be a better approach to do in the SessionHistory packet.
For ex.
isSafetyCar = 0,
isVirtualSafetyCar = 1.
And once it's 1, it can never return to 0. So if the VSC ends, it should remain in the data to show a lap was not clean due to race control.
Right now I check the session packet for safetycarstatus and update the lapdata accordingly. Because one driver could still be in Lap 2, and the other in Lap 3. I use clean laps to calculate avg laptimes.
