Somehow even still going exactly 325 well into the braking zone:
Can someone calculate the G-force of the speed going down from 325 to 125 within a single data point?
One of the comments points out that this is public data. If either the team or fom was manipulating the data it would be a lot less obvious than this
Unless the car is governed at 325, it seems more likely that the telemetry stream dropped out for a bit, then came back. When no data packets were received, the client program just kept repeating the same stale values to keep the graphs going.
It’s cheaper and easier to do it that way than to program graphics that describe “no telemetry received” into the graphs.
It’s on many cars at many points in the session. They are trying to hide the super clipping issue.
Even the example given is 3 cars at different points (their fastest laps).
You can also see the speed went above the 325 and when it started to come down it was held at 325 till well into the braking zone. When watching you can clearly hear and see the cars slowing down. Plus they do a lot of lift and coast into the corner at the end of the straight to re-gen, otherwise they have to do the rest of the lap without any battery power.
I don’t have much against battery management but this is pathetic… Blatantly lying about telemetry seems like the absolute worst way to handle this „issue“