FSD v14.2.2.2 (Update 2025.45.7) now installing - Release Notes Added

[BeFamousVideo]

I'm excited about the FSD advancements in the last 18 months. When talking to non Tesla people they have no clue about what it is like to be a Captain and monitor the driving and not babysit the steering wheel and pedals. Current version of FSD might actually be a better driver than me now.
I saw a feature on the app or truck interface that has the 14v total miles driven on FSD.

Sponsored

 

[Spartacus]

fixed a small problem on a really narrow road that leads to the beach. Before I had to take over and explained each time it was to make room for oncoming traffic. Now it moves the outside wheels to the edge of the road as the oncoming driver must do. Very nice

 

[Garee]

I hope it fixes it trying to park in my neighbor’s driveway instead of my own.

I had the same problem only once or twice, it does not do that anymore

 

[Gigahorse]

Since Robotaxis are still geofenced, they probably use a model that's focused on their area only (no need to handle international-style lanes/signs/etc. or anything that doesn't exist outside of that relatively small area they drive in).

Yea, the fenced area is pretty big though, FSD that is in my truck now 14.2.2.2 seems a LONG way away from me being able to take a nap in the back or have the truck be a robotaxi and go pick up my kid from practice.

 

[Sandro.natale]

Release Notes:

Tesla Roll Outs FSD V14.2.2.2: A Look at the Improvements

Polished Intuition
The standout characteristic of this latest version, which is now rolling out to the fleet at larger after being with early-access testers for less than 48 hours, is the elimination of hesitation. In complex environments where v14.2.2 or v14.2.2.1 would hesitate or stutter, the new build exhibits more confidence.

That confidence likely comes from the additional polish that Tesla’s AI team has placed on this build, working over the holiday season. It also applies to some improvements to Speed Profiles and how they handle traffic around them, as well as improvements to highway exits.

Better Perception
Perhaps the most compelling argument for this stopgap release is the refinement of the perception stack. Tesla has focused on improving the stack to better find and predict what vulnerable road users like pedestrians and cyclists will do next.

Early access user testing in parking garages noted that the car was preparing for pedestrian traffic behind blind corners - essentially moving from a reactive posture (slamming the brakes) to a predictive one (slowing down smoothly ahead of time).

Nag Fixed - Again
One of the biggest positives of this update has been reducing the false positives in the Driver Monitoring System, which FSD v14.2.2.1 had dialed up to the max. The previous iteration was nagging drivers for every little head movement or hands not being completely visible or free.

Now, that appears to be gone, allowing for the same smooth, hands-free operation that V14.2 originally debuted with.

The Takeaway
While FSD v14.2.2.2 isn’t the massive reasoning upgrade and sentience we were looking for with FSD v14.3, it is still an extremely polished build that has come a long way from the initial releases of FSD v14.

It also represents something else that is more important than a big tech leap over the holidays: stability. Tesla has ironed out many of the erratic behaviors in previous builds to give everyone a much smoother and more stable build of FSD.

I hope this version also addresses driveways with automatic gates. On my second try of FSD driveway parking it rammed my gate as it was opening. Didn’t wait for the gate to fully open.

 

[georgek43]

Release Notes:

Tesla Roll Outs FSD V14.2.2.2: A Look at the Improvements

Polished Intuition
The standout characteristic of this latest version, which is now rolling out to the fleet at larger after being with early-access testers for less than 48 hours, is the elimination of hesitation. In complex environments where v14.2.2 or v14.2.2.1 would hesitate or stutter, the new build exhibits more confidence.

That confidence likely comes from the additional polish that Tesla’s AI team has placed on this build, working over the holiday season. It also applies to some improvements to Speed Profiles and how they handle traffic around them, as well as improvements to highway exits.

Better Perception
Perhaps the most compelling argument for this stopgap release is the refinement of the perception stack. Tesla has focused on improving the stack to better find and predict what vulnerable road users like pedestrians and cyclists will do next.

Early access user testing in parking garages noted that the car was preparing for pedestrian traffic behind blind corners - essentially moving from a reactive posture (slamming the brakes) to a predictive one (slowing down smoothly ahead of time).

Nag Fixed - Again
One of the biggest positives of this update has been reducing the false positives in the Driver Monitoring System, which FSD v14.2.2.1 had dialed up to the max. The previous iteration was nagging drivers for every little head movement or hands not being completely visible or free.

Now, that appears to be gone, allowing for the same smooth, hands-free operation that V14.2 originally debuted with.

The Takeaway
While FSD v14.2.2.2 isn’t the massive reasoning upgrade and sentience we were looking for with FSD v14.3, it is still an extremely polished build that has come a long way from the initial releases of FSD v14.

