Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register
This site may earn commission on affiliate links.
The next big milestone for FSD is 11. It is a significant upgrade and fundamental changes to several parts of the FSD stack including totally new way to train the perception NN.

From AI day and Lex Fridman interview we have a good sense of what might be included.

- Object permanence both temporal and spatial
- Moving from “bag of points” to objects in NN
- Creating a 3D vector representation of the environment all in NN
- Planner optimization using NN / Monte Carlo Tree Search (MCTS)
- Change from processed images to “photon count” / raw image
- Change from single image perception to surround video
- Merging of city, highway and parking lot stacks a.k.a. Single Stack

Lex Fridman Interview of Elon. Starting with FSD related topics.


Here is a detailed explanation of Beta 11 in "layman's language" by James Douma, interview done after Lex Podcast.


Here is the AI Day explanation by in 4 parts.


screenshot-teslamotorsclub.com-2022.01.26-21_30_17.png


Here is a useful blog post asking a few questions to Tesla about AI day. The useful part comes in comparison of Tesla's methods with Waymo and others (detailed papers linked).

 
Last edited:
I’ve been using it for drive mode, chill or insane. I play a game to see how efficient I can be, until a courteous driver at a red light has his windows down and lets me partake of his most awesome Spanish speaking music blasting so loud it makes my windows shake while revving his Toyota or Honda. I do believe if it worked with suspension, I’d appreciate that a tad more.
It does work with suspension... that is what my left scroll is programmed to.
The Plaid vibrates less from a hole shot in the lowest suspension setting.
 
It does work with suspension... that is what my left scroll is programmed to.
The Plaid vibrates less from a hole shot in the lowest suspension setting.
Yea but it’s a terrible implementation for suspension. “Drive Mode” lets you select between all modes. “Suspension” only lets you go up 1 notch. Can’t go all the way up and can’t go back down without manually going back into the menu or speeding up fast enough for the car to just default back to a lower setting.
 
Has anyone made or found a youtube video that shows hw4 behaving better that hw3? I haven't, and if anything I have seen the opposite.
It probably won't be too long before hw5 chatter starts. Unless they add a forward camera(s) to hw4. Current b pillars will keep the car turning all right turns.
DirtyTesla made a semi comparison and they seem about the same.

 
I was in MN last week and 11.4.4 was dreadful on roads like this with turning lanes. It keep 'diving' into them at 55 MPH.
A variety of other missteps on this last road trip as well with it taking turns to early and didn't follow routing. Luckily we started watching for this behavior.
So annoying that the max speed keeps changing to whatever nearby or crossing road we would pass on various highways. Had to regularly bump it upt.
Highway FSDb is pretty bad compared to Highway AP.

HjDu0Db.jpg
In all fairness, FSD is trying to do a whole lot more than AP. All AP does is essentially stay in the lane and it's easier to do a good job when you have less of a job to do but if the only job you really need is staying in the lane it's a frustrating step backwards with FSD.

Maybe it's a MN thing but ducking into turn lanes has been one of my major complaints with FSD for the last year or so. It's improved a bit the more recent versions (at least those before 11.4.4) but it's definitely still a problem. Did it not do that behavior for you?
 
In all fairness, FSD is trying to do a whole lot more than AP. All AP does is essentially stay in the lane and it's easier to do a good job when you have less of a job to do but if the only job you really need is staying in the lane it's a frustrating step backwards with FSD.

Maybe it's a MN thing but ducking into turn lanes has been one of my major complaints with FSD for the last year or so. It's improved a bit the more recent versions (at least those before 11.4.4) but it's definitely still a problem. Did it not do that behavior for you?
I see most of your point on AP vs FSD but wow you'd think they have a QA priority to make sure there wasn't obvious general behavior regression like these two things -- lanes and MPH changes.

I was in MN last summer but don't recall having this issue.

It seemed MN is really really good about traffic flow and those two types of turning lanes let traffic behind them keep the flow going.
 
According to TeslaFi there's a good number of people on 11.4.7.2 now. 11.4.4 is becoming the version for the un-cool kids.

I got it yesterday but I'm at work now so I can't check to see which map version I have.
11.4.4 is the version for the un-cool kids who upgraded to a new HW4 car like me!
 
11.4.4 is the version for the un-cool kids who upgraded to a new HW4 car like me!
I was a-posting on a similar thread yesterday, mildly bemoaning the fact that, with a 2023 M3 with HW4, I was stuck with 11.4.4. And based upon Elon's comments a couple of months ago, it might be six months or something until I got caught up with the HW3 types.

And then appeared, out of the blue, another HW4 person who's actually on 11.4.7.2.

Tricky bit: I just got upgraded from (I think) 2023.26.100, which is what the car came with, to 2023.32.7 which had 11.4.4. The person who popped into the discussion had something like 2023.26.something-or-other; so, clearly, 11.4.7.2 might have to wait a bit until the numbers catch up. Whee!
 
