And the Tesla guy was wrong. My configuration can’t get the self parallel park or summons mode yet. The v12 FSD was only rolled out to a relatively small number of users and will be rolled out to the rest of us at some point in the future.
I suggest that whatever you do, don’t obsessively reload https://www.teslafi.com/firmware a few times per day to see if v12 is rolling out yet… It was installed on a bunch of California cars, but nothing more for a week. If you do want to get it, you should go through the in car settings and enable FSD beta, if it is not already. Hopefully you’ll get a chance to try it before your trial period ends.
I’m anxious for it because v11 has really been pretty bad. I mean, if v12 can just manage to avoid taking the bus only exit from the freeway, when the route wants to stay on the freeway, it will be a big improvement.
That makes me laugh, but also makes me think, how do we give corrective feedback? We were driving with Autopilot on home from a hike yesterday and one stretch it had the speed completely wrong. How do I let Tesla know their shit is broke there?
According to a reddit forum, it was rolled out on a bunch of California cars (and I am in California) and later some non-California cars and then nothing. I have the three free months of FSD through a referral and I have Advanced selected so I should be eligible for early updates if they decide to give it to more of us.
I have had two issues. The right turn that you take to get into my neighborhood is weird and confuses people as to whether you can make the turn on red (you can). FSD had me take over. The other issue is that you can be in the far left lane of a freeway going 75 or 80 but there might be someone behind you wanting to go faster. I have to disengage and move over for them and then re-engage.
I thought it was “Pedal to the metal, Commander.”
When disengaging autopilot, a prompt comes up that says something like “Why was autopilot disengaged? Press the right button to leave a voice note.” I did that at first, but stopped because there was no feedback my comments did anything.
The speed can come from (at least) two different places. The map itself usually has the speed limit built into it, but the map is not always correct. There is a road near me, where as best I can tell from the signs the speed limit is 35, however the map has it change between 35 and 40 several times in a few blocks.
The second place is from reading speed limit signs. If the car reads a sign, it will override the map information. Sometimes this is useful, like a slower speed limit for a construction zone (not that anyone slows down), or when the map doesn’t have any information. Near here we have signs that say “25 MPH (unless otherwise posted)” so the car thinks the speed limit dropped to 25, when that is not what the sign says.
Tesla uses Google maps, and it is possible to report problems on Google maps, but I don’t know if speed limits can be reported, or just things like businesses have closed.
By far the greatest interaction I have with FSD is adjusting the set speed. Fortunately that is very easy with the right side wheel on the 3/Y or the stalk on the S/X.
Ok, funny one today. The drive mostly went fine. The good news: when I got to my destination, the car actually picked a spot and parked itself. Amazing! I don’t know what was different here vs. previous times, as this was the first time I’ve seen this behavior. The bad news: it parked in a handicapped spot 
.
I actually wonder about this. Suppose I was legitimately handicapped, having the placard and all that. And suppose my car was fully autonomous and I’m summoning it. Why shouldn’t it pick a handicapped spot? The whole point is that it’s picking me up, and I need to be able to get to it. I suspect the law may need some tweaking.
I think your car knows you and the AI assumed you use a wheelchair based on your username. 
Makes sense. FSD is very useful given how my arm is trying to strangle me all the time…
Just got FSD 12.3 pushed to me (I was on 12.2.1). Supposedly has some major upgrades. Hopefully gets more widely deployed, too. I’ll do some more writeups when I get a chance to test it.
Still on v11.1. Jealous
Good luck! I get the feeling that 12.3 will roll out to more people than 12.2.1, but they might still do a trial run first. It’s a huge improvement at any rate.
Uber spent millions trying to develop a self-driving car and only succeeded in killing a woman crossing a street.
https://www.cnn.com/2023/07/29/business/uber-self-driving-car-death-guilty/index.html
Uber also stole self-driving trade secrets from Google. We probably shouldn’t judge other self-driving efforts based on what Uber did.
It’s a good thing that non-self driving cars never kill anyone. Saying that it’s the only thing that they succeeded in doing is silly hyperbole. Try harder.
It was a non-self driving car that ran my wife over as she was legally crossing a light controlled crosswalk. I bet a self-driving car wouldn’t have done that.
BTW, my wife had multiple traumatic brain injuries and had to have a leg rebuilt but somehow survived and has mostly recovered.
Actually 11.4.1.
Gave FSD 12.3 a spin tonight. It’s a noticeable improvement over 12.2.1. Less of a gap as compared to 11.x of course, but still not trivial.
The constant speed behavior seems to be gone. It held at the speed limit or even more just fine, with no weird variation.
A spot that had a strange slowdown previously no longer has a problem. There’s writing on the road that says “keep clear”, which may have confused it previously, or made it more hesitant. But it had no problem this time.
Some events were just uncanny. I was coming up to a stoplight, 2 lanes in each direction, and the lane I was in had 3 cars at the light, while the other lane was clear. The car changed to the clear lane without any prompting. And very natural, too.
No interventions of any kind either there or back. I suspect that forced interventions are going to be fairly rare from here on out. I’m going to have to rate drives based on some kind of sub-intervention score, where I might have done something differently myself, but didn’t feel the need to intervene.
Another sort of funny problem with 12.2.1: I hit a yellow light at just the wrong moment. We’ve all been there–it’s right on the border, and you’re trying to decide whether to floor it or hit the brakes. But you can’t decide, and the longer you wait the worse the outcome is going to be. Well, the car seemed to have just the same kind of indecisiveness, first seeming to go for it and then hitting the brakes hard at the last minute.
Dunno yet if 12.3 has the same behavior; it’ll take some luck to hit another light in just the same way. We’ll see.
This scares me. The decision at the yellow is a very simple mathematical formula. That should be an easy calculation for a computer.
Time=Distance/speed . Either you have enough time to stop, or you don’t.
Why is this not an instantaneous decision?
Because it’s no longer decided in any strictly mathematical way. That way lies madness, and 300,000 lines of C++ spaghetti code.
They now train a neural net end-to-end with data from actual drivers. And presumably it’s captured exactly the same kind of hesitancy that human drivers display, just as it’s captured the fact that almost nobody actually comes to a total and complete stop at stop signs.
They should be able to fix this with better data, training it only with those cases where drivers aren’t hesitant. But we shouldn’t expect perfection, since human drivers aren’t perfect either. The goal is to have a well-above-average driver that can maintain that state under all conditions (no distractions, no drunkenness, no tiredness, etc.).