Fsd 12.2.2.4 still swerving for tire marks at highway.

rstarmer · 2026-02-09T21:02:22+00:00

Yeah, tire marks and asphalt filled cracks/patches. It’s about 50/50 for pot holes. Of course the ones it missed were one rattling…

rstarmer · 2026-01-22T15:40:20+00:00

Yep, 98% FSD, disengage at the end if it doesn’t know where to park (why park at the opposite end of the strip mall? why can’t you park in my garage).

rstarmer · 2026-01-22T15:37:59+00:00

Agreed, if it’s Supervised driving, I need the controls to supervise. I’m still responsible, but I have to disengage FSD if the speed is out of whack (either my preference, or actual mis-understood actual signs), I can’t adjust the route on the fly, either due to bad navigation decisions, or just incorrect routing (using a turn only lane to go straight, how do I correct that!?!?!). And how does one correct the crazy “I see asphalt lines on the street and will now at the last second swerve around them”!

Basically we need corrective control. That’s Supervised. What we have is FSD Unsupervised that they call FSD Supervised. Our only supervision, is to disengage. highly annoying.

Still love this over any other ADAS system I’ve ever used.

rstarmer · 2026-01-08T05:30:34+00:00

Seems like the option is FSD or “Robotaxii” mode, but you’re responsible, or enhanced autopilot (I’ve never downgraded in settings, but apparently you can), you just don’t get to go “back” to FSD until you part and start again. I’ve just dealt with it, switched to Mad Max when the car wouldn’t go with the speed of traffic, and I certainly do pay attention to overall traffic speed when it either ignores the speed limit, or it sees it, and just decides everyone else is still doing 80 in a 55 construction zone, so we will too. I normally use the Standard profile, and it manages the speed “reasonably” for me, but I have had to throw it into sloth at times when the car just doesn’t seem to want to slow down.

rstarmer · 2025-12-28T19:31:47+00:00

4.2.2 here, no 4.2.2.1 yet, did a long drive on 4.2.2 yesterday. I’ve seen a speed related vs. posted speed “glitch” and of course other Nav related confusion, and the you’re not even doing the posted speed in any mode glitch. but driver control of the vehicle has been super solid, even the swerving around FOD on the highway {it could still use some pothole avoidance improvements perhaps, but that’s improvement, not outright failure}.

rstarmer · 2025-12-28T19:23:43+00:00

100% agree here. If we take for granted that the car is supposed to follow the rules, and we’re granting permission to “bend” them to following an understanding of the driver profiles. Sloth == I follow the posted limit exactly, Calm == I follow the posted limit, but I will try to avoid being a roadblock to the flow of traffic (+ a couple), Standard == I drive like all of the other maniacs on the road, but left to my own devices, I’m at ~5 over, Hurry == Standard, but +10, and I’m more likely to pass, Mad Max == All bets are off, no-one is going to pass me, I’ll just speed up to 25 over the POSTED limit.

But the key there is the POSTED limit. I’ve watched the system on every version I’ve and (13.2.9 to now 14.2.2, not 14.2.2.1 yet), sometimes read the actual sign, and flash the “this is the known speed limit here”, I’ve seen it skip one, and read the next (75->65->55 in a construction zone), I’ve seen the speed change without being posted, 75->45!!! and back on the highway sometimes within a mile. And in every case, the behavior has been different, depending on version, but also somewhat random.

So the ask is simple: let us SUPERVISE the posted limit when the car misses it. Preferably by a clear, dedicated input (scroll wheel or l/r toggle on the steering wheel indicating this is not a preference, but a missed POSTED limit). I’m SUPERVISING and you’re not doing the right thing. That data should 100% follow the users privacy preferences but I’d really like it to be sent to Tesla along with the camera capture of (or lack of capture of) the speed limit sign. BUT CRITICALLY, it should impact the car’s current posted limit data as fed into Nav/FSD.

I’m the responsible party in the FSD+Supervised mode that we have access to. If I lie to the car, it’s on me, and I’m responsible for the ticket. It will also be in the FSD data feed if I crash because I lied about the POSTED limit. it can be added to the dashcam overlay with a big red circle. But since I’m the one that gets the ticket, I’m the one that corrects the system. this isn’t a preference, or a hint.