It also represents something else that is more important than a big tech leap over the holidays: stability. Tesla has ironed out many of the erratic behaviors in previous builds to give everyone a much smoother and more stable build of FSD.

STABLE? REALLY?
downloaded and installed FSD v14.2.2.2 last night. all sounds great in the release notes, but except for continuing the terrible speed management introduced in the first version of FSD14, my FSD had been working pretty well before the update. This afternoon we took a 2 mile drive to meet with the veterinarian (no animals with us). On this two miles, which the CT has navigated pretty well hundreds of times over the past year, it

1. Blew through a stop sign (I had to slam on the brakes, but it had gotten half way into the traffic lane, getting me a few really dirty looks, but fortunately not a collision)

2. Turned into the opposing lane after a stop sign (luckily no cars coming and I quickly disengaged and turned back into the correct lane) but after re-engaging it decided the speed limit was 45 instead of the posted 25. Disengaged again

3. Tried to turn onto a golf cart path- no idea why, that’s a totally new behavior, I quickly disengaged, - then when re-engaged just a few hundred feet away it tried to rapidly stop at a phantom stop sign

4. Tried to turn into my neighbors’ driveway instead of mine (it’s been doing that since the last update, so I‘ve learned to just disengage when I’m close to home. I’d hoped this was fixed in 2.2.2 so I let go itself after the update, but no, it shows my correct driveway on the map, then turns several hundred feet before my house into the driveway before. Hey, at least the signal turns on for the correct side of the street now- I guess that’s progress, but it’s certainly not a confidence builder in E2E)

5. Got me chewed out by my wife who is now insisting that I never use FSD in our neighborhood, and she’d prefer that I only use it on the highway, if at all. She’s very clearly stated her preference that I never use FSD when she’s in the truck

all this within 2 miles up and 2 miles back on roads and streets it has been navigating pretty well for over a year.

my experience today indicates that at least for my CT, no, it is not a “much smoother and more stable build”, and the erratic behaviors are worse. In fact I’ve never experienced a couple of those in over a year of FSD use.

way to go developers- this update is not going to increase FSD usage, at least not in my household

my wife who is my daily passenger wants us to go back to either of our previous EVs- Cadillac or Mercedes- as they are much nicer, more luxurious, much more comfortable vehicles with much better build quality, and they also self-drive on the highway- the Tesla appeal is ‘self driving almost anywhere’, especially in neighborhoods.

FSD14 dropping the speed scroll wheel, and switching to exclusively depending on speed profiles pretty much axed safely driving in neighborhoods. Constantly flipping through speed profiles to try to get an approximation of safe and desirable speed is more trouble that just driving the vehicle myself. It requires either accepting an unsafe speed- either too slow or illegally fast, or fussing with way too much user input, and much more so than FSD13.

More importantly, the erratic behavior we experienced today is plain dangerous enough to stop using FSD altogether. As an actual owner, I’d hardly describe FSD14.2.2.2 as an “extremely polished build”. That’s someone’s hopeful fantasy of the future, not today’s reality.

I’ll hold out for FSD14.3, hoping the decision makers wise up, and at least return the driver control of max speed with the scroll wheel as an option. Tesla really must try harder to make the FSD less frustrating and more relaxing as the legally designated ‘driver assist’ system that it actually is, instead of prematurely pushing a dream of full autonomous driving while taking away the currently required and much needed driver oversight.

I’d love to have my vehicle chauffeur me safely, comfortably and at legal speeds from home to destination, and one day it just might. But today is not that day.

 

[Aerospace2061]

I hope it fixes it trying to park in my neighbor’s driveway instead of my own.

 

[Aerospace2061]

STABLE? REALLY?
downloaded and installed FSD v14.2.2.2 last night. all sounds great in the release notes, but except for continuing the terrible speed management introduced in the first version of FSD14, my FSD had been working pretty well before the update. This afternoon we took a 2 mile drive to meet with the veterinarian (no animals with us). On this two miles, which the CT has navigated pretty well hundreds of times over the past year, it

1. Blew through a stop sign (I had to slam on the brakes, but it had gotten half way into the traffic lane, getting me a few really dirty looks, but fortunately not a collision)

2. Turned into the opposing lane after a stop sign (luckily no cars coming and I quickly disengaged and turned back into the correct lane) but after re-engaging it decided the speed limit was 45 instead of the posted 25. Disengaged again

3. Tried to turn onto a golf cart path- no idea why, that’s a totally new behavior, I quickly disengaged, - then when re-engaged just a few hundred feet away it tried to rapidly stop at a phantom stop sign

