Ways to improve FSD feedback loop (v14.3.2 and beyond)

[Aces-Truck]

Now that we have Intervention Categories, It's clear that Tesla is trying to get better feedback on when we take oveover for FSD. I welcome that. But the method used in 14.3.2 (at the time of this initial post) IMO still is pretty lacking. There are two things that stick out for me:

1) I run into cases where it's not clear what Category to use.
2) The need to interact with the screen right after taking over for FSD can be a bit dangerous, when you are dealing with the need to become the Driver. Especially if it happens in the middle of an intersection.

I read a good article at "Tesery.com" discussing this feedback loop here: "https://www.tesery.com/blogs/news/t...s?shpxid=ae3a1bbe-a908-4d6f-a158-a0117d0546d7".

I like the idea of another category like "Disregard". But maybe we should look at all the current categories, to see if others are needed. For me, I tend to kick out FSD repeatedly, in two scenarios: At home where I want to back in; and at a friend's house where it thinks it should turn into a neighbors driveway. I tend to pick "Navigation" as the reason, or sometimes "Preference". But without consistency in which categories to use, I think it will be less useful for the Tesla engineers to find the edge cases they want to fix. What other ideas do you guys have for this?

Sponsored

 

[shopaholic]

I agree, most of the time, I takeover near my house, driveway or at a destination for parking. I also see that it doesn’t pick best spots at superchargers and or totally a wrong location.

 

[hemiarch]

I agree with “navigation” because I frequently disengage for boneheaded routing decisions.
the other place I frequently take over is “lane choice” decisions. Moving to the fast lane half a mile before your exit doesn’t work well and predictably leads to navigation errors like missed exits.
I think the parking decision to backup or pull in forward didn’t belong in this menu but should be a feature in the driveway/curbside/street menu.
the worst possible time to ask this is right after disengagement but that can be remedied with a snooze button.

 

[CyberGus]

Moving to the fast lane half a mile before your exit doesn’t work well and predictably leads to navigation errors like missed exits.

I've noticed in the latest build that FSD is now aggressively moving to the rightmost lane when approaching an upcoming turn or exit. Several times it stuck me behind slow-moving traffic when the exit was 2 miles out. It even cancelled my turn-signal override to go around lol.

 

[hemiarch]

I've noticed in the latest build that FSD is now aggressively moving to the rightmost lane when approaching an upcoming turn or exit. Several times it stuck me behind slow-moving traffic when the exit was 2 miles out. It even cancelled my turn-signal override to go around lol.

Fantastic. That would be a welcome improvement for me. I find myself saying WTF? most often right before an exit.

 

[CyberGus]

Fantastic. That would be a welcome improvement for me. I find myself saying WTF? most often right before an exit.

Right, when traffic is heavy you can't wait until the last moment to get in the exit lane, or else you end up being "that guy" with your blinker on, pleading for someone to let you cut the line lol

 

[hemiarch]

Right, when traffic is heavy you can't wait until the last moment to get in the exit lane, or else you end up being "that guy" with your blinker on, pleading for someone to let you cut the line lol

Yeah. In a Cybertruck. The vehicle everyone loves to let merge the most.

 

[REM]

I'd love to see the option to have Grok prompt us for the reason. This would take quite a lot of work on their side, however.

 

[Pops]

My major gripe with the feedback window is it cant be dismissed. I do appreciate that they made it much smaller with the 2nd update. But as OP stated sometimes its "none of the above" and I just want to dismiss the window. If there is a way, I have not found it.

 

[Blue Oval Ron]

It's a pain in the arse.
Hate it.
And go back to scrolling the thumbwheel for speed control. The presets suck too

 

[hemiarch]

My major gripe with the feedback window is it cant be dismissed. I do appreciate that they made it much smaller with the 2nd update. But as OP stated sometimes its "none of the above" and I just want to dismiss the window. If there is a way, I have not found it.

I think of “preference” as kind of the dismiss or x button. What do you guys mostly use this option for?

 

[SlegMD]

I still laugh when I look at the “discomfort” option. Seems… odd

Usually between Nav and pref myself.

 

[TyPope]

Now that we have Intervention Categories, It's clear that Tesla is trying to get better feedback on when we take oveover for FSD. I welcome that. But the method used in 14.3.2 (at the time of this initial post) IMO still is pretty lacking. There are two things that stick out for me:

1) I run into cases where it's not clear what Category to use.
2) The need to interact with the screen right after taking over for FSD can be a bit dangerous, when you are dealing with the need to become the Driver. Especially if it happens in the middle of an intersection.

I read a good article at "Tesery.com" discussing this feedback loop here: "https://www.tesery.com/blogs/news/t...s?shpxid=ae3a1bbe-a908-4d6f-a158-a0117d0546d7".

I like the idea of another category like "Disregard". But maybe we should look at all the current categories, to see if others are needed. For me, I tend to kick out FSD repeatedly, in two scenarios: At home where I want to back in; and at a friend's house where it thinks it should turn into a neighbors driveway. I tend to pick "Navigation" as the reason, or sometimes "Preference". But without consistency in which categories to use, I think it will be less useful for the Tesla engineers to find the edge cases they want to fix. What other ideas do you guys have for this?

We need to add another category "Because a rice burner gunned his engine at the stoplight"

 

[TyPope]

We need to add another category "Because a little fart box gunned its engine at the stoplight"

 

[DMSTR]

I'd love to see the option to have Grok prompt us for the reason. This would take quite a lot of work on their side, however.

I agree. Maybe Grok could provide"1 - bla bla bla, 2: bla bla bla" etc. Rather than covering the screen with the options.

Sponsored