As much as I like Mark, He’s got some explaining to do.
At 15:42 the center console is shown, and autopilot is disengaged before impact. It was also engaged at 39mph during the youtube cut, and he struck the wall at 42mph. (ie the car accelerated into the wall)
Mark then posted the ‘raw footage’ on twitter. This also shows autopilot disengage before impact, but shows it was engaged at 42mph. This was a seprate take.
/edit;
Youtube, the first frames showing Autopilot being enabled: 39mph
Twitter, the first frames showing autopilot being enabled: 42mph
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.
And another a couple seconds later:
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.
Here’s more from youtube, taken several seconds apart:
They are very very similar, but they do appear to be two different takes.
It would, but he explicitly says ‘without even a slight tap on the breaks’ in the youtube video.
Then:
Here is the raw footage of my Tesla going through the wall. Not sure why it disengages 17 frames before hitting the wall but my feet weren’t touching the brake or gas.
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 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.
As much as I like Mark, He’s got some explaining to do.
At 15:42 the center console is shown, and autopilot is disengaged before impact. It was also engaged at 39mph during the youtube cut, and he struck the wall at 42mph. (ie the car accelerated into the wall)
Mark then posted the ‘raw footage’ on twitter. This also shows autopilot disengage before impact, but shows it was engaged at 42mph. This was a seprate take.
/edit;
Youtube, the first frames showing Autopilot being enabled: 39mph
Twitter, the first frames showing autopilot being enabled: 42mph
https://www.motortrend.com/news/nhtsa-tesla-autopilot-investigation-shutoff-crash/
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.
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.
Here’s more from youtube, taken several seconds apart:
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?
He explicitly states that he didn’t tap the brakes.
It would, but he explicitly says ‘without even a slight tap on the breaks’ in the youtube video.
Then:
- Mark Rober
Twitter.
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 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.