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:
Sorry to tell you, your manufacturer build only integrated into mainline 2023.2.12, so you won't get current release of FSDb. May as well upgrade to mainline and wait until the next FSDb release.
Can you elaborate? I’m on 2022.44.100 too and I thought since the number is lower than 2022.45.11 (or today’s 2022.45.12) that my car would update to latest FSD build. How is manufacturer build slotted into the other builds. Us new owners want to play your FSD games too.
 
  • Like
Reactions: jebinc
Can you elaborate? I’m on 2022.44.100 too and I thought since the number is lower than 2022.45.11 (or today’s 2022.45.12) that my car would update to latest FSD build. How is manufacturer build slotted into the other builds. Us new owners want to play your FSD games too.
Any build ending in three digits, e.g. 100, 101, 200, etc. is a manufacture build that your car comes with. This build usually contains changes specific to some new parts in your car. Those changes need to integrate into the mainline build, which would normally be the next major build after the current mainline. In this case your build is based on 2022.44.x (Year 2022 Week 44). The next mainline major build was 2032.2.x (Year 2023 Week 2).

The 2022.45.x build is a special build of mainline 2022.44 specific for FSDb. So there is no way your manufacture build would "upgrade" to any build other than the next major one that you are based on, i.e. 2023.2.x or later.

Hope that helps.
 
Last edited:
Still not quite enough to update all of the 2022.45.11 cars. So this is not a widening of the 11 rollout, yet.
I don't know how accurate it is, but according to "Not a Tesla App",

11.3.2 (2022.45.11) has 238 installs with 55 pending
11.3.3 (2022.45.12) has 317 installs with 116 pending

That suggests that they're expanding the rollout - assuming the site's numbers are meaningful.
 
Last edited:
So, see attached. I’ve been tracking this since 10.2 or .3, whatever. This is my neighbors driveway, it’s like a mile long, and at this same spot every time FSDb throws up this error. Essentially, it’s an unmarked rural road (but, it’s a driveway). Never makes it past this curve. Figure I’d post a pic, since it’s been almost two years of failures. It’s gotta be map data that doesn’t allow this to work, as my road I live on, pretty much looks just like this, only a bit wider, and FSDb drives it just fine. Who knows?
 

Attachments

  • BE4FE5CE-53EA-4223-8F0E-086F52B05A11.jpeg
    BE4FE5CE-53EA-4223-8F0E-086F52B05A11.jpeg
    391.8 KB · Views: 48
So, see attached. I’ve been tracking this since 10.2 or .3, whatever. This is my neighbors driveway, it’s like a mile long, and at this same spot every time FSDb throws up this error. Essentially, it’s an unmarked rural road (but, it’s a driveway). Never makes it past this curve. Figure I’d post a pic, since it’s been almost two years of failures. It’s gotta be map data that doesn’t allow this to work, as my road I live on, pretty much looks just like this, only a bit wider, and FSDb drives it just fine. Who knows?
Is GPS pin-point accurate on the that driveway?
 
  • Helpful
Reactions: FSDtester#1