this post was submitted on 17 Mar 2025
391 points (96.9% liked)
Technology
66687 readers
4595 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
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
If you watch the footage it's clearly the same take.
From the twitter footage:
This is from the first couple frames showing that Autopilot is enabled, just as the blue lines appeared on screen: 42mph displayed on the center console.
collapsed inline media
collapsed inline media
And from the youtube footage:
Again, from the first couple frames as Autopilot is enabled, just as the blue lines appear: 39mph displayed on the center console.
collapsed inline media
Here's more from youtube, taken several seconds apart:
collapsed inline media
collapsed inline media
They are very very similar, but they do appear to be two different takes.
He stated in the video he tapped the brakes. Doesn’t that disengage auto pilot?
It would, but he explicitly says 'without even a slight tap on the breaks' in the youtube video.
Then:
- Mark Rober
Twitter.
He did state that he hit the brakes. Just on the fog one, not the wall. 🤷
But the fact that FSD disengages 17 frames before the crash also implies the software, along with the car, crashed 😂 I’d love to see the logs. I imagine the software got real confused real quick.
This is likely what happened. The software hit an invalid state that defaulted to disengaging the autopilot feature. Likely hit an impossible state as the camera could no longer piece the "wall" parts of the road with the actual road as it got too close.
Likely an error condition occured that would happen in the same way if an object suddenly covered the camera while driving. It would be even more concerning if the autopilot DIDN'T disengage at that point.
The software likely disengaged because the wall was so close it could not function. It would be the same as if an object suddenly covered up the camera while you were driving. It would turn off the autopilot/FSD or whatever they call it. (At least I hope it would)
He explicitly states that he didn't tap the brakes.