karbomusic
Member
One simply cannot deliver some new functionality as beta that totally interferes creating very unsafe scenarios EVEN WITH THE NEW FUNCTIONALITY TURNED OFF (or to that point, even autosteer and everything underneath it).
Extremely bad QA and regression testing on their part.
Just turning off FCW and/or AEB avoids the issue (that's the way to truly turn it off) - That said, too much reliance on automated testing I think. They should have done this in rings. I'd think if they gave to the "zero ring" of a few employees and long-time testers for a couple days, they would have found this.
Also, no one can predict/affect the severity of a bug/regression during beta testing. The best solution would be humans testing at least some before rolling out to the entire beta community. Not sure if they did that and/or if areas that were already being heavily beta tested have less issues due to the fact so much testing has occurred there already, making the issue less likely in those locations - no idea, total guessing on my part.