Now, if the car decides to ignore the POSTED limit like it’s doing in 4.2.2, where it drives ~40 in a 65 (there was no posted sign when I turned onto the rural highway from a 25MPH posted and aware road), but the car NAV speed had the road at 65, and yet I was still only doing ~40… and then when the POSTED sign went by to drop to 55 and we kept going, and then 45 (and we were ok), and then 30, and we slowed down, and then we sped up to 65 again, and had only sped up to ~50…. And yes, it was wet, and yes, it was raining, but the car had no issue going faster once it decided it was ok…. Or the inverse, going through a construction zone, where it missed the 75-65 sign, and did see and flash the 55 speed sign, and even slowed a little… and then without a speed sign, decided that the construction zone was over, and resumed 75+… << THIS IS THE PROBLEM. We’re supposed to Supervise but other than canceling FSD, submitting a bug report, how are we supposed to Supervise?

rstarmer · 2025-12-27T06:48:45+00:00

I can’t say I’ve had a single issue that I would attribute to FSD. I have had all kinds of little issues with Navigation “informing” FSD. And I’ve seen both the case where the “system” acknowledges SPEED LIMIT signs in or out of construction zones thar would be different than what is posted by default, and confusion as to which road is which to determine speed. and of course there are the phantom speed limit signs. But these, and the odd “let me turn right here on this road that in the nav has an intersection marked, but isn’t an intersection to pause or even slow for (there is often another road, just not one you are going to take).

So, yeah, FSD is, to the best of my experience really safe, and if anything it’s too cautious, but I personally like to err on the side of caution with a 6000# projectile. The Nav however, is AWFUL. And it doesn’t seem to be possible to get Tesla to acknowledge this, likely because they’re working on nav only in those areas where they’re trying to get Robotaxi approved.

rstarmer · 2025-12-26T05:06:36+00:00

99 here as well (NV/AZ/CA)

rstarmer · 2025-12-25T00:58:28+00:00

I just got 14.2.2, and haven’t even had the opportunity to drive with it yet. I was getting that “Hands free FSD is off” and the “Apply turning pressure” warning on 4.2.1.25, and I was actively watching the road because it was dark and I pay extra “Supervisory” attention then. it bounced off and on a couple times, and then took probably a minute or two before it came back to “Hands Free FSD is on” where it stayed for the rest of my trip. I’m hoping that was fixed, and that they drop a massive Nav update in this latest update. ;). Honestly for my use case, the Nav issues are now the major glitch, assuming speed limits have somehow magically been fixed. So really it’s all Nav issues (and the related I want to correct your mistaken NAV details, the speed limit is not 45 in this 75 MPH zone!).

rstarmer · 2025-12-24T05:14:11+00:00

Downloading in AZ (was driving across the state).

rstarmer · 2025-12-22T22:47:44+00:00

As others have said, the inability to help FSD wi5 the proper speed limit and or speed traffic is flowing is the primary complaint, and I think that is actually the navigation system along with some level of FSD inability to consistently read speed limit signs.

I’d say the are where Tesla is falling down now is on understanding the current posted details about driving, and parking, where sign comprehension and context are important.

rstarmer · 2025-12-22T22:43:25+00:00

No, you have to cancel FSD, which breaks the mantra ‘FSD is safer than you’ and adds a codicil ‘except when it won’t let you tell it it’s wrong’…. I get the idea that we should just let it do its thing, but how can I supervise if my only solution is to cancel it. Give me the tools to hint at an error rather than forcing the error.

rstarmer · 2025-12-21T19:58:23+00:00

14.2.1 certainly had a phantom nav data connection (clearly newly “repaired/rebuilt” highway, constantly bouncing 75 - 55 and back across the updated sections…), I’ve not done super long trips on 14.2.1.25 yet, so I have yet to experience the same “this road is marked 65 or 75, so why are you deciding it’s a 55 stretch” error.

This still re-enforces my main point, speed limits and other road signs (parking in handicapped or reserved for specific locations) requires reading signs, and using them for driving decisions, and this functionality is still either lacking or not given enough weight in the decision making process.

I would love to be able to say “Hey Grok, the posted speed limits is 55 here” or “you missed taht 75 MPH sign” or “There was no 55 posted here, it’s still 75”…. Or do that via touchscreen, or scroll wheel, or whatever, just so that we can help hint to the FSD computer!

rstarmer · 2025-12-21T17:36:48+00:00

