4 ms·

> The accident in the Bay Bridge tunnel has occurred with Tesla's Full Self-Driving Beta mode active indeed, just as the driver claimed. This is almost certain

> The accident in the Bay Bridge tunnel has occurred with Tesla's Full Self-Driving Beta mode active indeed, just as the driver claimed. This is almost certainly false. This kind of highway uses Autopilot, not FSD beta. In fact in the tweet that they show that simulates that same drive you can see on the screen that it's using Autopilot, not FSD beta.

bobkazamakis 4y ago
this is the exact kind of bullshit that corporations have gotten away with for too long. As a consumer, I do not give one flying fuck what the new hip-slang for computer vision is, call it "put your life in the hands of a company run by the most burned out divorced dad person of the year".
- yreg 4y ago
  One claim is completely different than the other one and the truth is important here.
  - boucher 4y ago
    Not really. In this scenario there's no functional difference between these two supposedly distinct products.
    - yreg 4y ago
      They are two different products with two different tech stacks.
      - lovich 4y ago
        having "self driving" in the name is probably the cause of the confusion. As far as non technical people are concerned, tesla soft ware for driving the car engaged. Whether it was one product or another is immaterial to the fact that tesla software caused the crash
        yreg 4y ago
        >As far as non technical people are concerned But this is hacker news so for us, here, the distinction is important. Which is what this whole absurd subthread is about. Redox pointed out that the article attributes the issue to the wrong product and you all are saying that it doesn't matter. Well perhaps you are not interested in the topic and it doesn't matter for you. For me it matters. --- Imagine an article about a Google Chat issue was posted on hacker news. Redox99 points out that the issue is actually in Google Meet. And then you, bob and boucher appear and you reply that it doesn't matter which one it is, both are google chat apps. Well I believe it matters a lot.
        lovich 4y ago
        The sub thread you replied to started with the poster literally saying “as a consumer…”. It was not a discussion of the technical minutiae, but of the overall situation
- redox99 4y ago
  Finding out which system it was using is pretty much the first step of any kind of investigation, which this is. As a consumer you probably would want to know if this is caused by the autopilot that you are using and have been using for years, or if it's the beta FSD that you have to opt in.
