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:
Tesla has been wanting to merge FSD Beta into the main production vehicle software, so potentially 2023.12.10 with FSD Beta 11.3.6 is the first release doing so, and it makes some sense to use an "old" FSD Beta version to reduce risk of trying to incorporate 11.4.x changes that are still changing. Similar to how say the media player functionality doesn't need to change on every vehicle update, FSD Beta functionality doesn't need to change either when going to say 2023.16.x.

Going forwards, Tesla can still maintain "early access" releases to test out newer versions of FSD Beta probably to the pre-Safety-Score group that the rest of us wait for it to get to a newer production version. In some sense, basically all of us will be in very similar situation of those waiting to get FSD Beta for the first time where "too new" software prevents updating to a compatible FSD Beta (e.g., until yesterday, those on 2023.12.5 could not update to 2022.45.15 / FSD Beta 11.3.6 nor 2023.7.5 / FSD Beta 11.4.1) except there will be some baseline version of FSD Beta available starting with 11.3.6.

To be clear, Tesla can still segment who receives updates by hardware, software, region, etc. such as MCU1 vehicles vs with FSD Capability vs in North America. So another next step for FSD Beta is being available on all vehicles even without FSD Capability so at minimum, people newly subscribing or purchasing the software can start using it right away without waiting for a software update. Another next step is to make use of FSD Beta neural networks even without FSD Capability such as replacing legacy stack for basic Autopilot.
 
Big oops there. Updating to 2023.12.x means you have no chance to get 11.4.x, because 11.4.x is based on 2023.7. They don't go backwards in time. 2023.7 means it is based on the code as of the 7th week of 2023, while 2023.12.x is based on th 12th week of 2023. Elon's time machine only goes forward in the, not backwards.

Speaking of time, when Elon says something like 11.4.2 is going to be rolled out "this weekend", what he really means is that it will not be rolled out before this weekend. He lives in a time bubble which only looks to the future, a time diode, so to speak. Like a >, a "greater than" symbol. He sounds like he means "this weekend", but he really means "not before" this weekend. He has never meant "Equal To", always "More Than", actual semantics not withstanding. History shows us that he speaks of the future, not the present. Always.

;-)
The lengths Elon will go just to prove me wrong!

Just after I started writing the above, Tesla started rolling out 2023.12.10 which contains FSD beta 11.3.6 . This probably means that what I said above was untrue by the time I posted it. Sorry.

As of this morning, 5/23, there are only 77 pending plus installed copies, so it may still be a few days before everyone gets it. I hope they keep putting FSD beta on current releases going forward. On the other hand, today is in week 21 of 2023, so even 2023.12.x is many weeks behind reality...

I also hope we get 11.4.2 soon, like Elon ... uh...suggested.... we would.

I expect this has already been discussed, but I wanted to apologize ASAP.
 
.....I also hope we get 11.4.2 soon, like Elon ... uh...suggested.... we would......
Elon said 11.4.2 would (not just suggested) start rollout LAST weekend. Clearly that didn't happen so "soon" is defiantly not going to the masses this week or even next next. Clearly 11.4.x has much more serious or at least harder to correct problems that Elon led us to believe. 23.12.10 has to be a stop gap rush out since 11.4.x is not near ready.
 
Elon said 11.4.2 would (not just suggested) start rollout LAST weekend. Clearly that didn't happen so "soon" is defiantly not going to the masses this week or even next next. Clearly 11.4.x has much more serious or at least harder to correct problems that Elon led us to believe. 23.12.10 has to be a stop gap rush out since 11.4.x is not near ready.

Or another guess. Maybe Tesla decided it was more important to drive FSD revenue?
 
Why do you think this is likely?

11.4 was 2023.6.15, 11.4.1 is 2023.7.5. I think it's more likely we see 11.4.2/3 at 2023.12.X.

This isn't the first time revisions have jumped up on base software. 10.69 did the same.

Because no one else is talking about FSD 12.X, yet twice you've brought it up.
I only brought it up when you referenced FSD V12 in your earlier post. See above. Did I misunderstand your post?
 
Looks like Tesla has more than doubled the rollout of 2023.12.10 / FSD Beta 11.3.6 still going to new additions instead of those already on 2022.45.15 / FSD Beta 11.3.6.

A few more previous versions detected with the wider rollout including some factory versions: 2023.2.10, 2023.2.12, 2023.2.201, 2023.6.8, 2023.6.9, 2023.6.11, 2023.6.100, 2023.12.1, 2023.12.1.1, 2023.12.5, 2023.12.9


