FSD not respecting set speed with scroll wheel, never hits the limit

[Crissa]

It'll consistently go under the set speed by a large amount unless you're on the freeway. 55 zones in my area I'll set up to 60 and fsd on my truck and m3 will try and do 45 unless I hit the throttle myself

Have you ever thought that 60 on those roads is less safe? ?

-Crissa

 

[17hertz]

I have the opposite problem . It goes 42 in a 35 and 75 on the freeway in a 65 lol

 

[usmatt2808]

I see all those quirks you all are mentioning. Thanks for confirming.

The right scroll wheel left-right clicks do nothing unlike in MY where it is distance from front car. There is also no Chill, Average and Assertive.

I am sure there will be several updates coming. Yes, I am complaining, but still super stoked that FSD on CT is here!
Thanks guys!
A

Unfortunately this behavior is not new - I have seen it on our ‘23 MX basically since leaving FSD 11.9. Despite numerous reports (from me at least) they seem unable/unwilling to fix this. And no, I don’t have it configured to let FSD determine the appropriate speed - as someone else mentioned when you turn that on adhering to the speed limit goes out the window regardless of any other settings. At this point a number of the FSD configuration parameters seem to be placebos. I love our MX & CT but come on - cruise control has been around over 50 years! You need to get the basics right THEN go for all the ‘wow’ features..

 

[cheno848]

Don't think it has anything to do with fsd "comfort." I live in a rural area and it stays 5-10 mph under set speed despite wide open empty roads. My Honda from 30 years ago would drive at the speed I told it to, this should too!

 

[DoberManPin-Sure]

It would be great if it honored our scroll wheel-set speed target (safety variables taken into consideration), but at least using the accelerator doesn't disable FSD . . . at least until 85.1 mph. I'm more interested in it honoring my speed reduction requests so I don't have to brake manually or turn off FSD only to re-engage it when it drops to the lower speed I'm looking for.

My only other issue--which is a modest one, as I love FSD--is 85 mph is too low for triggering a trip timeout in many of my driving circumstances. I understand they don't want it too high (or non-existent) from a potential safety and a liability perspective, but I don't like my trip timeouts. Despite several such timeouts--all thankfully on relatively short drives--I still have no "strikes," which is good.

I'm loving the Beast so much, I'm sad when I have to drive my TRX. First world problems, I know. I've contacted a broker to facilitate its sale . . . saving driveway space and insurance premiums.

 

[Outdoors]

Have you ever thought that 60 on those roads is less safe? ?

-Crissa

It just is how FSD is working right now. Has nothing to do with less safe or more safe. It's not optimized. It is even worse with no address in navigation.

Wonder if I could cook an egg on the FSD computer right now. It has it's thinking cap on.

All will be good in time. What I mean by that is this issue will be resolved quite shortly.

 

[Obie_fl]

I've gone back and forth between driving with ASSO on and off with this version. I've settled on leaving it on. There is definitely an issue with it coming up to speed, I just tap the accelerator. The downside is it doesn't slow down so you have to brake and disengage. It least it gets reported when it disengages.

Considering this is the first version on the CT I think it's pretty good. The other main fault I see is cutting left hand turns too sharp. Having said that I have had quite a few zero intervention trips with the exception of tapping the accelerator. Considering that a year ago I never had zero interventions with the S or Y we have come a long way.

Oh one big safety intervention thanks to MIlton we have lots of flashing reds right now, it tried to run through one yesterday.

Regarding following distance I thought that was no longer available on the cars FSD either but I haven't driven the Y much lately.

 

[BeastDrew]

I strongly feel the speed limit setting has significant room for UI optimization. rolling the scroll wheels up and down will make the up and down arrows blink on the screen, but it still says "MAX" and the speed doesn't change. the only input is via pressing on the accelerator, and that's only temporary. and it doesn't necessarily respect the offset set in settings.

It says "Max" only when you have Auto Set Speed turned on. Otherwise the max speed goes up or down with the scroll wheels (but as others noted, it hardly ever gets to the max speed you set)

 

[Jim Waller]

Pressing accelerator helps, as does manually indicating a lane change request when it won't pass. Seems like a bug, but these workarounds make it tolerable until they fix.

 

[heems]

