I had it give me an audible alert today on a two lane road with a dead bird in my lane and a car approaching in the other lane.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
FSD v12.x (end to end AI)
- Thread starter Buckminster
- Start date
-
- Tags
- #fixphantombraking autopilot chill is not chill elon is an ass fix fsd extreme late deceleration fsd does not commit to go fsd does not maintain proper speed fsd hard and late braking fsd jerky driving fsd late deceleration fsd stops too early too quickly fsd stops too far behind line fsd tailgating in city streets
Musskiah
DisGruntled
A dead bird!?!? Are we talking like a turkey-sized bird or a finch-sized?
And was it actually dead or merely pining for the fjords?
Looked like a crow had gotten run over. Decent sized bird. I suspect FSD would have preferred to avoid it but couldn’t because of the oncoming traffic, hence the audible alert.
What did the alert say? I keep getting a toll booth detected alert on 12.3….. and I have yet to drive through a toll booth since I got that update.
12.3 has a vivid imagination. Like, about that number on the speed limit signs. I was on a back road marked 35 yesterday and the visualization showed a sign with 60 on it. It did correct at the subsequent limit 35 sign.What did the alert say? I keep getting a toll booth detected alert on 12.3….. and I have yet to drive through a toll booth since I got that update.
I completely forgot about that. I have it spazz out and show the alert 15 times in 1 minute.What did the alert say? I keep getting a toll booth detected alert on 12.3….. and I have yet to drive through a toll booth since I got that update.
If it stops trying to destroy wheels, I's be sooooo happy.
Tire company executives are starting to sweat on the toilet from profit.
Got to love when stuff like this happens, they start the roll out to 12.3.1 then stop the roll out, start roll out to 12.3.2, then stop the roll out, start the roll out to 12.3.2.1 then stop the roll out, now 12.3.3 is on the radar and a lot of us are still stuck on 12.3 baked into 2023.x main branch 
It took us how long just to get 12.3 because they kept doing that?Got to love when stuff like this happens, they start the roll out to 12.3.1 then stop the roll out, start roll out to 12.3.2, then stop the roll out, start the roll out to 12.3.2.1 then stop the roll out, now 12.3.3 is on the radar and a lot of us are still suck on 12.3 baked into 2023.x main branch
I feel so blessed on 12.3.2.1 rn.Got to love when stuff like this happens, they start the roll out to 12.3.1 then stop the roll out, start roll out to 12.3.2, then stop the roll out, start the roll out to 12.3.2.1 then stop the roll out, now 12.3.3 is on the radar and a lot of us are still stuck on 12.3 baked into 2023.x main branch
So basically after all the excitement over the various government agencies investigating Tesla, and FSD haters claiming it was the end of the road for Tesla, and yada yada, we get (drum roll) ... a new word added to the name!!
Excuse me, I have to sit down a moment, I'm feeling faint. I know I'll sleep better in my bed tonight.
(not saying you were a hater or anything @diplomat33 , just a general comment to the thread)
EVNow
Well-Known Member
I was in particular wondering what the wording here in app will:
- Autosteer (Beta)
- Full Self-Driving (Beta)
Are both upgraded to Supervised in 2024.3.10? Or will basic "Autosteer" remain in beta forever?
It is now mandatory to type FSDS instead of FSDb
After the holiday update and before 12.3, my 2018 m3 did not honor continuous torque and when I got a nag, I had to torque in the reverse direction for a second or so. Try that.
With 12.3, no nags with continuous torque.
I'll likely replace my calling it FSDbollocks with FSDshit.
Similar threads
- Article
