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


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. 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.
  9. Check for duplicates before posting, duplicates may be removed
  10. 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
[โ€“] billwashere@lemmy.world 3 points 8 hours ago* (last edited 8 hours ago) (1 children)

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.

[โ€“] LeninOnAPrayer@lemm.ee 2 points 7 hours ago* (last edited 7 hours ago)

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.