Connect with us
tesla-fsd-beta-10.69.3.1-defeat-device tesla-fsd-beta-10.69.3.1-defeat-device

News

Tesla FSD Beta 10.69.3.1 update reviews from Beta testers

Credit: teslaphotographer/Instagram

Published

on

Tesla Full Self-Driving (FSD) Beta 10.69.3.1 has been out for some time now, and Teslarati talked to a few beta testers about the update. 

Below are some notes and observations about v.10.69.3.1 from Tesla FSD Beta Testers. 

FSD Beta 10.69.3.1 and Lanes

Lane selection has been one of the issues that most FSD Beta testers bring up when they talk to Teslarati. Before 10.69.3.1, FSD Beta reportedly had trouble understanding when to switch lanes, which one to switch to, or when to remain in a lane. FSD Beta testers are still experiencing lane selection issues

“Not only has lane selection in anticipating a turn been a step back for me, lane selection whilst performing dual lane left-hand turns still suffer. The car doesn’t stay in its assigned lane but drifts. This does not happen on right turns,” said Les, a long-time FSD Beta tester.

Advertisement

“Lane selection still has issues. Most of the time it’s ok, but occasionally, it does strange things like changing into the right lane momentarily, then back to the left when there is an upcoming left-hand turn,” noted FSD Beta tester Sandy.

Turn Issues in FSD Beta 10.69.3.1 

Les and fellow FSD Beta tester Sandy mentioned other lane issues related to turns. Les noted that one of the biggest step back with FSD Beta 10.69.3.1 occurs when the car faces an upcoming turn. 

“On previous builds, the car would only occasionally move in the opposite lane direction of an upcoming turn. On this build, virtually every turn I had upcoming, when the car got within half a mile of said turn, it would signal and move into the lane of the opposite direction,” Les said.

“Virtually every right turn I’ve had upcoming, the car, inexplicably, signals and changes into the left-hand lane. Same for left-hand turns, within half a mile out the car signaled and changed into the right-hand lane. Confounding to say the least, to the point of comedy,” he added. 

Advertisement

Sandy noticed that his car requires interventions or disconnects at stop signs sometimes. In the past, other FSD Beta testers have mentioned that their vehicle experiences jerky movements or their signal lights turn off and on during intersections, traffic lights, and stop signs. It’s as if the car is deciding whether the driver wants to turn or not. 

“Following and lane changes seem smoother and more natural,” said Sandy. “However, it still has issues that require intervention/disconnects. When it creeps at stop signs, it can make jerky movements with steering wheel and, imo, it creeps to slowly and takes too long before proceeding.”

Mixed Reviews for 10.69.3.1

As with all of Tesla’s FSD Beta updates, there have been a few good reviews and bad ones. Beta testers tend to focus on the issues, as it is their responsibility to report them so Tesla can improve FSD. However, testers also report significant improvements they see during their drives. 

In the case of 10.69.3.1, it seems like FSD Beta received mixed reviews. Some testers believed that the update significantly improved the advanced driver assist software while others thought it was a step back. 

Advertisement

“I have tested the 10.69.3.1 build on my Model Y, and it’s a giant leap forward from builds prior to 10.69,” observed Tony, a Model Y owner and a member of the FSD Beta program. 

Tony noted that the biggest changes were improvements to acceleration, smoother turns, and less necessary steering wheel input. Sandy also observed more improvements with Tesla FSD Beta 10.69.3.1 rather than issues. 

On the other hand, Les believed that v.10.69.3.1 was a step back for FSD Beta. 

“These 10.69.3.1 step backs are the biggest in my FSD Beta testing experience to date. Previous builds have been much better for me. But again, I understand the process; updates are sometimes “2 steps forward and 1 step back.” I still enjoy testing. The product isn’t finished yet,” he said.

Advertisement

Tesla FSD Beta Wide Release

Tesla started the wide release of FSD Beta v.10.69.3.1 in late November. A day after its release, Tesla rolled out FSD Beta to cars with less than 100 Autopilot miles and Safety Scores lower than 80.

