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:
11.3.6 seems to be settling down which is consistent with releases that seem to improve over a couple of weeks. No idea why this appears to happen. I am back to the point with 11.3.6 that the majority of drives are disengagement free. Overall now 11.3.6 is an improvement for me.

Today my only "No Right on Red" sign was actually recognized and the car didn't turn. First time ever that has happened. I saw posts in Reddit that stated the same.

Yesterday I drove 150 miles on controlled access highways and had 1 disengagement which was so I could verbally provide feedback when the car wanted to go to the passing lane when I was approaching an exit. While I still don't like some of the zip merges I am finding that if I just wait the car is merging "successfully" so I'm waiting a lot longer before considering disengaging.
 
11.3.6 seems to be settling down which is consistent with releases that seem to improve over a couple of weeks. No idea why this appears to happen. I am back to the point with 11.3.6 that the majority of drives are disengagement free. Overall now 11.3.6 is an improvement for me.

Today my only "No Right on Red" sign was actually recognized and the car didn't turn. First time ever that has happened. I saw posts in Reddit that stated the same.

Yesterday I drove 150 miles on controlled access highways and had 1 disengagement which was so I could verbally provide feedback when the car wanted to go to the passing lane when I was approaching an exit. While I still don't like some of the zip merges I am finding that if I just wait the car is merging "successfully" so I'm waiting a lot longer before considering disengaging.
It seems that the car is heeding No Turn on Red signs. If so, Tesla should add something to the visualization to indicate this. As timid as the car has been when it does not have the right of way, it's hard to say whether this is intentional.
 
This double left turn seems to be causing trouble for 11.3.6:
double left into wide fork.jpg


Seems like something map data will need to handle as this Google Street View perspective from the right-most of three 1-way lanes shows the white car turning from the left-most lane into the middle/right of a really wide lane that soon forks to a left-turn-only lane and straight lane. The tricky visual aspect is that this overpass/bridge is a fixed width for 4 total driving lanes but it happens to be split into 1 oncoming and 2 destination lanes for the double left turn, but there's no visible dashed white lane separators until past the white car.

It would help if there were guiding stripes painted for the double left or maybe even clearer / earlier lane separators, but these still would only help when close enough to see them, so medium-term planning to get into the appropriate lane would still need to rely on pretty precise lane details that indicates there's initially 2 lanes with the left one immediately splitting.

