Hi
@TinMan_JB,
The app
should record results at the end of each lap. There might me some inconsistencies on the first lap as ACC sometimes doesn't report the first or even second sector. I'm afraid, there's not much I can do about that as I'm totally dependent on the information ACC provides. Lap 1 should give a laptime but for online this looks to be time from joining race until end of lap 1 (ie in the region 2 - 20 minutes from what I've seen). Curiously, Bathurst always appears to be the actual lap 1 time. Maybe Kunos will address this in future.
The laptime displayed depends on the mode. In Player Car/All Cars mode (ie displaying all laps), this will be the laptime of each lap. Final Standings gives your "position" at the end of the race and each player's fastest lap, with the associated sector times. The position might disagree with the final timetables in ACC and in the server results file
- The server result file I think is going to be the most "correct". It should apply post race penalties and discount players leaving before final classification. However, if memory serves, I don't think the gaps are stored/can be calculated
- ACC timetables apply post race penalties but are skewed by players leaving before classification. Gaps are correct (perhaps)
- ACC Results Companion still counts players that leave before classification for positions. It can't adjust for post-race penalties (I'll come to that in a minute), so some positions might not be correct, if penalties are to be applied post race. Gaps should be the same as with ACC timetables (I think).. Note penalties server during the race will be taken account of as they will affect your recorded time (via DT, Stop&Go or DQ)
Gaps aren't quite as they should be though. The gap should be the actual time for a following player to reach where a place (ie the finish line) after the preceding player has crossed it. The gap I use (which I think is the same as for ACC) if when the following player crosses the finishing line, it is the estimated time to get to where the preceding player is now. Ultimately, this should produce roughly the same time, but there could be anomalies (eg preceding player crashes/stops immediately after finishing line will skew the time). The reason I record this way is two fold
- This is the way ACC supplies information out of the box
- For me to calculate the "real" gap would require me to have a much higher sample rate - I want to keep the sample rate low to minimise the impact of my app on performance
I've put in place a mechanism to record penalties, but currently (ACC 1.3.12), it looks like ACC isn't outputting them on the Broadcast interface (I've only seen messages when penalties are cleared). I understand there's some mapping issue they need to fix. Once penalties are output, I'll display them, then I guess I'll need to look at the SRO rulebook to see how they are displayed post race (although there looks to be a post race penalty type, so hopefully that does all the hard work for me).
If you need me to look at the discrepancies between the server and ACC Results, send me the server file and the ACC Results diagnostics. (right click the session, select Export Diagnostics and attach the zip file created - you might need to change the file type from zip to txt to attach here)
Doug
![Luca [OT]](/data/avatars/s/3235/3235113.jpg?1697196734){kind=avatar}