I see most of your point on AP vs FSD but wow you'd think they have a QA priority to make sure there wasn't obvious general behavior regression like these two things -- lanes and MPH changes.
oh, yes, I agree. It's frustrating to have it take a step backwards and frustrating how they seem to be in the habit of breaking things in the process of fixing others.

AP was originally intended for larger, controlled access highways and spread 'down' to undivided highways than 2 lane roads/highways. But then where do you draw the line between an 'autopilot road' and a 'FSD road?' and how do you progress FSD without compromising AP? Tesla made a jump when they released V11 that combined everything and pushed FSD to highways. It was a necessary break but it also caused the problems we're experiencing.

Have you tried disabling FSD and using AP on a road to compare the two? I'm curious how they would behave differently.

MPH changes are a bit tricky - how do you know what the speed limit is? You can remember from the last time you drove on a road, you can watch for a speed limit sign, you can estimate based on the road and how other people are driving or you can refer to traffic laws (e.g. in MN the speed limit on highways is 55 MPH unless otherwise posted.) The problem is, all of those can be wrong or you can miss data and what do you do if you have conflicting data? FSD has a 'memory' in the form of the map database. Of course the map database will always be out of date to a certain degree so then you use speed limit signs. But what happens when you can't see the signs because they're blocked by a truck, tree, etc? To us it's pretty straight forward but that's because humans are really good at fuzzy logic. When you start to write rules for figuring out how fast you should go it gets messy pretty quickly.

Pretty much every other car company will only release a 'finished' product. With Tesla, we truly are getting the beta version and experiencing all the issues therein. Note, I'm not saying Tesla is right in all this, just recognizing some of the issues they face in the development process.
 
I was a-posting on a similar thread yesterday, mildly bemoaning the fact that, with a 2023 M3 with HW4, I was stuck with 11.4.4. And based upon Elon's comments a couple of months ago, it might be six months or something until I got caught up with the HW3 types.

And then appeared, out of the blue, another HW4 person who's actually on 11.4.7.2.

Tricky bit: I just got upgraded from (I think) 2023.26.100, which is what the car came with, to 2023.32.7 which had 11.4.4. The person who popped into the discussion had something like 2023.26.something-or-other; so, clearly, 11.4.7.2 might have to wait a bit until the numbers catch up. Whee!
Wouldn't it be nice if they could separate the FSD code from the rest of the code? I have to assume that the two are much more intertwined than it appears at first blush.
 
Wouldn't it be nice if they could separate the FSD code from the rest of the code? I have to assume that the two are much more intertwined than it appears at first blush.
Didn’t we get excited when they merged the different stacks? I thought they started with seperate code? Maybe I’m remembering it wrong
 
Wouldn't it be nice if they could separate the FSD code from the rest of the code? I have to assume that the two are much more intertwined than it appears at first blush.
The car came with 11.3.7 on the original code. And it was pretty much like I think I remembered it: Very jerky on the turns. However, and this is because I can't remember, there was that FHTSA-mandated recall where a Tesla on FSD wouldn't slow down quickly when the speed limit changed; pretty clearly, this particular variant of 11.3.7 had that.

I'd hate to be the person or group over at Tesla in charger of version management these days. What with different cars, different computers, different countries, different map sets, different Standard Autopilot/EAP/FSD/ and $DIETY knows what-all, it must be a real zoo over there.
 
Last edited:
Didn’t we get excited when they merged the different stacks? I thought they started with seperate code? Maybe I’m remembering it wrong
They didn't merge the stacks they extended the FSD Beta stack to work on highways while keeping the legacy AP stack. The legacy AP stack is still used and on every Tesla. You can easily switch to the legacy AP stack (blue arrow) in the Menu.


IMG_2737.jpeg
 
MPH changes are a bit tricky - how do you know what the speed limit is? You can remember from the last time you drove on a road, you can watch for a speed limit sign, you can estimate based on the road and how other people are driving or you can refer to traffic laws (e.g. in MN the speed limit on highways is 55 MPH unless otherwise posted.) The problem is, all of those can be wrong or you can miss data and what do you do if you have conflicting data? FSD has a 'memory' in the form of the map database. Of course the map database will always be out of date to a certain degree so then you use speed limit signs. But what happens when you can't see the signs because they're blocked by a truck, tree, etc? To us it's pretty straight forward but that's because humans are really good at fuzzy logic. When you start to write rules for figuring out how fast you should go it gets messy pretty quickly.
My MPH management was *way* better just using AP on the highway in the past so clearly they changed the logic and prioritizing the overriding source.
It is nuts to be going 70 and then the limit gets changed to 25. They should have thresholds and double checks to make sure it is not erratically bouncing around.

The key is that they had it figured out before so your question doesn't make sense to me. It's not like they are trying something new in this regard.
 
  • Like
