gparent

I will do my best to continue updating the spec and publish it in a format that's easy to work with for the community, as opposed to a proprietary document. I'm a little late but I haven't given up. https://gitlab.com/gparent/f1-2020-telemetry/ Example for 2020: https://f1-2020-telemetry.readthedocs.io/en/latest/telemetry-specification.html

No worries. Once I have some free time I'll make a release with the F2 2020 changes. I'm missing driver IDs at the moment. I have the team ones.

I took them myself.

This may help for F2 tyres: https://gitlab.com/gparent/f1-2020-telemetry/-/commit/6063dd6dc3b82743ab8597f58d09493117750590 Keep in mind the visual and actual tyres are different values.

Please drop the attitude. If you're a good developer, you actually update your documentation more than once every 3 years. While of course forum users need to search, there's literally 0 reason whatsoever why we would need to read three year's worth of history instead of just having the reason summarized in the original topic. There's no need to defend the obviously outdated and broken documentation that was shipped with 2020, copy pasted mostly from 2019.

Because you're a child who enjoys messing people's virtual racing. That's about 80% of the races in Unranked, and they usually run with reduced damage.

When you receive the LapData packet, loop over the vehicles and use the m_carPosition member to determine who is first. I store that in a list that I create beforehand. In Python: positions = [*range(22)] def _car_lap_data(lap_data_packet): for vehicle_index, vehicle_lap_data in enumerate(lap_data_packet.lapData): positions[vehicle_lap_data.carPosition - 1] = vehicle_index # positions[0]'s value is the vehicle index of the pole position. # positions[1] is 2nd place's vehicle index

The values for F2 compounds are incorrect (they were incorrect in 2019 as well) Actual compounds: 11 = super soft, 12 = soft, 13 = medium, 14 = hard, 15 = wet Visual compounds: 15 = wet, 19 = super soft, 20 = soft, 21 = medium, 22 = hard

+1 for the second point. I had to get those myself in the previous game and both the actual and visual compounds differed between F2 2019 and F2 2018.

No worries and thanks a lot for providing the values.

The team IDs are in the appendix already, at the bottom of the third column.

Looking at the definition for WeatherForecastSample, it has a time offset in minutes. So you would get N forecast samples (up to 20), and then you could tell with the offset when they are supposed to apply. I'm really happy to see penalties broken down in this way. I'm also hoping that spectators can now receive events like fastest lap and all of the other events they do not receive in 2019. Thanks for the good work. EDIT: Here are some suggested fixes: uint32 and double are missing from the types In *CarSetupData*, the comment for the m_rearAntiRollBar field refers to