The EV maker rolled out FSD Beta V11 to a few testers already. FSD Beta V11 is Tesla’s single-stack update. However, update 10.69.3.1 seems to be rolling out to more testers. 

Tesla also made Full Self-Driving Beta available to anyone in North America who purchases it from their car screen. Now that Tesla has released FSD Beta to anyone in North America interested in trying it out, the company might want to streamline its performance. Based on Teslarati‘s interviews with FSD Beta Testers, the software performs differently based on location, driver, terrain, and other factors.

“Phantom braking on city streets (not highways) returned for me in one bizarre instance; it wasn’t the sudden hard kind of braking, rather this was a new braking behavior that was slow and gradual almost to a stop while I was going straight in the middle lane of a three-lane road. Not at a turn, wasn’t going through an intersection, and the road was clear,” described Les in one instance. 

“There were no cars around me so I let the car do its thing to see what it was doing; it literally started slowing from 40mph to 5mph before I disengaged and accelerated back up to speed. Very weird. I went back to that spot a couple days later and the car didn’t do it. It acted normal,” he explained. 

Advertisement

Tesla Full Self-Driving has not received regulatory approval yet. It still faces a lot of skepticism, especially in terms of safety. Delivering consistent, reliable performances in various driving situations might help it get regulatory approval. 

Are you an FSD Beta tester? Have you tried out V11? If you have, I’d like to hear from you! Contact me at maria@teslarati.com or via Twitter @Writer_01001101.

Maria--aka "M"-- is an experienced writer and book editor. She's written about several topics including health, tech, and politics. As a book editor, she's worked with authors who write Sci-Fi, Romance, and Dark Fantasy. M loves hearing from TESLARATI readers. If you have any tips or article ideas, contact her at maria@teslarati.com or via X, @Writer_01001101.

Advertisement
Comments

Elon Musk

The Boring Company just doubled its tunneling power in Nashville

The Boring Company’s Prufrock MB2 is commissioned and ready to mine beneath Nashville’s streets.

Published

on

By

boring-company-prufrock-1-2

The Boring Company’s second tunnel boring machine, Prufrock MB2, is officially ready to dig in Nashville. The company confirmed the news on X, posting: “Prufrock-MB2 is ready to mine in Nashville! MB2 commissioning is complete, including the brief 11 rpm rotation shown here. Will MB2 catch up to MB1, who had quite the head start? And Prufrock-MB3 ships in August!”

MB2 arrives with meaningful improvements over its predecessor. Lessons learned from the launch and operation of MB1 have already been applied to MB2 to improve efficiency and prepare the machine for launch.

Traditional tunnel boring machines operate in a stop-and-go cycle, digging roughly five feet, halt, erect precast concrete segments to line the tunnel wall, then resume. That repeated interruption is one of the main reasons conventional tunneling is slow and expensive. Prufrock is designed to install the tunnel liner simultaneously with mining, eliminating the need to stop every five feet. The machine also skips the need for excavated launch pits. Prufrock arrives on a truck, tilts down, and launches into the ground within 24 hours. And when the tunnel is complete, it emerges from the ground and drives to its next launch site on a trailer, eliminating the need for expensive cranes or pit excavation. The machine is also fully electric and runs with zero people in the tunnel during normal operations, controlled remotely from a surface operations center.

It won’t be long before we hear of another major update on The Boring Company’s Music City Loop project – a planned underground transit network beneath Nashville that would move passengers in electric vehicles through a series of tunnels at highway speeds, and bypassing surface traffic entirely. Nashville was selected in part because of its strong rock conditions that suits the Prufrock machines well, and relatively less regulatory hurdles.

Progress has been steady on multiple fronts. All 37 permits and approvals required ahead of tunneling have been obtained, out of 45 total. Key wins include a fully executed TDOT tunnel permit authorizing 25 miles of tunnel, unanimous airport authority approval for a Nashville International Airport station, and the city’s first residential station agreement serving downtown tower residents.

With MB1 already tunneling, MB2 now commissioned, and MB3 shipping in August, Nashville is becoming something of a live proving ground for scaled tunnel boring. The broader ambition is not limited to one city. The Boring Company’s stated goal is to make underground transportation a practical alternative to surface roads across major metro areas. Nashville is one of many cities, including a successful Las Vegas tunnel system, where that idea is being put to the test at real speed.

