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?
this post was submitted on 13 Mar 2026
10 points (100.0% liked)
Formuladank – The No.1 source for motorsports news since 1837
4774 readers
42 users here now
Are we checking? This is a place to take a p*ss out of motorsports.
F1 is not the only motorsport in the world, so go ahead and post your shitposts about WEC or MotoGP or IndyCar or ralley or Polish Speedway or whatever. Even Formula E, I guess. It needs some love, too.
By the way, F2 > F1.
Rules? What rules? Stop inventing. Just don't be a douche. Lemmy.world's sporting conduct applies.
If you experience connectivity issues read https://catbox.moe/faq.php
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.