identifying seems to be one of the biggest problems and another is commitment after identifying. It seems to be recalculating and "deciding" what to do many times a second. While changing a plan can be beneficial, in many or most cases commitment is the key to success.
I’ve had several instances recently where FSD is trying to take a turn and sees a gap, starts to proceed the. Stops or hesitates then slowly starts again at a point where it will cause an accident or at least cause someone to slam on their brakes. In almost all of these cases it it would simply proceed as soon as it identified the gap in traffic it would be fine, it’s the hesitation that causes it to fail.
Agreed, FSD uses blinkers to mean "I WANT to do a lane change" instead of "I am GOING to do a lane change". While there are times I do the former (for example, in stop and go traffic when trying to get to an exit lane), I was taught (correctly, imho) that you should only ever do the latter.
I would argue that literally *all the time* requires active driver attention, when you are driving the car (which is what is going on here).
Just taking the best line.
I gonna have to go with my hopeful theory that they make it deliberately crappy to keep you alert. But it's crappy in an unsafe manner.
I think that is my frustration with it at the moment. There are so many annoying things that it does that just don't seem to get better, or improve by tiny/meaningless percentages.
My understanding is that NoA is for limited access freeways. I’ve been on several roads where the visualization changes from the blue line(s) to the red & yellow lines. These are generally 4+ lane divided highways. The smaller 2 lane roads are generally all on FSD beta. I presume Tesla uses mapping data for this distinction but I can’t say for certain.
So, in NJ, let's say that there's three classes of roads: Limited access highways (LAH), four lanes (2 each way) or bigger; Major local roads (MLR), with four lanes (2 each way) or bigger, stoplights, no stop signs, and probably Jersey Barriers down the middle; and local roads (LR), two lanes, one each way, stop lights, stop signs, and all. And maybe road markings down the middle and maybe not.
With FSD beta, my experience is that NOA is engaged when on a freeway, or other freeway-like highway as well as any highway outside of city limits with speed limit of 65 mph, or greater. I regularly drive on 2-lane rural highways with speed limits between 65 and 75 MPH. The car uses NOA on these roads. When entering a city limit, or when the speed limit drops below 65 (often at the same time), the car switches to FSD beta.
Ah that might be the distinction. On a separate trip, I did notice it switching to FSD Beta when it incorrectly detected a lower speed limit, but it seemed to handle driving fine above 65mph:
I don't think the system makes any distinction based on speed limits. Most of the interstates around Minneapolis have a speed limit of 55 or 60 but still use the AP stack rather than FSD.Ah that might be the distinction. On a separate trip, I did notice it switching to FSD Beta when it incorrectly detected a lower speed limit, but it seemed to handle driving fine above 65mph:
To be clear, the CA highways through the forests did have 65mph speed limit with T-intersection stop signs for the connecting smaller road while staying on NoA stack although limited to 5mph over the speed limit.
It's simply how the roads and road segments are classified in the map database.
teslamotorsclub.com