12.5.5 does not have profile selection but it’s probably defaulting to chill or standard. In that vein this is what the engineerings are relaying (in 12.5.6) with respect to speed on highway:


12.5.6 E2E update from we robot event

 

[mdcoleman]

Being my first Tesla and EV, I probably don’t have much room to talk, but I will say I love the CT and have not once been disappointed after 4.5 months and 4k miles. Got the FSD update two weeks ago and wasn’t overly impressed initially, but with a recent update and what SEEMS like real-time learning, it has improved since the initial software. Surprisingly, the CT hit 70 in a 60 zone last weekend, but I do have it set to natural, and it was past 930p with far fewer cars on the road than we’re used to in the Seattle area. Glad to know Sir Elon applies actual hard data to his products and doesn’t accept the “5 is fine, 6 you’re mine” rule of the past when it comes to over-the-speed-limit driving.

All other things constant, even though the CT is a completely separate thing…I had a Model 3 Highland demo/loaner yesterday during my sail appliqué recall appointment, and the FSD on that was significantly more aggressive, realistic, and human-like. And by significant, I mean leaps and bounds. Where the CT hesitates or bows out of a lane change or similar “critical” decision, the M3 took the bull by the horns and went for it. Drastically more confident.

I know there are many, MANY more hours of info used and applied to the M3 system, which probably explains the delta between the two systems, but when I picked up the truck after service was complete, it was like stepping backwards in time. As of this time, I’ll chalk it up to Assertive mode as the differentiating factor in how the M3 drove versus the CT.

 

[Deleted member 27593]

Higher speeds lead to more accidents. If FSD is supposed to be safer than human drivers, we should be glad that it respects speed limits.

 

[Obie_fl]

Higher speeds lead to more accidents. If FSD is supposed to be safer than human drivers, we should be glad that it respects speed limits.

The problem is it often times doesn't get up to the speed limit, if you don't mind being tailgated or flipped off then it is fine.

 

[Obie_fl]

Being my first Tesla and EV, I probably don’t have much room to talk, but I will say I love the CT and have not once been disappointed after 4.5 months and 4k miles. Got the FSD update two weeks ago and wasn’t overly impressed initially, but with a recent update and what SEEMS like real-time learning, it has improved since the initial software. Surprisingly, the CT hit 70 in a 60 zone last weekend, but I do have it set to natural, and it was past 930p with far fewer cars on the road than we’re used to in the Seattle area. Glad to know Sir Elon applies actual hard data to his products and doesn’t accept the “5 is fine, 6 you’re mine” rule of the past when it comes to over-the-speed-limit driving.

All other things constant, even though the CT is a completely separate thing…I had a Model 3 Highland demo/loaner yesterday during my sail appliqué recall appointment, and the FSD on that was significantly more aggressive, realistic, and human-like. And by significant, I mean leaps and bounds. Where the CT hesitates or bows out of a lane change or similar “critical” decision, the M3 took the bull by the horns and went for it. Drastically more confident.

I know there are many, MANY more hours of info used and applied to the M3 system, which probably explains the delta between the two systems, but when I picked up the truck after service was complete, it was like stepping backwards in time. As of this time, I’ll chalk it up to Assertive mode as the differentiating factor in how the M3 drove versus the CT.

While there is no self learning on the vehicle there is definitely a "learning" period after new updates. I have witnessed it numerous times on my cars FSD updates. Not sure if the cameras are recalibrating or if it just takes a few drives for the variables to settle out. Many others have noted this too.

Strange that you found the M3 more aggressive maybe it was set in the old mad max mode. I find the truck a bit more aggressive then our model Y but it just might be the difference in settings and the lack of profiles on the CT.

 

[CTSoFL]

Hi Guys,
Not sure if someone else has seen this:

If I have the speed limit setup as driver adjustable via scroll wheel, it never reaches the set speed. If speed limit is say 55mph and I set the speed to 70mph, it just hovers around 64-65.

If I add some throttle then it goes up to 70mph and maintains 70mph for a few minutes and then drifts back.

Any thoughts?
Thanks!

We all drive like assholes and rarely obey all, even most, technical rules of the road.

FSD tends not to drive like an asshole and follows all the rules of the road.

When faced with this, especially since 99.999% have been driving as the former since day 0 of our Learner's Permit, the difference is jarring.

?‍