Less control on FSD v14

[Djinndjinn]

That offset is for your speed limit warning. Lane assist is also in that menu and it's irrelevant when FSD is active. Tesla stated there is no user controls on Speed Limit outside of the profiles and that's pretty easily tested. The offset doesn't work on FSD.

Duh. I‘m a dufus . Figured that out when I set the offset to zero (thinking it might be additive to the speed profile) and my CT just kept going ‘ding ding ding …”.

Sponsored

 

[Coolhandz]

Got my update last week I think and have about 1,000 miles on it so far. Been reading through these posts and it seems like a lot of people have differing opinions on this update. For me, I love it. It is so nice to click on FSD while parked in the garage and have it take me the 30 miles to work without any interventions aside from parking in the parking lot at work. I think I figured that out this morning by saving my parking spot as a favorite. We'll test it out tomorrow to see how it goes.

I see a lot of complaints on speed adjustments no longer being present. I agree to a certain extent, but I speed. I always have. So for me, keeping it in Mad Max mode has been awesome. I would hate driving down an unmarked country road and it would stay 35 when the limit was 55. I'd scroll the wheel up to 62, nothing would happen, and then I'd have to nudge it up and hopefully it would stay. There are still some obvious kinks with this as it often does not read or know the correct speed limits and so it will do 62 in a 35 thinking the limit is 45 or 55. I haven't ever corrected it because I saw no need to.

One thing that i have noticed is the extreme sensitivity to stuff in the road. Namely skid marks or blacks lines where road crews have filled in cracks. FSD seems to think these are objects in the road and will swerve around them, sometimes aggressively. Yesterday it slowed down and went around a group of turkeys which was neat. It also likes to give extra room for pedestrians walking on the shoulder or vehicles stopped on the shoulder which has been really nice. I also noticed it was a bit more aggressive in using the shoulder to squeeze into turn lanes when the line is long to go straight.

My only other gripe is that sometimes FSD seems to think about changing lanes or when it is going to turn. Rather than peeking around the car in front, it will jerk the steering back forth rapidly as if it can't make up its' (AI) mind. Can be a bit annoying. It will also sometimes think an entrance ramp is a lane on the highway and move right to pass only to find out the lane is ending. It will do this sometimes for turning lanes too and then suddenly jerk back in the left lane.

All-in-all I think these are minor things that can be worked out more easily. I think the next couple of incremental updates will iron out these bugs.

 

[TexasRaider]

Mine has been going 15 under the speed limit with no traffic around. So, I can’t use it for long distances or else it’ll impact my arrival times.

 

[Sjohnson20]

speeds have been great for me on standard. when I want to go faster I move to hurry or mad max.

 

[Djinndjinn]

In addition to the jerkiness (especially on starting, but also with decision-making), its understanding of the actual visual speed limit has taken a step back if that’s even possible.

Can someone explain “GIS” and why the CT seems incapable of reading and interpreting road signs? It seems to be using a database instead of actually reading the sign that’s in front of Its cameras. If it was able to read the sign, then its speed limit understanding would be as accurate as I would be as a driver. And this info could be used to layer the different speed modes upon a common source of truth.

Crissa in a previous post mentioned something about it can’t read speed limit signs because of a patent issue with Mobile Eye that is set to expire. ?

The various speed profiles would actually work very well if they were paired against the correct speed limit.

 

[SCTesla]

In addition to the jerkiness (especially on starting, but also with decision-making), its understanding of the actual visual speed limit has taken a step back if that’s even possible.

Can someone explain “GIS” and why the CT seems incapable of reading and interpreting road signs? It seems to be using a database instead of actually reading the sign that’s in front of Its cameras. If it was able to read the sign, then its speed limit understanding would be as accurate as I would be as a driver. And this info could be used to layer the different speed modes upon a common source of truth.

Crissa in a previous post mentioned something about it can’t read speed limit signs because of a patent issue with Mobile Eye that is set to expire. ?

The various speed profiles would actually work very well if they were paired against the correct speed limit.

FSD does read Speed Limit signs. Tesla has stated this as of 2020 and there's proof. Sometimes it reads the wrong signs (minimum speed) and the sign has to be a certain size and position for it to populate, but there are a ton of videos online of FSD reading signs that people even made up or altered signs...even signs on the back of pick up trucks.

The issues are, there aren't always signs, sometimes they are obscured by other vehicles or obstacles, and sometimes the conditions aren't right (rain, fog, reflection). When there's not a sign present, FSD reverts to mapping. The signs in the maps are populated by the fleet first then by Google/Open Maps. So the priority for FSD is visualization, then fleet produced, then third-party.

 