The current behavior seems to be it really wants to be in the outer turn lane because it believes the inner turn lane will be forced to make a left turn, but this also is problematic in that during the outer left turn, it tries to switch to where people in the inner turn lane would drive (people don't usually make this 2-step U-turn.) Similarly, if I force it into the inner turn lane, it tries really hard before the turn to get out, but when actually making the inner left turn, it stays really far left making people think we're taking the next left turn and is slow / unable to get into the straight lane because it thinks there's 3 lanes instead of the current lane forking.

What's worse is at least OpenStreetMap's data incorrectly indicates there's 4 total lanes here (with no distinction of how many in each direction).
 
  • Like
Reactions: FSDtester#1
It’ll be good enough for me whenever it meets a certain set of my personal requirements, regardless of the % of completion. Those requirements are simple: no more jerking off the steering yoke and no more watching me via cabin camera to make sure I’m jerking off the steering yoke.
At least for FSD I'm very glad I don't have a steering yoke. At least with the steering wheel I just let the wheel slide thru my hand(s). Super easy and I'm always in control. The yoke for FSD at least would seem to be a nightmare based on all the videos I've watched. No wonder some posters view the yoke jerking as a major problem.
 
At least for FSD I'm very glad I don't have a steering yoke. At least with the steering wheel I just let the wheel slide thru my hand(s). Super easy and I'm always in control. The yoke for FSD at least would seem to be a nightmare based on all the videos I've watched. No wonder some posters view the yoke jerking as a major problem.
True, why jerking the steering wheel especially at slow speed turns and residential streets? After more than one year of coding and NN tuning? Tesla needs to put someone who knows how to drive on coding the drive mechanics module!! This is not a racing game implementation!
 
  • Funny
Reactions: EVNow
I agree with the poster a few posts ago about everything calming down. I drove about 50 miles today and only had one disengagement intervention and a couple Accelerator pedal pushes. everything was fairly smooth. Even did a couple roundabouts pretty well. The disengagement was before the roundabout. It was accelerating pretty quick and a car was entering the roundabout to my left, and it caught it almost too late and slammed on the brakes and I disengaged at that point, but Other than that things are a lot better. Looking forward to 11.4.
 
True, why jerking the steering wheel especially at slow speed turns and residential streets? After more than one year of coding and NN tuning? Tesla needs to put someone who knows how to drive on coding the drive mechanics module!! This is not a racing game implementation!
I'm as annoyed as the next guy about this stuff, but let's remember that nobody has ever done this before. This is a research project in pretty much every way. The hardware (multiple sets), the driving software, the planning software, the training infrastructure, the simulations, analysis tools, version control, safety requirements, performance requirements, visualizations, different driving environments for weather, road types, road configurations - the list of items that have to be considered and resolved must be absolutely endless. I think the only thing that was generally solved when they started was identifying objects in images and drawing boxes around them.

Criminy. They even got yanked into Twitter for a while there.

I believe that it is all the gubbage surrounding the project that is slowing down progress the most. I wonder how much time they get to spend on the actual driving software, algorithms and neural networks. Any other engineers here know that sensation from their own professional life?
 
  • Like
Reactions: Dennisis
I'm as annoyed as the next guy about this stuff, but let's remember that nobody has ever done this before. This is a research project in pretty much every way. The hardware (multiple sets), the driving software, the planning software, the training infrastructure, the simulations, analysis tools, version control, safety requirements, performance requirements, visualizations, different driving environments for weather, road types, road configurations - the list of items that have to be considered and resolved must be absolutely endless. I think the only thing that was generally solved when they started was identifying objects in images and drawing boxes around them.

Criminy. They even got yanked into Twitter for a while there.

I believe that it is all the gubbage surrounding the project that is slowing down progress the most. I wonder how much time they get to spend on the actual driving software, algorithms and neural networks. Any other engineers here know that sensation from their own professional life?
Actually, it's a very simple requirement. Jerky steering wheel indicates "out of control". It indicates that you do not know what you are doing. That's why all the wife/girl friend/passengers hates it. Look at the Waymo drive clips. Do you see them jerking the steering wheel?
 
Look at the Waymo drive clips. Do you see them jerking the steering wheel?
Talking about Waymo and FSDb in the same breath is a bit silly. Waymo is a commercial taxi service that operates at low speeds in geofenced areas using very expensive hardware. FSDb is a consumer system that operates at all speeds everywhere using consumer hardware. Tesla is tackling a vastly more difficult problem, and that's why they can't spend the time to fine tune everything just yet. I don't know how long you've been using FSDb, but the wheel jerkiness has been massively reduced. When the FSDb team has the time, I'm sure they'll get the whole thing running buttery smooth - including steering at very low speeds.
 
Talking about Waymo and FSDb in the same breath is a bit silly. Waymo is a commercial taxi service that operates at low speeds in geofenced areas using very expensive hardware. FSDb is a consumer system that operates at all speeds everywhere using consumer hardware. Tesla is tackling a vastly more difficult problem, and that's why they can't spend the time to fine tune everything just yet. I don't know how long you've been using FSDb, but the wheel jerkiness has been massively reduced. When the FSDb team has the time, I'm sure they'll get the whole thing running buttery smooth - including steering at very low speeds.
I thought I was talking about low speeds in residential areas. Something which do not need a lot of Beta driving setups and feedbacks. Certainly lower effort than UPL turns. Just imagine taking a DMV driving test, if you jerk your steering wheel driving out of the DMV office. Your examiner probably will tell you to head back immediately.
 
Observed what seems like new, or at least newly mentioned in the UI "Merging out of the rightmost lane" behavior today; it was a stretch of freeway with no onramps / offramps on the right side. The nav actually needed the car to stay in the right lane due to me needing to exit at the next exit.

It did end up merging back to the right lane eventually, but not after 2 attempts to get out of the right lane. First one I wasn't paying attention to the screen and disengaged when I felt the car suddenly start to leave the lane (the blinker activated late), and the second time I let it merge to see how soon it would merge back.

Also it seems like the "sound / vibrate" feature to warn before changing lanes doesn't work for FSDb because I have both enabled
 
Actually, it's a very simple requirement. Jerky steering wheel indicates "out of control". It indicates that you do not know what you are doing. That's why all the wife/girl friend/passengers hates it. Look at the Waymo drive clips. Do you see them jerking the steering wheel?
Simple requirements don't necessarily mean simple solutions. The jerky wheel drives me a bit nuts as well but I wouldn't presume to tell the developers it's an easy fix.
 
I think Alan will approve it before Jeb does.



It’ll be good enough for me whenever it meets a certain set of my personal requirements, regardless of the % of completion. Those requirements are simple: no more jerking off the steering yoke and no more watching me via cabin camera to make sure I’m jerking off the steering yoke.

My biggest gripe with the software is not its crap driving but the constant nagging along with the crap driving. Adding those two ingredients is what creates the Faux Self Driving: Junk.

🤣
 
I agree with the poster a few posts ago about everything calming down. I drove about 50 miles today and only had one disengagement intervention and a couple Accelerator pedal pushes. everything was fairly smooth. Even did a couple roundabouts pretty well. The disengagement was before the roundabout. It was accelerating pretty quick and a car was entering the roundabout to my left, and it caught it almost too late and slammed on the brakes and I disengaged at that point, but Other than that things are a lot better. Looking forward to 11.4.
Seriously, how is this even possible? The on board software does not evolve within the car. Clearly a placebo effect, or driver learning/acceptance curve.

If there any proof of how this could even happen (“settling down”)???
 
  • Like
Reactions: Les Mann
Seriously, how is this even possible? The on board software does not evolve within the car. Clearly a placebo effect, or driver learning/acceptance curve.

If there any proof of how this could even happen (“settling down”)???
It's probably due more to the various factors (traffic, lighting, nav route, etc ) that affect FSDb averaging out as the driver undertakes additional trips.
 
  • Like
Reactions: jebinc