455K views · Feb 5, 2022 · 9:11 · 0 HN recommenders · 7 mentions · discussed 2022
AI Addict reviews a Tesla Full Self-Driving Beta drive, showing hard braking, red-light running, wrong-way turns and a collision with a bollard. The video is timestamped by incident.
Why Hacker News points people here: Cited as evidence that FSD beta is unsafe and that self-driving is far from solved.
“the time of the collision is 3:30.”
Direct link to the FSD beta crash video, collision at 3:30.
The video was embedded in the article he linked, but for maximum convinience the direct link is this video and the time of the collision is 3:30.
“Had they not intervened, the damage would have been much worse.”
Crash starts from the 3:26 mark: [0]. Had they not intervened, the damage would have been much worse. Further in the video, it has repeatedly become confused in trying to drive through the pylons - again the driver intervenes. This is just one of the many reasons why FSD is not only putting drivers at risk, but it is really turning its customers into real-life crash dummies. A more accurate re-brand of this product should be something more like 'Fools Self Driving' than 'Full Self Driving', given the false advertising and lack of safety features for these drivers using the product. [0] this video
“the route planning seems to work overtime to avoid making a specific turn”
Interestingly at the beginning of the video the route planning seems to work overtime to avoid making a specific turn. See about 25s in: this video That's kind of like what you're describing, but more dumb where the car tries to avoid the trouble spot entirely.
“you only need to watch a few videos of them encountering similar markings on YouTube”
Melbourne doesn't generally have what Autopilot would consider "normal" roads, though. The incident involved someone getting off a tram, so the road would have looked something like this: link In the future, perhaps Teslas will handle this well, but you only need to watch a few videos of them encountering similar markings on YouTube to know that this type of road currently results in massive confusion for a Tesla. Example: this video
“this 'safety-critical' beta quality software”
> Works just fine for my two cars thanks.. This just reads 'Works fine on my machine' . > I feel like you haven't driven one? One does not need to be a beta tester or a crash test dummy to see enough reports and tests from others over the years, risking their lives on using this 'safety-critical' beta quality software to know that this contraption needs to be investigated and the reports speak for themselves. [0] [1] [2] [3] [4] [5] [0] this video [1] link [2] link [3] link [4] link
“in the city, on a mountain road, anywhere with snow or heavy rain or fog, it's game over”
On a straight highway in sunny california maybe, in the city, on a mountain road, anywhere with snow or heavy rain or fog, it's game over and will always be if we keep using the current techs this video
“Collision with bollard in Feb 2022”
> No, I think this argument is largely correct. And frankly settled: anyone who's driven recent FSD beta versions knows very well that the cars "see just fine". They don't hit anything, they see and avoid obstacles. Only if you ignore times where intervention stopped it from hitting something, times where it did actually hit something, massive amounts of jitter and popping in the visual output, phantom braking, etc. Unless of course "recent" means n+1 where n is the version that crashed into something. Collision with bollard in Feb 2022: this video attempts to plow through cyclist Feb 2022: link almost crashes into tram (can't gauge speed or direction?) Jun 2022: link Crashes into curb Aug 2022: link Phantom brake Sep 2022: link Almost colliding with bridge pillar 2 weeks ago: link Crashes into various objects in testing 2 weeks ago: link
