One of the major problems I have had with FSD 12.3.6 is that is does not understand posted signage. Cases in point:
1. Traveling on "State Highway 35" in Wisconsin where the speed limit varies from 55MPH on open stretches to 40MPH around curves to 30MPH thru towns and as low as 20MPH in School Zones "When Children Are Present". So here we are on an open stretch traveling 55MPH when we pass a sign indicating that we are on State Hwy 35 - it's a black&white sign that does not resemble a speed limit sign but the car thinks it is the new speed limit and FSD all of a sudden decides to slow to 35 MPH at which point I either disengage or hit the accelerator to maintain 55MPH lest I get rear-ended. After several repeated instances of this behavior over a few miles, i decided to let it slow down and see if it figures out what the actual speed limit is. It seems that FSD notices the error and after about 5 seconds will, on its own, resume the posted speed. Thus, FSD and/or the car needs to understand exactly what kind of sign it is reading.
2. School Zones: FSD does not understand that it needs to own down in a school zone. This is a bit more complex task than just changing the speed of the car. My experience thru four different school zones is that FSD seems to ignore School Zone speed limits entirely and I had to disengage.
3. Speed Limit signs when going around sharp curves like Exit Ramps. For example, traveling 60MPH approaching a sharp curve that has signs posted to take the curve at 30MPH. FSD did not slow down and I had to disengage and took said curve at 42MPH. This has happened on multiple occasions so I rarely let FSD drive on roads with sharp curves (besides, I sound like my dad: "You're going too fast! Slow down!" And I'm 66 years old now)
4. Construction Zones: FSD sort of seems to know what a construction zone is but does not always seem to read or understand the "Construction Zone Speed Limit" signs -or- to resume the normal speed limit when it sees the "End Construction" sign.
5. Lane Indicator signs and perhaps road surface lane markings. Quite often the Navigation system seems to know which lane should be used in situations where there is, say, four lanes: a right turn only, a forward only, a forward-or-left, and a left turn only lane. FSD has often chosen the right-turn-only lane to go forward because there were cars in each of the lanes covering the lane markings. But there was a lane-indicator sign that FSD ignored. Again, FSD really needs to be able to read and understand all the various sorts of signs and put them into the immediate driving context.
6. Motoring down a freeway at 60MPH. Take an exit that, at the top of the ramp, has a single lane that simply continues onto the side street (there is no stop or yield sign and no merging with traffic on that road). There is a speed limit sign that reads "City-wide Speed Limit 25 unless otherwise posted". Then a few feet later there is a posted speed limit of 30MPH and FSD slows to 30MPH. A few feet after that, I have no idea why, FSD decides the speed limit is now 55MPH! Nope! I do not know what triggers this but it is repeatable. FSD should be more aware of what sort.of street it is on and take that context into consideration when it gets conflicting information.
7. This point isn't a posted sign issue but rather, the lack of a posted sign. Scenario: traveling on a road with a speed limit of 25MPH. Approaching an intersection where the only choice is to turn right onto the highway. Come to a stop sign, stop, turn right onto a highway that has a speed limit of 55MPH but that speed limit isn't posted when turning onto the highway so FSD creeps along at 25MPH on a 55MPH highway. FSD and/or the car Navigation system should know the speed limit for that highway.
1. Traveling on "State Highway 35" in Wisconsin where the speed limit varies from 55MPH on open stretches to 40MPH around curves to 30MPH thru towns and as low as 20MPH in School Zones "When Children Are Present". So here we are on an open stretch traveling 55MPH when we pass a sign indicating that we are on State Hwy 35 - it's a black&white sign that does not resemble a speed limit sign but the car thinks it is the new speed limit and FSD all of a sudden decides to slow to 35 MPH at which point I either disengage or hit the accelerator to maintain 55MPH lest I get rear-ended. After several repeated instances of this behavior over a few miles, i decided to let it slow down and see if it figures out what the actual speed limit is. It seems that FSD notices the error and after about 5 seconds will, on its own, resume the posted speed. Thus, FSD and/or the car needs to understand exactly what kind of sign it is reading.
2. School Zones: FSD does not understand that it needs to own down in a school zone. This is a bit more complex task than just changing the speed of the car. My experience thru four different school zones is that FSD seems to ignore School Zone speed limits entirely and I had to disengage.
3. Speed Limit signs when going around sharp curves like Exit Ramps. For example, traveling 60MPH approaching a sharp curve that has signs posted to take the curve at 30MPH. FSD did not slow down and I had to disengage and took said curve at 42MPH. This has happened on multiple occasions so I rarely let FSD drive on roads with sharp curves (besides, I sound like my dad: "You're going too fast! Slow down!" And I'm 66 years old now)
4. Construction Zones: FSD sort of seems to know what a construction zone is but does not always seem to read or understand the "Construction Zone Speed Limit" signs -or- to resume the normal speed limit when it sees the "End Construction" sign.
5. Lane Indicator signs and perhaps road surface lane markings. Quite often the Navigation system seems to know which lane should be used in situations where there is, say, four lanes: a right turn only, a forward only, a forward-or-left, and a left turn only lane. FSD has often chosen the right-turn-only lane to go forward because there were cars in each of the lanes covering the lane markings. But there was a lane-indicator sign that FSD ignored. Again, FSD really needs to be able to read and understand all the various sorts of signs and put them into the immediate driving context.
6. Motoring down a freeway at 60MPH. Take an exit that, at the top of the ramp, has a single lane that simply continues onto the side street (there is no stop or yield sign and no merging with traffic on that road). There is a speed limit sign that reads "City-wide Speed Limit 25 unless otherwise posted". Then a few feet later there is a posted speed limit of 30MPH and FSD slows to 30MPH. A few feet after that, I have no idea why, FSD decides the speed limit is now 55MPH! Nope! I do not know what triggers this but it is repeatable. FSD should be more aware of what sort.of street it is on and take that context into consideration when it gets conflicting information.
7. This point isn't a posted sign issue but rather, the lack of a posted sign. Scenario: traveling on a road with a speed limit of 25MPH. Approaching an intersection where the only choice is to turn right onto the highway. Come to a stop sign, stop, turn right onto a highway that has a speed limit of 55MPH but that speed limit isn't posted when turning onto the highway so FSD creeps along at 25MPH on a 55MPH highway. FSD and/or the car Navigation system should know the speed limit for that highway.