Continue Reading

News

Tesla urges New Jersey owners to oppose new bill that could block Robotaxi

Published

on

Credit: Grok

Tesla has launched a direct campaign targeting its customers in New Jersey, sending emails that warn of pending legislation that could effectively block true driverless technology in the state.

The email focuses on Senate Bill S.1677 and Assembly Bill A.3968, measures intended to create a three-year autonomous vehicle pilot program but laden with requirements that Tesla argues make unsupervised Robotaxis impossible.

According to the email, the bills impose “restrictions so severe that true driverless deployment would remain illegal.” Specific hurdles include mandates for human safety drivers during operations, multimillion-dollar insurance minimums, reportedly $5 million, and thresholds like 100,000 miles of demonstrated safe autonomous driving before any driverless approval.

Tesla contends these are arbitrary barriers that ignore real-world performance data and favor entrenched competitors over innovative technologies like its Full Self-Driving (FSD) system.

The push comes as Tesla has started expanding Robotaxi operations in states like Texas, where unsupervised vehicles are already providing rides in several cities. New Jersey, by contrast, risks falling behind. The company highlights in the email communication that more than 94 percent of serious crashes result from human error, meaning impairment, distraction, or fatigue. These are all problems that Robotaxis eliminate entirely.

In 2025, New Jersey recorded 582 traffic deaths, underscoring the human cost of delayed adoption.

Tesla’s outreach stresses the transformative potential of robotaxis. For families, they could offer safer school runs without drowsy or distracted drivers. For seniors and people with disabilities, robotaxis promise independence and reliable mobility.

In areas with limited public transit, they could deliver affordable, on-demand transportation, reducing congestion, emissions, and overall transportation costs. Economically, the company warns that restrictive rules could cost New Jersey jobs, innovation investment, and billions in potential growth as autonomous ride-hailing scales elsewhere.

Supporters of the legislation, including Sen. Andrew Zwicker, describe the pilot as a cautious framework with strong safety oversight, including incident reporting, expert task forces, and restrictions in sensitive zones like school areas. They view it as balancing innovation with public protection.

Tesla and pro-AV advocates counter that the bill lacks technology neutrality, creates insurmountable entry barriers for commercial deployment, and prioritizes process over outcomes — effectively functioning as a de facto ban on services like Robotaxi.

This latest clash echoes Tesla’s past battles in New Jersey over direct vehicle sales. The email directs owners to Tesla’s advocacy platform, where they can send customized messages to legislators calling for amendments: outcome-based safety standards, open competition, and clear pathways for fully driverless commercial operations.

As hearings approach, Tesla’s campaign frames the issue as a choice between protecting the status quo and embracing life-saving progress. With robotaxi technology already proving itself in permissive states, New Jersey owners are being asked to ensure their state doesn’t lock out the future of transportation.

Continue Reading

News

Tesla’s Navigation Nightmare: Why the easiest part of FSD might be the hardest

Published

on

Credit: TESLARATI

Turn-by-turn navigation is not new technology.

For over two decades, drivers have relied on Garmin, TomTom, and later smartphone apps like Google Maps and Waze to receive precise, reliable directions. These systems have guided millions safely through unfamiliar cities, highways, and backroads with remarkable effectiveness. They handle real-time traffic, construction detours, and complex intersections with minimal fuss.

Yet Tesla, the company that promised revolutionary Full Self-Driving (FSD), continues to struggle with this foundational capability. As FSD (Supervised) v14.3.4 has started rolling out to cars this week, navigation remains its glaring Achilles’ heel, undermining the entire autonomous vision.

Tesla Summon got insanely good in FSD v14.3.2 — Navigation? Not so much

Tesla’s FSD excels in many driving behaviors—smooth acceleration, confident lane changes in ideal conditions, and responsive handling of visible obstacles. However, when it comes to following a route accurately, the system falters repeatedly.

