-
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
I have noticed no real difference. I don't think there will be any large behavior changes until we get 12.4.
Not only elderly people but also people who may not be able to drive a car for the entire life time (unexpected illness for example). People paid 4k, 6k, 9k, 12k, 15k if different times. Maybe Tesla should allow one time to transfer and reduce the the price for the next car depending how much people paid for FSD.
Last edited:
This is 2024.3.15
Can someone currently on 2024.3.10 check how big their AP model is? I didn’t notice any changes to driving behavior.
Software -> Service -> Infotainment -> Software -> Autopilot Data Bank
I remember bank B was like 1.73gb a while back.
Last edited:
Still nothing here yet, I assume the validation for my specific vehicle build is low on their priority because it only matches Model X built from January 2023 - February 2023 (2023 model year but still has USS and HW3)
I haven't tried 12.3.4 on the freeway yet but for me 12.3.3 was a freeway lane ping-ponger.
Read your release notes. It is ONLY one sentence. There is NO V12 stack on the freeway. It is V11 stack. V12 is "city streets".
PianoAl
Active Member
I haven't had such a bad experience since then, but I've been more wary. I think I'd pressed the accel pedal before that turn, and it hadn't slowed down. Can't say if newer version acts differently.
I saw a California Highway Patrol car did that on freeway 15 in San Diego last night. I had to disengage FSD.
I didn't notice any improvements with v12.3.4. If anything it felt a bit more indecisive. For one controlled intersection 2 lane left turn there was a second or so of stuttering starts/stops as if it wasn't sure what to do and there were other cars in the left turn lane with no issues. Shortly after that left turn it went into the adjacent so lane positioning is as bad as ever. Speed control continues to be a PITA. Turn signal still initiates two neighborhood blocks early - you'd think vision only would be vision only but apparently not so much with respect to turn signals, braking, accelerating, stop sign creep, and even some lane selection where 300k lines of C++ have apparently been replaced with simulated training data.
I originally expected slight v12.3.4 improvements given they released it to the usual youtubers but now it just feels like they wanted everyone on the same release.
I originally expected slight v12.3.4 improvements given they released it to the usual youtubers but now it just feels like they wanted everyone on the same release.
There are roads which the system does not recognize as highways but realistically are in fact highways. Navigate on Autopilot (which only works on highways) has this same quirk. I believe it's a mapping issue (rather than a real-time perception issue) because the navigation system advises you at the trip-planning stage which roads (i.e. highways) are eligible for Navigate on Autopilot. I.e. it has already determined if a road is a "highway" before the car has had a chance to "see" the road.
For example, Route 17 in NJ (3 lanes in each direction, concrete median, entrance and exit ramps, merge lanes, shoulder lanes, speeds up to 55 MPH) is not recognized as a highways by either NoA or FSD. You can tell v12 is running on the highway instead of v11 because of the differences in the visualization pane. It's an interesting way to see how v12 behaves on highways, but the performance is a huge step back from v11 and it becomes obvious why v12 is not designed to run on highways. I wish we could manually switch to v11 for these cases because v12 is dangerous on highways. It rarely drives fast enough, switches lanes frequently for no good reason (even with Minimal Lane Changes turned On), and most importantly it has trouble completing a lane change without wavering back and forth.
PianoAl
Active Member
On a particular section of road, v12.3.3 would consistently slow down at several spots. Yesterday, still on 12.3.3, the car drove at the MAX speed without slowing, almost as if it had learned from my pressing the accelerator.
A surprising amount of inconsistency for a computer. If I'd installed 22.3.4, I'd have cheered, "Yay. Fixed!"
A surprising amount of inconsistency for a computer. If I'd installed 22.3.4, I'd have cheered, "Yay. Fixed!"
EVNow
Well-Known Member
Were there other cars around? FSD seems to take cues from other cars.
EVNow
Well-Known Member
Beginning to feel quick releases are because of an order from Musk rather than any real improvements.
CWhite
2020 Model S LR+
Talk about a bummer. Has anyone had an issue with installing on a legacy car? Was so happy to finally get V12 for my 2020 Model S. Clicked install and it went to 30% and seemed to stall. Didn’t have an option so I just turned in for the night. Next morning the app showed it was still at 30%. Went to the car and nothing works except the key for to unlock/lock. Screens are dead, no climate, nothing. Contacted Tesla and after them checking remotely they said they are sending tow truck to my house. 30 minutes later my car is leaving. To their credit they were super responsive. Hard to believe the update could brick my car. Ruined 4 years of 100% total reliability. Hopefully Monday will get it back, I am going to insist they install the software while it is there.
FSDtester#1
Craves Electrolytes
Not so sure about that, no matter what destination I input on 12.3.4 it takes me to a strip club...
Edit: I was corrected by @Joboo7777 , Gentlemen's Club.
I need to learn to be more PC.. thanks buddy!
Last edited:
PianoAl
Active Member
Similar threads
- Article
