Definitely poor intersection design though as well. I've seen lights with extensions around the bulb to prevent them from being seen from obtuse angles, I wonder why these lights don't have those? Especially at night it would completely block your vision of the light(s) that don't apply to your road.
But the serious issue with the FSD doesn't become moot because of this.
Plus, if you see both red and green lights, your first instinct as a driver (human or not) should be to stop and re-examine more closely, not run through it.
I would hope a driver using FSD or any other system like it would be alert/aware to intervene...but for this video, it looks like they were trying to see how the car would react.
This entirely feels like a manufactured scenario since they simply did not act like a informed driver, and decided to freak out.
If none of this is true, than they are incredibly shitty drivers that were not paying attention to what was happening and let the car cruise through a red light. The exact same scenario would have occurred with a standard 1990 era cruise control system.
"They're a bad person so this must be fake", or maybe they're a bad person which is exactly why they thought doing something like this is okay
Look I'm all for knowing this information, that something like this can happen. But to be clear, in no way do I condone how it was done. This seems reckless for the sake of clicks.
There is an intersection in Houston that is one of the most dangerous in the USA that kills a dozen people a year due to poor design and planning from TxDOT. There are probably hundreds of intersections like this around the country that will need to be fixed.
If I go paint road lines into a wall painted like a tunnel, are the drivers who hit the tunnel wall responsible, or is it me who painted the road lines?
The white lines of the two adjacent lanes made it look like there was a well-defined lane there, with the barrier right in the center.
Here's a pretty good picture of what it looked like then:
https://www.autopilotreview.com/wp-content/uploads/2019/03/m...
You can see there is no hatching to make it obvious it was a non-drivable area.
I would have expected something like this might have made a difference:
https://driveractive.com/Assets/photos/rm25.png
(that said, why didn't radar help?)
Also, there's a huge yellow and black chevron block visible in that picture that any human driver paying attention would have seen and easily avoided. Crosshatching is unnecessary if you're paying the least bit of attention to what's in front of you. What was the software's issue here?
It is absolutely a problem with the Tesla software that it wasn't able to parse that area properly. Doesn't necessarily mean the human driver wasn't at fault.
I do think that it had already stopped at least one, maybe multiple crashes since it has been last replaced.
The discussion here though is about visibility, and the attenuator would have been quite obvious there.
Page 2 (which is actually the 22nd page of the pdf) shows an image of the pre-crash state of the attenuator. It is present, but non-operational due to a previous crash. While that crash affected it's usefulness, it's visibility is only marginally reduced.