Forum Discussion
Is it me or is the final classification packet not working right half the time? Sometimes I'm able to receive this packet in the final screen, sometimes it doesn't send at all, or extremely late (1+ minute, that I've noticed). This is causing me a lot of problems in handling the end of a session. I wonder if it might be because I used the fast forwarding option in a quali session to get to the final screen faster.
Another weird bug I've found is when a qualification session is restarted in the final screen, is that once the new session restarts, m_carPosition of the LapData packet will be the same for all drivers except the player. It gave me a little bit of trouble in my telemetry app, since I was using that as a backup to m_gridPosition in the LapData packet. It's a bit odd that m_carPosition has a meaningful value when the session is first started, but upon restarts it's entirely useless.
EDIT: Remembered another thing - m_frameIdentifier in the header is also always 0 for the Final Classification packet, it seems. I'm fairly sure that's a design choice, but I think using UINT32_MAX would've made more sense, as this is the "end-all-be-all" packet for the end of a game session. It's not the end of the world, though.