I just turned off this 'feature' as it's more dangerous than it's worth.
Here's the thing - it has no issue accurately recognizing the state of traffic lights. I've never seen it get this wrong. However the confirmation requirement is the problem.
Today was the last straw. Whenever I approach a light I glance at the 'stop line' displayed on the screen to ensure it's green, and if it's not I confirm with the stalk. On this occasion I visually confirmed that the line was green (as there was a lead car in front of me). However right when I was about to enter the intersection the line switched to red and my car slammed on the brakes, almost causing an accident behind me. To be clear - the light was still green, and still showed as green on the display.
Having the line change from green to red is NOT ok (unless of course the light changes).
Tesla needs to pause their pursuit of L5 on the beta branch long enough to merge the new vision stack into the release branch and release it with existing feature parity, plus a few obvious next steps like removing this confirmation requirement for lights.
Thanks for letting me vent
Here's the thing - it has no issue accurately recognizing the state of traffic lights. I've never seen it get this wrong. However the confirmation requirement is the problem.
Today was the last straw. Whenever I approach a light I glance at the 'stop line' displayed on the screen to ensure it's green, and if it's not I confirm with the stalk. On this occasion I visually confirmed that the line was green (as there was a lead car in front of me). However right when I was about to enter the intersection the line switched to red and my car slammed on the brakes, almost causing an accident behind me. To be clear - the light was still green, and still showed as green on the display.
Having the line change from green to red is NOT ok (unless of course the light changes).
Tesla needs to pause their pursuit of L5 on the beta branch long enough to merge the new vision stack into the release branch and release it with existing feature parity, plus a few obvious next steps like removing this confirmation requirement for lights.
Thanks for letting me vent