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.
Just got this, and few observations on the first drive - as multiple posts above, speed control is worse than v11. It's way too chilled in the middle setting, sometimes drives way below the set speed even without any other traffic or other reasons to do that (I disabled auto speed after a few minutes as that was even worse), I didn't try assertive mode yet. What I absolutely hate is that they removed the single/double pull setting as I use TACC a lot (in particular as the routing doesn't want to use carpool lanes and entry/exits). I did add another profile to go back to autosteer, but there was absolutely no reason to remove that option from FSD.

On the other hand, it is way better in making turns and moving around in general (except that it drove in the middle between 2 lanes a few times while apparently it could not decide to go in one or the other, even when entering a left-turn lane).

All in all this needs a lot more improvement still.
 
I’d be fine with this if it allowed use of the original method of speed control. But the old mode no longer exists.

But seems it is a limitation of the NNs and they CAN’T have a system that just ramps up to the set speed reliably, as it did before, when it has to take into account many other factors as input to the neural network. But right now the NN seems to completely ignore any inputs from driver requested speed above a certain level when using the old mode (which is now a new mode because it is not the same as the old mode).

That being said it seems to be consistently below the limit (perhaps a safety guardrail as you say), so surely they can fix that with training.

But it may be that this borking is going to be with us for the long term. We’ll see if they can figure it out. It could be a more difficult problem than autowipers!

It seems tricky to train a neural network on what speed it should travel. And apparently they can’t just tell it the speed (otherwise the old mode would work). So the days of the car traveling at the requested speed may be behind us.
It worked on 11.4.x on highways with the message:
“Maintaining speed for traffic” or whatever it would say. Figure they could just apply this city streets.
 
Time is short - Opossums are dying, people!

Ditto.

The one to two year lifespan seems too short.

I'm going with 2-4 years.

Opossum women are lovely, with long slender snouts.

The kids are cute:
opossum.jpg


A gnarly block headed male opossum who visited one evening looked pretty ancient. Opossum's super powers are eating venomous snakes and lots of ticks.

Saving wildlife is high on my list of FSDb requirements.
 
It worked on 11.4.x on highways with the message:
“Maintaining speed for traffic” or whatever it would say. Figure they could just apply this city streets.
Totally different since that could just be managed with the planner code.

If (traffic is going faster) then
Speed up
endif

That was 3 lines of the 300k lines.
 
  • Like
Reactions: gsmith123
A little bit more information for our neighbors to the North. Sounds like Canada will not be a part of this rollout, as additional training and validation is required for the country:

I’d be wondering if this is affecting the Model S/X rollout outside of areas in California where the vehicles are less numerous and thus data are lacking.
 
  • Like
Reactions: ArchHamster
but there was absolutely no reason to remove that option from FSD.

A theory I've heard about why it's gone is that they don't have enough compute to run:
- V12 (actually driving the car)
- V11 stack (for visualizations and probably automatic emergency braking)
- V-whatever legacy stack that controls TACC (as fallback when you override steer and the car reverts to TACC)

So they had to cut something and they decided to turn off TACC.

That said with a bit more work they could let you turn on TACC when FSD is off, via a double stalk pull. That wouldn't run into any compute limits since it wouldn't need to run TACC in parallel.

Knowing Tesla they can be pretty ruthless in prioritization though and may have just decided TACC wasn't that important (we're beta testers after all, I personally think I've agreed to deal with drawbacks like that and I don't have to take every update).
 
A theory I've heard about why it's gone is that they don't have enough compute to run:
- V12 (actually driving the car)
- V11 stack (for visualizations and probably automatic emergency braking)
- V-whatever legacy stack that controls TACC (as fallback when you override steer and the car reverts to TACC)

So they had to cut something and they decided to turn off TACC.

That said with a bit more work they could let you turn on TACC when FSD is off, via a double stalk pull. That wouldn't run into any compute limits since it wouldn't need to run TACC in parallel.

Knowing Tesla they can be pretty ruthless in prioritization though and may have just decided TACC wasn't that important (we're beta testers after all, I personally think I've agreed to deal with drawbacks like that and I don't have to take every update).
traditional radar would probably help with TACC specifically
 
A theory I've heard about why it's gone is that they don't have enough compute to run:
- V12 (actually driving the car)
- V11 stack (for visualizations and probably automatic emergency braking)
- V-whatever legacy stack that controls TACC (as fallback when you override steer and the car reverts to TACC)

So they had to cut something and they decided to turn off TACC.

That said with a bit more work they could let you turn on TACC when FSD is off, via a double stalk pull. That wouldn't run into any compute limits since it wouldn't need to run TACC in parallel.

Knowing Tesla they can be pretty ruthless in prioritization though and may have just decided TACC wasn't that important (we're beta testers after all, I personally think I've agreed to deal with drawbacks like that and I don't have to take every update).
Except they woulnd’t be running them simultaneously. V12 on city streets, TACC with single pull or steering override.
 
If I don’t have 12.3 by 6am I’m going to find a 1967 Dodge Dart in a junkyard, fill it with a combination of 87 octane and kerosine, fill the oil tank to WELL ABOVE the fill line (gasp!), remove the catalytic converter, park near a grove of young trees, and hold the RPMs at 6,000 as the trees get doused in poisonous gas until the tank runs dry.

My terms have been laid out. Tesla, you have less than 8 hours to comply.
 
If I don’t have 12.3 by 6am I’m going to find a 1967 Dodge Dart in a junkyard, fill it with a combination of 87 octane and kerosine, fill the oil tank to WELL ABOVE the fill line (gasp!), remove the catalytic converter, park near a grove of young trees, and hold the RPMs at 6,000 as the trees get doused in poisonous gas until the tank runs dry.

My terms have been laid out. Tesla, you have less than 8 hours to comply.
Don’t forget to drive over some opossi on the way!
 
Except they woulnd’t be running them simultaneously. V12 on city streets, TACC with single pull or steering override.

To fallback on TACC on steering override it does need to keep TACC running continuously, so it can instantly switch over. Otherwise you'd get a weird jerky cutover between when FSD drops out and TACC starts up.

(Obviously I don't have an real inside insight into Tesla's software to confirm these ideas, but it seems pretty plausible to me)