Owners report wrong turns, missed exits, inefficient routing through local roads instead of highways, phantom speed limit errors, and even directing vehicles to building rear entrances. Interventions for navigation issues often outnumber those for core driving maneuvers. Tesla has begun surveying owners specifically about these errors, acknowledging the problem after years of complaints.

Navigation is perhaps my biggest complaint when it comes to FSD, because sometimes, we do know better. Some of us have been living in our areas for our entire lives, but even those who have not have years or even decades of experience driving on local roads. We might know a little better about routing.

But the navigation mistakes are more than just FSD potentially taking a slightly different route that may or may not save you a few minutes. Sometimes, they’re genuinely mind-boggling.

This isn’t just annoying; it cascades into broader failures. A flawed route plan confuses the AI’s decision-making, leading to hesitant behavior, unnecessary disengagements, or dangerous maneuvers like attempting impossible U-turns or ignoring clear ramps. In a system meant to operate with minimal supervision, unreliable navigation erodes trust.

More often than not, false or plain incorrect navigation is what causes me to interrupt FSD operation. Unfortunately, I believe the latest FSD version is the worst example of it, and it leads me to believe that Tesla might be making some changes; they’ve just made them in the wrong direction.

It makes you wonder: Why is a company that has done so much with the progress of FSD and autonomy struggling so much with navigation, something that is not new and has been around a long time?

Multiple Data Sources

First, Tesla’s navigation relies on a fragile patchwork of multiple data sources—Google Maps, TomTom, OpenStreetMap, Valhalla, and its own fleet-derived data—stitched together rather than a single authoritative map. When these conflict on lane geometry, road status, or turn details, the system hesitates or chooses incorrectly.

Traditional GPS providers maintain centralized, regularly validated databases with professional curation and rapid updates. Tesla’s hybrid approach, while innovative in crowdsourcing, introduces inconsistencies that a purely vision-based or end-to-end AI approach may not easily reconcile in real time.

Persistent Learning

FSD seems to struggle with persistent learning from driver interventions.

Unlike consumer apps that quickly adapt to repeated corrections or user preferences (e.g., avoiding certain routes or remembering habitual detours), Tesla’s FSD often fails to internalize fixes on the same trip or across similar scenarios. Owners note making the same manual override multiple times without the routing engine updating its behavior meaningfully.

This stems from the neural architecture prioritizing real-time perception and control over long-term route memory and personalization, making navigation feel rigid and “opinionated” compared to the adaptive logic in Waze or Google Maps.

I noticed that when I asked Grok to try and get me home a certain way (a way that FSD routinely took in the past because it was the most efficient), it had to place a waypoint between my location at the time and my house. When I went to edit the waypoint out, as Grok had placed it for a way to get FSD to get off the highway at the right exit, it was stumped again, rerouted, and took a longer way home.

Reasoning, Scaling, and Intuition

Third, scaling navigation for unsupervised or robotaxi ambitions requires not just accuracy but adaptability and user-like reasoning. Current FSD often defaults to single routes that ignore driver preferences or real-world nuances like time-of-day traffic patterns. It fails to match the intuitive, context-aware planning that traditional systems have refined over the years.

Resolving navigation is critical for several reasons. Practically, it is the backbone of any autonomous journey: without trustworthy routing, the car cannot reliably reach destinations, rendering FSD useless for robotaxis or hands-free commutes. Safety depends on it—mismatched plans create hesitation in merges or intersections, increasing accident risk.

Economically, Tesla’s valuation and future hinge on FSD delivering unsupervised driving; persistent navigation flaws delay regulatory approval and erode consumer confidence. For owners who paid premiums for FSD, these issues represent unfulfilled promises. While it is unlikely Tesla will lose too many customers due to bad navigation, some will be frustrated with the constant need for human input.

Tesla has achieved miracles in electric vehicles and battery tech. Mastering turn-by-turn—technology Garmin nailed in the early 2000s—should not be this hard. By investing in tighter data integration, faster learning loops from interventions, and more intuitive routing algorithms, Tesla could close this gap.

Until then, FSD’s navigation struggles highlight a humbling truth: even the most ambitious innovator must sometimes master the basics before conquering the future.

Continue Reading