[65SoYoLO]

Today, I went by the same school zones speed limit sign twice within 15 minutes of each trip. The first time it did not read the sign, the second time it read the sign.
Why?

 

[Djinndjinn]

FSD does read Speed Limit signs. Tesla has stated this as of 2020 and there's proof. Sometimes it reads the wrong signs (minimum speed) and the sign has to be a certain size and position for it to populate, but there are a ton of videos online of FSD reading signs that people even made up or altered signs...even signs on the back of pick up trucks.

The issues are, there aren't always signs, sometimes they are obscured by other vehicles or obstacles, and sometimes the conditions aren't right (rain, fog, reflection). When there's not a sign present, FSD reverts to mapping. The signs in the maps are populated by the fleet first then by Google/Open Maps. So the priority for FSD is visualization, then fleet produced, then third-party.

Well I don’t have data, just my observations, but the visualization first does not seem to be the case. Tons of examples where I’m driving by a traditional speed sign, with full view, and it misses it. So there must be some more complicated algorithm than simply “I see it, or if I don’t see it I use a database”.

But what we humans are held accountable for legally are speed limit signs that we visually see. And in the absence of any speed limit sign for some distance, then according to the laws of that type of highway for that particular state.

So it would seem to me that the visualization should be the top priority, and that doesn’t appear to be the case. And if you can’t get the visual speed limit sign correct, that everything afterwards is completely screwed up regardless of what speed protocol is chosen.

I have driven Teslas since 2012, and some of my earlier model S’s were far better at reading speed signs.

 

[REM]

What is a real head scratcher is whether the company is expecting that 1. Average people will understand this, and/or 2. Expecting that anyone besides die-hard fans will have the patience to tolerate that especially now. Like i said, Most people just want set it and forget it when it comes to their cars. I guess statistically it doesnt matter because higher take rate and usage rate just means faster progression toward their goal. Less interaction means everyone juts gets it as it is, and deals with its limitations for longer. Idk either way tesla has basically sealed their guaranteed progression and likely the throne regarding AI powered self driving, even if their methods basically mean using the general population as test pilots.

Brother, we are the beta testers so that FSD unsupervised can make it to the mass market lol. This will not happen until we help pull the training NN past the march of 9's

 

[JCERRN]

Brother, we are the beta testers so that FSD unsupervised can make it to the mass market lol. This will not happen until we help pull the training NN past the march of 9's

I suppose that is true, by buying it your are also opting in as a beta tester. Kinda feels that way when buying a tesla in general, especially an early generation model (like CT).

god speed.

 

[TexasRaider]

Mine has been going 15 under the speed limit with no traffic around. So, I can’t use it for long distances or else it’ll impact my arrival times.

Thankfully this has changed with v14. Drove a few hundred miles today (14.1.7). So much better and fluid. However, the CT is swerving for potential potholes while going 75MPH.. tough feeling.

 

[Ed243]

Glad it can now keep its speed constant during Interstate travel. It was annoying repeatedly pressing or holding down the accelerator to travel at max speed with no other traffic around. Unfortunately the dry wipes on the windshield have gotten more frequent. Wipers off!

 

[AlmostHuman]

Over 2,000 on FSD 14.1.7 over four days with an entire day in some crazy heavy rain. Drive drove 98% of the miles including parking at some of the chargers. FSD version 14 completely changes the vehicle.

 

[georgek43]

Are you using sloth mode? I don't have a problem with it speeding in my area; even when its displaying the incorrect speed limit.

So it’s been a month and a half on FSD14. Highway performance is good with traffic, but speed management is poor without surrounding traffic. Too fast, too slow, rarely just right. It’s frustrating and definitely a downgrade from being able to set a precise speed.

I want driver speed control back.

I’m an actual owner. Not an influencer.

 

[CyberGus]

Yesterday I noticed a blue halo around the speed-limit indicator, which was showing 55MPH while on a 75MPH highway. I believe vision had captured the slower limit from a sign on the parallel frontage road.

(It switched back to 75 before I was able to snap a photo; the blue halo disappeared shortly thereafter.)

Note that it didn't actually slow down, which suggests that there's some logic to handle discrepancies between mapping data and real-world signage. I think it would very helpful if it displayed greater detail, showing the speed from the Map, from Vision, and the resulting target based on your preferences.

Currently, when the wrong speed is chosen, it's difficult to discern why.

Sponsored