-
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 has decision wobble fsd jerky driving fsd late deceleration fsd sometimes may not detect train crossings fsd stops too early too quickly fsd stops too far behind line fsd tailgating in city streets
v12 is not designed for highways and performs poorly on them. It's supposed to automatically switch to v11 for highways, but some highways are incorrectly detected as surface streets, so the switchover doesn't occur. The most obvious way to tell which version is running is to have the Auto Max Speed setting on. If the Auto Max icon stays on while you are on the highway, then it did not switch to v11 because Auto Max only exists on v12.
This makes it hard for FSD to evade police in southern CA.
www.cbsnews.com
Anaheim police roll out new Tesla patrol vehicles
The Anaheim Police Department will roll out its new fleet of Tesla patrol SUVs next Monday.
www.cbsnews.com
AlanSubie4Life
Efficiency Obsessed Member
The auto speed behavior will also be very different if you're in manual model (not using Auto Max). (Meaning very different behavior when using v12 stack on freeway vs. v11 stack as intended.) So Auto Max and Manual behavior will be the same in this regard. So pretty easy to tell in manual mode as well, because it's the same as Auto Max (except for the Auto Max display and the cap speed). But yes the Auto Max display is an instant tell which does not exist in that area in Manual Mode.
You can look at the tentacle length, it's pretty easy to tell from that regardless of mode. Also an instant tell.
Last edited:
As pointed out highway is still V11 so there should be very little difference on highways compared to past builds for you.
Was there anything in V12 that was better than V11 on city/streets or are you just highlighting the negative?
According to Teslascope they're still shipping V11 highway code improvements in V12 builds, so it could drive differently now
This is something I commented on when V12 first came out.. the rumble bumps, those little round disks on the right or left side of a lane, or the groove carve outs in the asphalt that are meant to make a vibration and noise to indicate to the driver that they are OUT of a lane.. sometimes these things are meant for when the markings may be covered by like snow, or sheen, and sometimes they are meant to just ALERT the driver that they are drifting outside of the drivable lane… I do not think that FSD has ANY way of understanding or interpreting these - and that’s based on the fact that they car will drive over them and just on them in a bike lane or other marking and not seem to make ANY effort to move back into the lane to avoid the sound/noise/disturbance..
I don’t know that VISION alone has some way of interpreting this, or if the internal MIC might, or maybe just wheel/vibration feedback. but at least for now it doesn’t appear that this sort of on the road indicator has any effect on the FSD AI.
I’ve seen this on both surface streets, and on say Hwy 17 as the original poster mentioned, so it seems it isn’t having any input for V11 or V12.
Not all highways trigger v11. I've never driven on the highway in question so somebody else would have to verify.
Other indicators would be the presence of status messages like "changing lanes to follow route" (does not exist in v12) and while changing lanes the target lane will be highlighted in light blue if and only if on v11.
I want to forfeit 23.3.15 if I'm in queue to get in lieu of 24.8.x/12.3.x next week.
Yes, it is Limited Access Highways the same as v10.x to NoA was.
Hey can you check under service mode what value is under Data Bank A for autopilot on 12.3.3 please. I realized we can check if there was any change to the model this way.
zoomer0056
Active Member
Go to vehicle settings list and hit software. Press and hold the model name for 3 consecutive seconds and let go. Enter the word “Service” then follow the above path.
JulienW:I want to forfeit 23.3.15 if I'm in queue to get in lieu of 24.8.x/12.3.x next week.
I'm dying of thirst! Everyone else has plenty of water but my cup runneth dry! I don't think I can last much longer, I must have water!
Elon:
Okay already, here's a nice tall glass of water...drink up and be well.
JulienW:
What... I only drink arctic glacier spring with light ice. Take it away!
I have 23.3.10/12.3.3 and going to 23.3.15/12.3.4 is about ⅛ of a thimble of water improvement and probably mostly placebo.
12.3.4 first drive showed notable improvement while drive on two lane road with no lane markings. It kept to its own side for a change! Also noticed the ping pong in lanes is much improved. I notice much fewer nags also.
There still are trouble areas to be sure but at least these improvements made the ride less stressful for me.
There still are trouble areas to be sure but at least these improvements made the ride less stressful for me.
Last edited:
Ben W
Chess Grandmaster (Supervised)
This was with the newer car (2022 Model Y), though I've noticed the same issue on the older car (2017 Model 3) as well.
I searched through the dashcam footage from the Model Y, and indeed the glare is pretty terrible. I'll try cleaning the inner glass and see if it helps. Thanks for the suggestion!
It does bug me that when the warning pops up saying "Camera occluded/blocked/blinded", it doesn't specify WHICH camera! I sort of assumed it wasn't the front camera because the housing and wipers should keep them clean, but evidently not!
Last edited:
After the release of v12 of FSD, I read a lot of evaluations of v12 to be better and a lot of evaluations of v12 to be bad. I was puzzled a bit, for my experiences have been better (I have only tested v12 on my neighborhood local city streets).
Then I realized that I have not evaluated v12 on two lane curvy Highways with turn in, turn out, occasionally signals, etc. like part of Route 152).
The path of v11 FSDb development is different from v12 FSDS.
For v11, it was a merge of the FSD v11 City and FSD v11 Highway codes. FSD v11 Highway was a re-code of the Old original Divided Highway code (AP, TACC, NOA etc) using the FSD v11 City code method. v11 City code always have problems with unmarked roads, narrow streets, speed control on local roads etc. but was pretty good on two lane curvy Highways (part of Route 152 using the v11 City code).
Now, that v12 coding method have resulted in pretty good City street driving, but have problems with two lane curvy Highways. (I have not tested to see if its worst then the v11 City code).
Then I realized that I have not evaluated v12 on two lane curvy Highways with turn in, turn out, occasionally signals, etc. like part of Route 152).
The path of v11 FSDb development is different from v12 FSDS.
For v11, it was a merge of the FSD v11 City and FSD v11 Highway codes. FSD v11 Highway was a re-code of the Old original Divided Highway code (AP, TACC, NOA etc) using the FSD v11 City code method. v11 City code always have problems with unmarked roads, narrow streets, speed control on local roads etc. but was pretty good on two lane curvy Highways (part of Route 152 using the v11 City code).
Now, that v12 coding method have resulted in pretty good City street driving, but have problems with two lane curvy Highways. (I have not tested to see if its worst then the v11 City code).