Seems like it might indicate it's a good time to add FSD Capability subscription -- except for those with HW4 probably waiting for 11.4.x.
 
Looks like Tesla has more than doubled the rollout of 2023.12.10 / FSD Beta 11.3.6 still going to new additions instead of those already on 2022.45.15 / FSD Beta 11.3.6.

A few more previous versions detected with the wider rollout including some factory versions: 2023.2.10, 2023.2.12, 2023.2.201, 2023.6.8, 2023.6.9, 2023.6.11, 2023.6.100, 2023.12.1, 2023.12.1.1, 2023.12.5, 2023.12.9


Seems like it might indicate it's a good time to add FSD Capability subscription -- except for those with HW4 probably waiting for 11.4.x.
Suspect that once all or most of the newbies are in, they'll probably let us old farts in so we can get whatever additional bells and whistles are in the 2023.12.X release.

My suspicion is that whenever some SW types are gluing large hunks of software together, Bugs Will Be Found.

Ha. Back in the day when in my Freshman year in Engineering, we were all forced into our very first programming class. In FORTRAN. (Should note: Unix and C were very, very new at the time and not seeing widespread use.) The prof made a point of telling all us newbies the below:

General rule: Write a 300 line program, not including whitespace and comments. 'Way more than half of the lines will have errors in them. Typos, everything else.

Before compiling, run Lint or the equivalent. This knocks the error rate to 25% of the lines. A lot fewer typos, but there'll be plenty of other errors.

Try compiling. The number of errors after fixing all the ABENDS and such in the compiler drops the error rate to 10%.

Start testing the software, varying the inputs and such. If one is lucky, error rate falls to 1%. And, for a very, very long time, that's where things stayed stuck. There might be errors in the code, but the SW will work well enough.

Now, imagine a code base of a million lines. Or two million lines. At 1% error rate, we're talking a 100,000-200,000 bunch of errors in the code.

If you were wondering why Microsoft/Apple/Adobe/etc have monthly updates, well, now you know 😁.

Modern techniques, like running fuzzers, or using languages that put a straight-jacket on one's coding practices, can perhaps knock the error rate down by another factor of ten, but there'll still be a huge number of errors out there.

The prof stated that, once in a while, some miracle worker or other will write a 300 line routine that has no errors, on the first try. People like that are out there to irritate the rest of us and proving that the exception makes the rule. Which only proves that really, really good programmers are worth their weight in gold and become internationally famous, like Moxie Marlinspike and Bruce Schneier.
 
Suspect that once all or most of the newbies are in, they'll probably let us old farts in so we can get whatever additional bells and whistles are in the 2023.12.X release.

My suspicion is that whenever some SW types are gluing large hunks of software together, Bugs Will Be Found.

Ha. Back in the day when in my Freshman year in Engineering, we were all forced into our very first programming class. In FORTRAN. (Should note: Unix and C were very, very new at the time and not seeing widespread use.) The prof made a point of telling all us newbies the below:

General rule: Write a 300 line program, not including whitespace and comments. 'Way more than half of the lines will have errors in them. Typos, everything else.

Before compiling, run Lint or the equivalent. This knocks the error rate to 25% of the lines. A lot fewer typos, but there'll be plenty of other errors.

Try compiling. The number of errors after fixing all the ABENDS and such in the compiler drops the error rate to 10%.

Start testing the software, varying the inputs and such. If one is lucky, error rate falls to 1%. And, for a very, very long time, that's where things stayed stuck. There might be errors in the code, but the SW will work well enough.

Now, imagine a code base of a million lines. Or two million lines. At 1% error rate, we're talking a 100,000-200,000 bunch of errors in the code.

If you were wondering why Microsoft/Apple/Adobe/etc have monthly updates, well, now you know 😁.

Modern techniques, like running fuzzers, or using languages that put a straight-jacket on one's coding practices, can perhaps knock the error rate down by another factor of ten, but there'll still be a huge number of errors out there.

The prof stated that, once in a while, some miracle worker or other will write a 300 line routine that has no errors, on the first try. People like that are out there to irritate the rest of us and proving that the exception makes the rule. Which only proves that really, really good programmers are worth their weight in gold and become internationally famous, like Moxie Marlinspike and Bruce Schneier.
I frankly expected a lot fewer ABENDS in my FSDb due to the improvements in FORTRAN and Linters over the last 30 years