Tesla Full Self-Driving v14.3.2 began rolling out to some owners earlier this week, and there are some notable improvements that came with this update.\n<\/p>\n
There were two new lines of improvements in the release notes: one addressing Actually Smart Summon (ASS), and another that now allows drivers to choose a reason for an intervention via a small menu during disengagement.\n<\/p>\n
Overall operation saw a handful of slight improvements, especially with parking performance, which has been the most notable difference with the arrival of FSD v14.3. However, there are still some very notable shortcomings, most notably with region-specific signage and navigation.\n<\/p>\n
Tesla Assisted Smart Summon (ASS) improvements<\/p>\n
There are noticeable improvements to ASS operation, which has definitely been inconsistent in terms of performance. Tesla wrote in the release notes for v14.3.2:<\/p>\n
\u201cUnified the model between Actually Smart Summon, FSD, and Robotaxi for more capable and reliable behavior.\u201d\n<\/p>\n
As recently as this month, I used Summon with no success. It had pulled around the parking lot I was in incorrectly, leaving the range at which Summon can be operated<\/a> and losing a signal while moving in the middle of the lot.\n<\/p>\n This caused me to sprint across the lot to retrieve the vehicle:\n<\/p>\n It was pouring when I left the gym so I tried to Summon my Model Y\n<\/p>\n It turned the opposite way and drove out of range, stopping here and forcing me to walk even further across the lot in the rain for it \ud83e\udd23<\/p>\n One day pic.twitter.com\/iD10c8sriB<\/a>\n<\/p>\n \u2014 TESLARATI (@Teslarati) April 5, 2026<\/a><\/p>\n Unfortunately, Summon was not dependable or accurate enough to use regularly<\/a>. It appears Tesla might have bridged the gap needed to make it an effective feature, as two tests in parking lots proved that Summon was more responsive and faster to navigate to the location chosen.<\/p>\n It also did so without hesitation, confidently, and at a comfortable speed. I was able to test it twice at different distances:\n<\/p>\n \ud83d\udea8 Tesla FSD v14.3.2 ASS testing part 1\n<\/p>\n This was a significant improvement than recent tries using ASS. The parking lot was pretty empty but getting it to come to my location in one singular motion and maneuver was encouraging. https:\/\/t.co\/vF7TS48GGV<\/a> pic.twitter.com\/sYt8tyHgNn<\/a>\n<\/p>\n \u2014 TESLARATI (@Teslarati) April 23, 2026<\/a><\/p>\n Tesla Full Self-Driving v14.3.2 ASS testing part 2 https:\/\/t.co\/lxfWfnLUxf<\/a> pic.twitter.com\/2R0r3ohI3M<\/a>\n<\/p>\n \u2014 TESLARATI (@Teslarati) April 23, 2026<\/a><\/p>\n I plan to test this more thoroughly and regularly through the next few weeks, and I avoided using it in a congested parking lot initially because I have not had overwhelming success with Summon<\/a> in the past. I wanted to set a low baseline for it to see if it could simply pull up to the place I pinned in the Tesla app.\n<\/p>\n It was two for two, which is a big improvement because I don\u2019t think I ever had successful Summon attempts back-to-back. It just seems more confident than ever before.<\/p>\n New Disengagement Categories<\/p>\n This is a really good idea from Tesla, but there are some issues with it<\/a>. The categories you can select are Critical, Comfort, Preference, and Other.\n<\/p>\n I think the reasons why people choose to take over would be a better way to prompt drivers, like, \u201cTraveling Too Fast,\u201d \u201cIncorrect Maneuver,\u201d \u201cNavigation Error,\u201d would be more beneficial.\n<\/p>\n I say this because it seems that how we each categorize things might be different. For example, I shared a video of an intervention because the car had navigated to an exit to a parking lot and put its left blinker on, despite left turns not being allowed there.\n<\/p>\n I disengaged and chose Critical as the reason; it\u2019s not a comfort issue, it\u2019s not a preference, it\u2019s quite literally an illegal turn, and it\u2019s also dangerous because it cuts across several lanes of traffic and is 180 degrees.<\/p>\n I chose to label this Navigation error as \u201cCritical\u201d while testing FSD v14.3.2\n<\/p>\n Here\u2019s why: \u2014 TESLARATI (@Teslarati) April 23, 2026<\/a><\/p>\n Some said I should not have labeled this as Critical, but that\u2019s the description I best characterized the disengagement as.<\/p>\n Categorizing interventions is a good thing, but it\u2019s kind of hard to determine how to label them correctly.\n<\/p>\n Inconsistency with Regional Traffic Patterns<\/p>\n Tesla Full Self-Driving is pretty inconsistent with how it handles regional or local traffic patterns and road rules. The most frequent example I like to use is that of the \u201cExcept Right Turn\u201d stop sign, which has become a notorious sighting on our social media platforms.\n<\/p>\n In the initial rollout of v14.3<\/a>, my Model Y successfully navigated through one of these stop signs with no issues. However, testing at two of these stop signs yesterday proved it is still not sure how to read signs and navigate through them properly.\n<\/p>\n \ud83d\udea8 Tesla FSD v14.3.2 attempts the \u201cExcept Right Turn\u201d stop sign: https:\/\/t.co\/W5MjAybaNK<\/a> pic.twitter.com\/P6oeUsk4PN<\/a>\n<\/p>\n \u2014 TESLARATI (@Teslarati) April 23, 2026<\/a><\/p>\n Off camera, I approached another one of these signs and felt the car coming to a stop, so I nudged it forward with the accelerator pedal pressed.\n<\/p>\n This helped the car go through the sign without stopping, but I could feel the bucking of the vehicle as the car really wanted to stop.\n<\/p>\n Musk said on the earnings call earlier this week that unsupervised FSD would probably be available in some regions before others, including a state-to-state basis in the U.S.<\/p>\n \u201cIt\u2019s difficult to release this like to everyone everywhere all at once because we do want to make sure that they\u2019re not unique situations in a city that particularly complex intersection or \u2014 actually, they tend to be places where people get into accidents a lot because they\u2019re just \u2014 perhaps there\u2019s \u2014 and like I said, an unsafe intersection or bad road markings or a lot of weather challenges. So I think we would release unsupervised gradually to the customer fleet as we feel like a particular geography is confirmed to be safe.\u201d\n<\/p>\n This could be one of those examples that Tesla just has to figure out.\n<\/p>\n Highway Operation<\/p>\n Full Self-Driving is already pretty good at routine roadway navigation, so I don\u2019t have too much to report here<\/a>.\n<\/p>\n However, I was happy with FSD\u2019s decision-making at several points, including its choice not to pass a slightly slower car and remain in the right lane as we approached the off-ramp:<\/p>\n \ud83d\udea8 Tesla FSD v14.3.2 highway operation: generally happy with the performance here, especially behavior near the exit\n<\/p>\n Love that the car got over in the right lane after its final pass, and stayed there as the off ramp was approaching https:\/\/t.co\/qVRVhg6XGR<\/a> pic.twitter.com\/1ELwHf2XKS<\/a>\n<\/p>\n \u2014 TESLARATI (@Teslarati) April 23, 2026<\/a><\/p>\n Better Maneuvering at Stop Signs<\/p>\n Many FSD users report some strange operations at stop signs, especially four-way intersections where there is a stop sign and a line on the road, and they\u2019re not even with one another.<\/p>\n I experienced this quite frequently and found that FSD would actually double stop: once at the stop sign and again at the line.\n<\/p>\n This created some interesting scenarios for me and I had many cars honk at me when the second stop would happen. Other vehicles that had waved me on to proceed through the intersection would become frustrated at the second stop.\n<\/p>\n FSD seems to have worked through this particular maneuver:\n<\/p>\n \ud83d\udea8 Tesla FSD v14.3.2 with a singular stop at the correct spot\n<\/p>\n No double stopping anymore in my experience https:\/\/t.co\/Wd0TaNjc1R<\/a> pic.twitter.com\/CdQPvJHaAM<\/a><\/p>\n
\u2705 This intervention wasn\u2019t \u201cpreference,\u201d as the maneuver FSD routed was illegal
\u2705 If a police officer saw this maneuver, it would result in a ticket https:\/\/t.co\/znhHb4haAo<\/a> pic.twitter.com\/bZOiLwWmQa<\/a>\n<\/p>\n