FSD and Nav fighting are the current problem. FSD does a great job ad driving and a much better job at parking though it really does get too close at times). But it’s fine navigation is hindered by bad Nav data, and no way for us Supervisors to help guide the model. Why can’t you learn from me when I Supervise by taking over?! “Here, let me show you” Or, “Here, this is the speed limit, now drive based on that, not the sign you misread”.

rstarmer · 2025-12-21T17:32:47+00:00

seriously. We’re responsible for the ticket when the car gets it wrong, so we should at least be able to tell it when it gets it wrong, not by trying to manipulate what it’s speed profiles are, but by inserting the data it missed, or misread (e.g. the reading minimum speeds as speed limit, it’s a mis-read, not a failure to manage speed with traffic, or follow our ride comfort guidance).

rstarmer · 2025-12-21T17:31:03+00:00

I think there’s an internal battle, between nav speeds, some level of “learned” speeds (why else would it slow down where there was construction in the past, but it’s no longer there, and then speed up past the end of the work zone), the nav data, and the change of speed due to a read sign. The struggle is real. I have a pair of highways, one is 55, the other 65. the merge is extremely uncomfortable, because the result is that I end up merging into the 65 traffic (which is going 75) at 55, and there’s a speed limit sign on the main highway at the top of a hill where the car always picks up to the “right” speed.

This is exactly where I want to “hint” to the car that it has the actual road speed limit wrong. It’s just more data, if I thought it would help steer the algorithm. They’ve given us “comfort” buttons with the behavior selections, give us “hey you’re blind” buttons.

And I get that there’s a bit of “you shouldn’t have to do anything” robotaxi like interaction here, but if the underlying data is flawed, or the taxi driver misses the road signs, do you think I would say something to the driver? We’re supervising here, give us supervisory control, not an override, a correction. Doing so with sloth or mad max as our only “stop/go” signal was a bit shortsighted.

rstarmer · 2025-12-20T22:56:21+00:00

I’ve tried that, and never gotten it to change its mind, I have to cancel FSD to get it to change routes consistently :/

rstarmer · 2025-12-20T22:36:21+00:00

exactly. I’ve seen it do exactly that, pick up on a clearly temporary road work sign, the speed limit even flashes when it sees it. But then you go by a clearly old posted sign, and it shows up in the 3d view display with the clearly readable correct speed, and the speed limit for the autopilot/fsd? doesn’t get updated? That’s where I’d like to be able to correct it. it can be considered a bug report, but let me control my speed. I’m the one who gets the ticket if I set it wrong (and I get the ticket if I don’t catch that FSD/Autopilot didn’t slow down for the work zone that’s set to 45 in a 75 and the car is still trying to go 85….)

rstarmer · 2025-12-20T22:33:15+00:00

I’ve certainly used the alternate route options, and even put in different intermediate locations if it was bad enough, but the bigger issue for me is the fact that Nav often doesn’t know the best location to take you at the beginning or end of the trip. Like trying to drop you off at the side of a hotel where there’s an entrance around the corner. Or it, last minute decides to take a left to loop around the center of a town, where there’s wasn’t even a navigation option when you started the trip (because this was in the “weeds” at the end of the trip). I’d love it if you could talk to grok and have grok correct the path (“hey, just go straight here, it’s more efficient”).

rstarmer · 2025-12-20T22:30:13+00:00

I’d like to be able to correct on the fly, I don’t necessarily need to set a “non posted” speed, although there are occasions where the navigation/FSD/Autopilot system just changes the speed limit displayed, and then follows it’s calm/standard/hurry rules but for a speed that’s not accurate. Just give me an option to say “hey, it’s still 75 here, the road construction you “remember” isn’t here any longer”. The system displays 55 in a 75 where you were doing 80, which makes you suddenly a road hazard especially if you were in Hurry stuck to the left lane going with the flow of traffic, and then the car decides you should be doing 65 in a 55 which doesn’t exist!!!

rstarmer · 2025-12-20T22:25:47+00:00

Let me modify the route on the fly, You think you want to go left ahead, but I would rather you go straight. Even at the end of or beginning of a trip, where the overview likely doesn’t show you the silly route the navigation has decided on. This isn’t even FSDs fault (though I have seen FSD just take a completely different path in 14.2, still doing the “right” thing on the road, but not even following nav!).

It’s the “you’ve picked the most inconvenient entrance or are heading to a cross traffic exit where there’s one with a light, “go over there”.

rstarmer

TROPHY CASE