gibsonf1 4y ago
Thats an interesting claim, that the highway would trigger use of autopilot and not FSD. How do you know that? I think Tesla, who would know for a fact the status of FSD during this accident, might want to tweet that FSD wasn't on if it wasn't. But they haven't. Also, as a human, why would you hit the breaks in the fast lane with cars approaching? This does not happen very often, especially on the incredibly crowded Bay Bridge. I actually was there at this accident and swerved just in time to miss the cars piling up (you can see my car in both videos of the accident just getting out). It was a truly scary thing.
- redox99 4y ago
  FSD does not support highways yet, so it automatically switches to autopilot when you enter a highway. You can tell because they use completely different UIs, visualizations, settings, etc (FSD and autopilot are fully separate software). Tesla has been promising FSD v11 which will support highways for a very long time already, but it isn't out yet.
  - gibsonf1 4y ago
    So you're saying that it is literally impossible to use FSD on the bay bridge? If so, why hasn't Tesla pointed this subtlety out?
    - redox99 4y ago
      Literally impossible is kind of a strong statement, but yeah people have driven there and shown that it uses Autopilot there (because it's classified as highway on the map data), which is the expected behavior as FSD does not support highways yet.
      - gibsonf1 4y ago
        Interesting, I wonder what the behavior is when someone turns FSD on when they are already on a highway as claimed in this case, as opposed to someone who has it on before entering. Maybe that's the issue, if you turn FSD on when already on a highway, the car starts FSD, senses its on a highway then given its programming that FSD should not operate on a highway, consequently hits the brakes? Tesla knows whatever happened in fact for sure.
phkahler 4y ago
I'm assuming most people are like me and don't give a shit weather it was FSD or Autopilot or some other software. The car software was driving.
- andrewinardeer 4y ago
  Driver is still responsible for vehicles actions.
  - LadyCailin 4y ago
    Both “Autopilot” and “Full Self Driving” both heavily imply otherwise, even if you’re technically correct.
  - wingineer 4y ago
    Which is what makes these misleadingly-marketed features so controversial…
  - tw98521358 4y ago
    You can’t override erratic braking can you? There isn’t much the driver can do to stop that behavior
    - manicdee 4y ago
      Push the gear stalk up Twist the steering wheel against the direction the car is turning it Tap the brakes These all immediately drop out of AP. The driver also has the option of pressing down on the accelerator to make the car go faster and cancel AP’s anomalous braking. One situation I can think of is using Navigate on Autopilot and the car thinks the exit is much further along than it is, tries to take the “exit” which is actually a concrete wall, AEB kicks in due to imminent collision. But then why haven’t other Teslas had the same issue there?
rising-sky 4y ago
Your counter claim is apparently false based on the attempt at recreation in this linked video. The driver engage FSD while driving into the same section of the Bay Bridge and tunnel https://twitter.com/TeslaOwnersEBay/status/1614083624458125312?s=20 https://twitter.com/TeslaOwnersEBay/status/16140836244581253...
- redox99 4y ago
  That's the very tweet I'm referring to. Look at the screen and you'll see it's autopilot, not FSD (ignore what they say). All these names are confusing to be honest, so it's understandable that people mix them up.

bobkazamakis 4y ago

this is the exact kind of bullshit that corporations have gotten away with for too long. As a consumer, I do not give one flying fuck what the new hip-slang for computer vision is, call it "put your life in the hands of a company run by the most burned out divorced dad person of the year".

yreg 4y ago
One claim is completely different than the other one and the truth is important here.
- boucher 4y ago
  Not really. In this scenario there's no functional difference between these two supposedly distinct products.
  - yreg 4y ago
    They are two different products with two different tech stacks.
    - lovich 4y ago
      having "self driving" in the name is probably the cause of the confusion. As far as non technical people are concerned, tesla soft ware for driving the car engaged. Whether it was one product or another is immaterial to the fact that tesla software caused the crash
      - yreg 4y ago
        >As far as non technical people are concerned But this is hacker news so for us, here, the distinction is important. Which is what this whole absurd subthread is about. Redox pointed out that the article attributes the issue to the wrong product and you all are saying that it doesn't matter. Well perhaps you are not interested in the topic and it doesn't matter for you. For me it matters. --- Imagine an article about a Google Chat issue was posted on hacker news. Redox99 points out that the issue is actually in Google Meet. And then you, bob and boucher appear and you reply that it doesn't matter which one it is, both are google chat apps. Well I believe it matters a lot.
        lovich 4y ago
        The sub thread you replied to started with the poster literally saying “as a consumer…”. It was not a discussion of the technical minutiae, but of the overall situation
redox99 4y ago
Finding out which system it was using is pretty much the first step of any kind of investigation, which this is. As a consumer you probably would want to know if this is caused by the autopilot that you are using and have been using for years, or if it's the beta FSD that you have to opt in.

gibsonf1 4y ago

Thats an interesting claim, that the highway would trigger use of autopilot and not FSD. How do you know that? I think Tesla, who would know for a fact the status of FSD during this accident, might want to tweet that FSD wasn't on if it wasn't. But they haven't. Also, as a human, why would you hit the breaks in the fast lane with cars approaching? This does not happen very often, especially on the incredibly crowded Bay Bridge. I actually was there at this accident and swerved just in time to miss the cars piling up (you can see my car in both videos of the accident just getting out). It was a truly scary thing.

redox99 4y ago
FSD does not support highways yet, so it automatically switches to autopilot when you enter a highway. You can tell because they use completely different UIs, visualizations, settings, etc (FSD and autopilot are fully separate software). Tesla has been promising FSD v11 which will support highways for a very long time already, but it isn't out yet.
- gibsonf1 4y ago
  So you're saying that it is literally impossible to use FSD on the bay bridge? If so, why hasn't Tesla pointed this subtlety out?
  - redox99 4y ago
    Literally impossible is kind of a strong statement, but yeah people have driven there and shown that it uses Autopilot there (because it's classified as highway on the map data), which is the expected behavior as FSD does not support highways yet.
    - gibsonf1 4y ago
      Interesting, I wonder what the behavior is when someone turns FSD on when they are already on a highway as claimed in this case, as opposed to someone who has it on before entering. Maybe that's the issue, if you turn FSD on when already on a highway, the car starts FSD, senses its on a highway then given its programming that FSD should not operate on a highway, consequently hits the brakes? Tesla knows whatever happened in fact for sure.

phkahler 4y ago

I'm assuming most people are like me and don't give a shit weather it was FSD or Autopilot or some other software. The car software was driving.

andrewinardeer 4y ago
Driver is still responsible for vehicles actions.
- LadyCailin 4y ago
  Both “Autopilot” and “Full Self Driving” both heavily imply otherwise, even if you’re technically correct.
- wingineer 4y ago
  Which is what makes these misleadingly-marketed features so controversial…
- tw98521358 4y ago
  You can’t override erratic braking can you? There isn’t much the driver can do to stop that behavior
  - manicdee 4y ago
    Push the gear stalk up Twist the steering wheel against the direction the car is turning it Tap the brakes These all immediately drop out of AP. The driver also has the option of pressing down on the accelerator to make the car go faster and cancel AP’s anomalous braking. One situation I can think of is using Navigate on Autopilot and the car thinks the exit is much further along than it is, tries to take the “exit” which is actually a concrete wall, AEB kicks in due to imminent collision. But then why haven’t other Teslas had the same issue there?

rising-sky 4y ago

Your counter claim is apparently false based on the attempt at recreation in this linked video. The driver engage FSD while driving into the same section of the Bay Bridge and tunnel https://twitter.com/TeslaOwnersEBay/status/1614083624458125312?s=20 https://twitter.com/TeslaOwnersEBay/status/16140836244581253...

redox99 4y ago
That's the very tweet I'm referring to. Look at the screen and you'll see it's autopilot, not FSD (ignore what they say). All these names are confusing to be honest, so it's understandable that people mix them up.