Hacker News Reader

Comment by Jean-Papoulos | Hacker News Reader

They didn't, it just needed a restart. From the first reports the first car's software genuinely glitched out because of the new track/rain/etc and had to be restarted, the other cars got anti-traction control triggered because going this slow for this long unspools the turbo, which got so bad the detection software made a false positive.

View on HN

They did, teams confirmed there was an update being deployed during the delay after the aborted formation lap.

Restarting in Hamilton's case "fixed" it because it removed the condition it was in, if he would have done the lap again, it would have happened again.

there's no traction control or other driver-assistance aids (ABS etc) in f1 cars

That's what the rules say, anyway. Cheating is part of the game, and @ActuallyVen goes into some of the ways teams have played with the rules.

https://youtube.com/@actuallyven

or if it is there, it is definitely, surely, cross my heart, not enabled in prod [1]!

[1] https://en.wikipedia.org/wiki/Allegations_of_cheating_during...

I think that's what he is saying that the anti-cheat falsy detected it as traction control

I mean, the article literally says a firmware update was deployed mid race to remove power limits, is the article wrong?

Teams confirmed it was a firmware update on the broadcast. Article is correct.

Not literally mid-race.

The initial formation lap was aborted due to the glitch (caused drivers to slow to a crawl or stop). The cars all went back to the pits. Then there was a long delay while FIA/teams/ECU provider figured out what was wrong. And eventually fixed it via a software update.

Reply on news.ycombinator.com