FSD 14.2.2.1 Still Reading Speed Signs Wrong

[Hamchuck]

There should be a way to manually adjust the speed limit indicated. I just came back from a 3000+ mile roadtrip and was fighting the issue the whole way. I run Waze to look for wrecks/cops so I am sure about the speed limits and how often Tesla gets it wrong. Needing to put FSD in Mad Max just so it goes 75 in a 75 when FSD thinks the limit is still 55, or chill or sloth when FSD don’t catch a reduced speed is a work around I don’t enjoy doing.

Sponsored

 

[txtravwill]

I feel like mine still doesn't even read them, just drives by and ignores most changes in our area.

 

[Dvldogg05]

Same problem here. So many times it does not update. Shows 35mph in a 55.

 

[photon]

A main road by my house has a 35 MPH limit and goes by a middle school. The 25 MPH when children are present is posted. The Cybertruck sets the speed limit to 20 the moment it sees that sign no matter the time of day. So strange

 

[drrussellhogue]

Tesla’s AP used vision starting in 2016 vision. Vision worked until FSD 14x but appears to be gone at least for now.

No it didn’t and doesn’t. But ok. Once it’s using vision more, the problem will go away.

You can watch it adhere to incorrect gps speeds all the time. You can also run multiple gps apps to confirm it’s the case (as I do). When Apple and Tesl, Google and Tesla, all show incorrect speed limits, it’s not because Tesla randomly missed the sign…it’s because it was using gps data.

 

[Limes2]

Hopefully in the future, it’ll be able to comprehend school holiday schedules so it won’t slow to 20 MPH in school zones when school isn’t in / when it isn’t applicable.

Hoping this is part of the upcoming "reasoning" update in v14.3. It will also need to understand calendar & time specific parking signs.

 

[SCTesla]

They aren’t reading the signs, right? They are using gps map data. If they start using vision to override gps map data then it would be better. Hopefully that’s coming.

No. Camera vision/sign reading is priority, then map data.

 

[georgek43]

It has to use vision as a key input if we’re ever going to achieve unsupervised FSD. Construction zones, temporary restrictions etc. Vision in earlier iterations was sketchy because there are so many “exceptions”. For example, in Virginia there are assumed legal speed limits depending on the road nature. It’s 55 on normal rural roads with a double center line. However that’s often not posted. When entering a town the reduced (often 25) limit is posted. When leaving a town or restricted zone the signs say “End 25 MPH restriction”. AP and older FSD versions read this as the current speed limit, while the reality is 55, although not posted as such. We humans know this and drive appropriately, but the computer would need more information than is evident visually. With the 14.x switch to prioritizing map speed data this is “solved” but there are a host of data errors, and of course no situational speed limit awareness, at least for now.

Yes, “we humans know this and drive appropriately”. This is why we need an easy way to correct the spread limit errors- and we had that with the scroll wheel until FSD14. The self driving is amazing- the speed management is terrible, frustrating and spoils the benefits of FSD14. Speed management is really difficult for an AI, for all the reasons discussed in these posts, but pretty simple for a human driver with a more extensive awareness of both subtle and complex cues. Just bring back the scroll wheel max speed override and FSD will be much better.

 

[SCTesla]

Hoping this is part of the upcoming "reasoning" update in v14.3. It will also need to understand calendar & time specific parking signs.

According to Ashok some of that reasoning is in 14.2.2.2 and more will come in Q1 with future 14.2 updates.

1. I don't see much difference in 14.2.2.2 vs. 14.1.X to get excited.
2. That means we won't get 14.3 in Q1.

 

[georgek43]

There should be a way to manually adjust the speed limit indicated. I just came back from a 3000+ mile roadtrip and was fighting the issue the whole way. I run Waze to look for wrecks/cops so I am sure about the speed limits and how often Tesla gets it wrong. Needing to put FSD in Mad Max just so it goes 75 in a 75 when FSD thinks the limit is still 55, or chill or sloth when FSD don’t catch a reduced speed is a work around I don’t enjoy doing.

There should be a way to manually adjust the speed limit indicated. I just came back from a 3000+ mile roadtrip and was fighting the issue the whole way. I run Waze to look for wrecks/cops so I am sure about the speed limits and how often Tesla gets it wrong. Needing to put FSD in Mad Max just so it goes 75 in a 75 when FSD thinks the limit is still 55, or chill or sloth when FSD don’t catch a reduced speed is a work around I don’t enjoy doing.

we had a simple way to adjust speed with the scroll wheel before FSD14 took it away. I want it back. Obviously the vehicle cannot manage speed correctly in far too many scenarios.

 

[Gaximus]

Definitely not using gpa map data consistently if at all. I can watch the signs appear on the side of the road and it changes. If it were using GPS data, this problem wouldn't happen.

My older Model S used GPS, and it has its own problems. It doesn’t take into account road constructions. Or new roads. I drove into a new neighborhood off a 60 mile an hour highway, and it thought it was still 60, even with a sign right there. Eventually it’ll use GPS with vision, once it gets better at reading signs, it’ll know what the speed limit is when you get on a road, before any signs, then update when that changes.
Reading signs and understanding them is a really hard problem, there is no standard for speed limit signs with special instructions like above. There are entire LLMs dedicated to just language recognition and meaning, we don’t want half of the FSD compute power going to reading signs. I think the way it should work, is read the sign, if there are extra instructions, send it to Tesla servers to be processed there(some guy in India) and then send it back and update the GPS.

Sponsored