Reactions: pilotSteve
Just got FSD downloaded in my new Model Y. Some comments on a 200 mile trip consisting of mainly highways (no freeways),but passing through several small towns:
  • FSD did not know what to do with flashing red lights - one time would have gone right through without stopping. Another time would have pulled directly out into both oncoming lanes with lots of traffic. A panic stop was needed
  • When approaching a 4 way stop in a high speed highway that did not have reduced speed limits as the stop sign was approached, it kept at 65 mph until I had to do a panic stop -obvious it was going to do a last minute four wheel lock up (maybe??) unless I intervened.
  • When pulling out from a back country road onto a high speed two lane country highway, there was no way the FSD recognized high speed oncoming traffic and would pull out (rather slowly) essentially directly in front of oncoming traffic. I had to panic stop as it tried to pull out. This happened more than once (ok, I'm a slow learner). From watching the visualization screen closely, the vehicles are not recognized at nearly far enough distance to be safe in these instances.
  • "Phantom" brakes a number times - mostly for seemingly no reason - at least could not see anything on the visualization screen.
  • Many fully obvious speed limit signs were ignored. When slower speed limits were approached, the braking was very harsh - a "tailgater" could ram you if inattentive for sure. IMO - don't use any form of autopilot when you have an extreme tailgater - too much phantom braking.
  • Really twisty roads seemed to fool the position of oncoming autos into thinking they were in your lane (mainly right tight turns) and brakes were heavily applied.
  • When no "navigation" route is in place and what I believe is the enhanced autopilot working, the lane keeping was simply exceptional compared to my ProPilot Nissan Leaf. I found that very useful and even confident on open stretches of rural highways. Adjusting the speed setpoint with the steering wheel dial was great. This I hopefully will keep when the 3 months trial of FSD is done.
  • Note that this was the first trip using the "autopilot/FSD" features and I likely do not have optimal "switches" in place for my style of driving (essentially every feature is turned on!). HOWEVER, I will not use FSD under most circumstances - simply too many dangerous actions occur that require close driver attention.
 
Had 11.4.7.2 make a left turn when the route called for this turn to be a right. Absolutely ridiculous.
And yes, this happened twice to me. Once was when a right turn was coming up quickly and the left turn signal turned on and it began steering into a separate left turn lane. I was on navigation/FSD with the right turn clearly part of the route.
 
I’m currently on my 4th Tesla with FSD and started beta testing -two years ago. I’m quite consistent with testing and have seen all kinds of terrible behavior (and some good) during this time, since I live in an urban area. I don’t sugarcoat anything but I’m patient so I keep testing despite plenty of frustration over this time.

My current HW 4 MX on 11.4.7.2 for about two weeks, is almost 3 weeks old. FSD was making the same old dumb, erratic errors, until today.

I noticed almost immediately this morning how much smoother the car was driving. This behavior was consistently better all day, which is notable because I drove a lot yesterday and it was the same old frustrating experience. It wasn’t perfect today but after testing consistently for ~22 months, this had to have been the best fsd experience ever.

They must be doing A/B testing, otherwise I don’t know how it could have improved overnight without a sw update. Anyone else with similar experience?

I see some of Elon’s Twitter followers making similar positive comments but I assumed it was just shilling but now I’m not so sure.
 
Yellow matter custard
Dripping from a dead dog's eye
Crabalocker fishwife, pornographic priestess
Boy, you've been a naughty girl, you let your knickers down
the Tesla Vision single stack dojo enhanced is smarter that humans. It is so smart, that it is pre-wiping the window (Tesla Prevision). I think mine is actually waving to other Teslas, a premium connectivity feature. Did you select single or married in the config.
Also the answer to which one is pink? it's Jethro
 
I’m currently on my 4th Tesla with FSD and started beta testing -two years ago. I’m quite consistent with testing and have seen all kinds of terrible behavior (and some good) during this time, since I live in an urban area. I don’t sugarcoat anything but I’m patient so I keep testing despite plenty of frustration over this time.

My current HW 4 MX on 11.4.7.2 for about two weeks, is almost 3 weeks old. FSD was making the same old dumb, erratic errors, until today.

I noticed almost immediately this morning how much smoother the car was driving. This behavior was consistently better all day, which is notable because I drove a lot yesterday and it was the same old frustrating experience. It wasn’t perfect today but after testing consistently for ~22 months, this had to have been the best fsd experience ever.

They must be doing A/B testing, otherwise I don’t know how it could have improved overnight without a sw update. Anyone else with similar experience?

I see some of Elon’s Twitter followers making similar positive comments but I assumed it was just shilling but now I’m not so sure.
I've seen quite a few comments on here where people have a similarly great drive but then they have a terrible drive the next day.

I have certain spots I drive every day where it acts differently. Like a railroad crossing where it sometimes stops even with no trains or red flashing lights but sometimes it'll go thru fine.

It's the unpredictability that makes it hard to trust it more.