I tried to use the right scroll wheel yesterday on my refresh with yoke, and it did nothing. I wasn't on the highway at the time, so not sure if that makes a difference?
Went out for another drive yesterday and the car completely came to a stop on side street with center marking because it thought there wasn’t enough room while a car came toward me. Flat-out hard brake to a stop. I can repeat this all day long on any road which is relatively narrow but still with plenty of space for a below average driver to navigate without a full-on stop (several feet on either side).
I was getting this in 10.69 and prior on ramps that it treated as local streets (vs switching to the legacy NOAP stack), it's probably only more prevalent now that the FSDB stack is used everywhere. In either case, I'd guess this is more "bad map data" than "not honoring local customs" as the on-ramp is arguably for getting up to speed and FSDB arguably should switch to a speed limit matching the road it merges into like it does when you change roads at any other intersection with good map data (which seems to be pretty sparse in my experience).
It doesn't recognize school zones yet. But most Beta people understand that and disengage while in school zone areas, driving manually until they're through the zone - then re-engage. Remember it's an L2 assist feature. It's currently designed for boring drives, and should be disengaged in many scenarios, like school zones, construction zones, police traffic control, etc.
I would click the "Disagree" emoji if it were not punitive as it is here on TMC.It doesn't recognize school zones yet. But most Beta people understand that and disengage while in school zone areas, driving manually until they're through the zone - then re-engage. Remember it's an L2 assist feature. It's currently designed for boring drives, and should be disengaged in many scenarios, like school zones, construction zones, police traffic control, etc.
I get your frustration, and can tell it's an important issue for you by your use of an appeal to emotion tactic, using "safety of our children". What monster wouldn't want to keep children safe? To date, as far as I can find researching it, FSD Beta has never struck a child. This may be because drivers are disengaging around school busses, zones, and parks where children are present.
For your own edification, there is a site that keeps track of deaths in Tesla accidents, and validates which ones were claimed to be on AP (including FSD Beta), and which ones were confirmed to be on AP/FSD. As a quick summary, since 2013, there have been 16 confirmed deaths on AP, out of 33 claimed.
Tesla Deaths: Digital record of Tesla crashes resulting in death
Tesla Deaths is a record of Tesla accidents that involved the death of a driver, occupant, cyclist, motorcyclist, or pedestrian.www.tesladeaths.com
I know none of this will sway your opinion, but I want to provide a balanced approach, and show the sky is not actually falling.
April 3rd redo - 12 mile round trip to CU, same intersection as yesterday
Conditions: Wet roads and over cast. Speed limit ranging from 20mph (School zone) to 45mph
FSDb Profile: Aggressive
Decided to head out during school bus hour; just to add stress to my day.... First and foremost - FSDb DOES NOT recognize flashing school zone 20 MPH speed limit signs, warnings or other. If you are not paying attention, you could easily fly through these zones at the non school time speeds listed for these roads - and, subject yourself to some steep fines 'ta boot. Similarly, children getting on and off of school buses remains unsafe - no recognition (by FSDb) of the school bus, flashing red lights and swing out school bus stop
Next, same behavior at this intersection as yesterday (replied to message above), but I was ready for it.... What I was not ready for was what happened shortly after completing the left turn... FSDb decided it didn't like the traffic in front of me (while moving at about 10mph) and jerked the wheel (Yoke) from my loose grip and jumped across the double yellow line into oncoming traffic lane. Good thing I was paying attention. Oh, and of course, the disengagement voice recording message didn't pop up this time. I forced one a few feet later by reengaging FSDb and then slamming on the brakes. Left them a choice message, I did.
I'm no longer going to use this version of FSDb - too unsafe to use in my area. No joke or exaggeration. Be safe out there, all!
Every downvote removes a positive up vote from your count. Minor, but annoying nonetheless. I can show you, if you would like, and then undo the downvote?
It responding to those things isn't a stated feature. So you would be recalling it for something that it isn't currently supposed to do.
No, it does not. They changed the calculation more than a year ago, so that it doesn't look at disgaree ratings at all.
No alerts, just following slow moving traffic - maybe it thought there was a passing lane to get around it (when there wasn't)? No idea - I was focused on not getting in an accident. Once crossed over, it recognized it F'd up and stopped abruptly.
Riddle me this then - why was a recall issued for other safety issues, like running red lights and stop signs? Because they are known to be illegal - same with the school bus and school speed zones.....
Are you sure? I've been here a long time and don't recall that change.
Because it responding to red lights and stop signs is a stated feature? (And is even on non-FSD Beta vehicles.) Even auto-response to speed limit changes is a stated feature.
Yes, I am sure.
Obeying the posted speed limit is also a stated feature and was one of the items previously recalled (i.e., slowing down when speed limit drops, etc.). You're really grasping for straws now...
My understanding is that the speed limit issue was resolved by removing the speed offset option, and reacting to speed changes more assertively. Previously when there was a speed limit drop, the car would coast and slow down very slowly, and now the deceleration curve is higher. The car also seems to react to speed limit signs when visualized instead of making the change at the sign itself. So if the speed limit is lower, the car will detect that and start slowing before the sign is reached.
Was it? I don't recall that. But are you saying that once something has been recalled, and fixed, that it can't ever be broken again?