4. Tried to turn into my neighbors’ driveway instead of mine (it’s been doing that since the last update, so I‘ve learned to just disengage when I’m close to home. I’d hoped this was fixed in 2.2.2 so I let go itself after the update, but no, it shows my correct driveway on the map, then turns several hundred feet before my house into the driveway before. Hey, at least the signal turns on for the correct side of the street now- I guess that’s progress, but it’s certainly not a confidence builder in E2E)

5. Got me chewed out by my wife who is now insisting that I never use FSD in our neighborhood, and she’d prefer that I only use it on the highway, if at all. She’s very clearly stated her preference that I never use FSD when she’s in the truck

all this within 2 miles up and 2 miles back on roads and streets it has been navigating pretty well for over a year.

my experience today indicates that at least for my CT, no, it is not a “much smoother and more stable build”, and the erratic behaviors are worse. In fact I’ve never experienced a couple of those in over a year of FSD use.

way to go developers- this update is not going to increase FSD usage, at least not in my household

my wife who is my daily passenger wants us to go back to either of our previous EVs- Cadillac or Mercedes- as they are much nicer, more luxurious, much more comfortable vehicles with much better build quality, and they also self-drive on the highway- the Tesla appeal is ‘self driving almost anywhere’, especially in neighborhoods.

FSD14 dropping the speed scroll wheel, and switching to exclusively depending on speed profiles pretty much axed safely driving in neighborhoods. Constantly flipping through speed profiles to try to get an approximation of safe and desirable speed is more trouble that just driving the vehicle myself. It requires either accepting an unsafe speed- either too slow or illegally fast, or fussing with way too much user input, and much more so than FSD13.

More importantly, the erratic behavior we experienced today is plain dangerous enough to stop using FSD altogether. As an actual owner, I’d hardly describe FSD14.2.2.2 as an “extremely polished build”. That’s someone’s hopeful fantasy of the future, not today’s reality.

I’ll hold out for FSD14.3, hoping the decision makers wise up, and at least return the driver control of max speed with the scroll wheel as an option. Tesla really must try harder to make the FSD less frustrating and more relaxing as the legally designated ‘driver assist’ system that it actually is, instead of prematurely pushing a dream of full autonomous driving while taking away the currently required and much needed driver oversight.

I’d love to have my vehicle chauffeur me safely, comfortably and at legal speeds from home to destination, and one day it just might. But today is not that day.

I agree with wanting the max speed setting back. Now it seems both the scroll wheel up-down spin and the side-to-side push does the same thing by changing the speed profile mode. It would be best to change the up-down spin back to the max speed adjust and the side-to-side push to change the speed profile mode in my opinion.

 

[Jwadoc]

Holiday update messed up FSD. 14.2.2 fixed it. 14.2.2.2 ruined it again. Not doing any updates after the next for 2 or 3 weeks after they come out to avoid these issues. I have to reset DAS and camera calibration to make it work for the next drive then fails again.

 

[Aerospace2061]

I hope this version also addresses driveways with automatic gates. On my second try of FSD driveway parking it rammed my gate as it was opening. Didn’t wait for the gate to fully open.

Sorry that happened, not good. May be wishful thinking and if the footage got recorded but any word from the Tesla service center or Tesla collision center if it will be covered due to in FSD…

 

[Carlos Thomas]

For the first time with the latest update it parked in my garage, which requires about a 100 foot run, thru a porte cochere and then into the garage.

 

[Fugue]

For the first time with the latest update it parked in my garage, which requires about a 100 foot run, thru a porte cochere and then into the garage.

What arrival option do you use?

Nice looking house, BTW.

 

[Carlos Thomas]

What arrival option do you use?

Nice looking house, BTW.

I select Parking Garage.

 

[MilliVanilli]

FSD v14.2.2.2's speed controls are absolute trash. No one wins. People who want absolute speed control don't get it. People who want "intelligent" speed control instead get a random number generator for the speed limit.

I just completed 300+ miles but gave up on FSD for the last 100 because I realized I was spending more effort changing profiles than to just drive it myself.

On a clear, open stretch of highway with a 55 MPH speed limit:

• Standard: Speed drifts up to 68 and after a random amount of time, FSD "realizes" it's going too fast and rapidly decelerates back to 62. Repeat this over and over. The weirdest is when it's passing a car and suddenly decelerates when next to it.
• Mad Max: Speed increases slowly until it got to 80 MPH at which point I canceled FSD.

I just gave up on all secondary roads because Standard was driving 2-3 MPH below the speed limit, and Mad Max would get up to reckless-driving ticket range.

It still occasionally put on the blinker without changing lanes. And self-parking is still hilariously bad.

The good news is that this encourages me to spend more quality time with my other cars.

 

[DrShah]

Did anyone notice how wrong the maps were on the version prior to this? I feel like my CT took some major steps backwards, hopefully this update will be better.

Sponsored