Was there a process in place to prevent the deployment that caused this?
No: blame the higher up
Yes: blame the dev that didn’t follow process
Of course there are other intricacies, like if they did follow a process and perform testing, and this still occurred, but in general…
I’ll bet you’re right that it’s the lights, but I don’t know about “overload” of anything.
The problem with camera vision (vs human vision or LiDAR) is poor definition range. This means that pointing a light at it, like happens with emergency vehicle lights, can cause it to dim the whole image to compensate and then not see the vehicles. Same thing as when you take a backlit photo and can’t see the people.
I agree, and what I said is not trying to exonerate the car companies but is pointing out the rage-bait of the news media.
“Volvo recalls ALL…” (emphasis mine), is meant to incite worry and or rage, while something like this would be truer to the details and relevance to consumers: “Volvo software bug may obscure speedometer. X number of model affected/reported. OTA fix released.”
OTA “recall.” Sucks that there was a bug like this, but the headlines try to make these out to be bigger than they are.
Physical or otherwise “bring to the dealer” recalls are bigger news because direct owner action needs to be done, often meaning their car is unavailable for some period of time. OTA just means people will drive their car like normal and it’ll be passively fixed, which is hardly news-worthy.
The screenshot doesn’t show preceding flow to reach it, but I did miss the “requires windows hello to enable” bit, which does suggest that wherever it is, it would have to be opt-in.
“The ability to disable the…feature during the setup process…” does not mean opt in, that means opt out.
Knowing windows setup, you need to click customize during the setup process and then go through several setup pages before you’re presented this option (or have to dig into additional/advanced settings to find it).
Most people won’t do this, won’t know how to do this, or will receive the pc with the initial setup complete and won’t know if this is on or off.
Take Tesla for whatever you will, but there’s crazy conflict of interest behind the dawn project/Dan o’dowd attacking this.
“Green Hills also develops automotive software—it's about 40 percent of the company's business, O'Dowd said—and is a software supplier for the 2022 BMW iX EV crossover. This has caused O'Dowd critics and Tesla fans to call out The Dawn Project's conflict of interest and question the organization's motives.”
https://www.motortrend.com/features/tesla-full-self-driving-ban-attempt-elon-musk-dan-odowd/
Did the car try to stop and fail to do so in time due to the speeding, or did the car not try despite expected collision detection behavior?
Going off of OP's quote, the jury found the driver responsible but Tesla is found liable, which is pretty confusing. It might make some sense if expected autopilot functionality despite the drivers foot being on the pedal didn't work.