Connect with us
tesla-fsd-beta-10-69-2-3-release tesla-fsd-beta-10-69-2-3-release

News

Tesla FSD Beta 10.69.2 “looking good” for weekend release + 10.69.1.1 Reviews

Credit: Whole Mars Catalog/Twitter

Published

on

Elon Musk shared that Tesla FSD Beta 10.69.2’s release is still set for this weekend. 

Tesla initially planned to release v10.69.2 last week but delayed the update to polish it up more. The company rolled out v.10.69.1.1 to more Beta testers instead. 

Tesla FSD Beta 10.69.1.1 Reviews

A few Tesla Beta testers who received v10.69.1.1 shared their observations and thoughts about the update with Teslarati. One of the common issues Beta Testers mentioned was phantom braking. 

One 2021 Model S owner, Howard, noted that his Tesla vehicle still experienced phantom braking too much. He shared that his Model S drove like a 16-year-old. “Not smooth with the wheel, throttle, or brakes,” he said.

Advertisement

Howard also observed that his Tesla ignored some speed signs, even if they popped up on the display. The Tesla Model S owner added that his car “still fades right into turn lanes when there is not [a] turn to be done. It then swerves to go to the last [turn] it just left.” 

Fellow FSD Beta tester, Michael, was “a bit disappointed” with the latest update. He noted experiencing some phantom braking along the Long Island Expressway. 

“Can’t seem to figure out the somewhat irregular lines in the HOV lane, which is surprising to me. Oh well….hope for better next time. Still not there, but much better than first experiences,” Michael added. 

Impressions from a longtime FSD Beta Tester

FSD Beta tester Les also shared his thoughts about v.10.69.1.1 with Teslarati. Les has been an Early Access software tester since 2018. He was kind enough to break down all his observations from testing FSD Beta 10.69.1.1.

Les mentioned seeing a few issues with FSD Beta that have been around since Fall 2021. Some of the issues are listed below.

Advertisement
  1. [The] car doesn’t always stay in [the] proper turn lane when using the outer lane of a left dual turn lane scenario; 8/10 times, mid-turn, it will cross over into the inner turn lane. It has done this for me with every FSD Beta build back to October 2021. 
  2. Inconsistent lane selection: my car will still sometimes move[s] into lanes opposite to the next upcoming turn, sometimes when close to that upcoming turn, sometimes missing the turn itself.
  3. Late turn signals: this is a long-standing issue many testers have reported. The turn signals [usually] activate too late when they need to activate ahead of a turn lane to alert drivers behind us.

Despite the continuing issues he observed, Les seemed to have an overall good experience with the latest update. He specifically highlighted Tesla’s work with Chuck Cook Style’s unprotected left terms which were specifically mentioned in v10.69’s release notes. Listed below are all his good observations about FSD Beta v. 10.69.1.1.

  1. The improvement to “Chuck Cook style” unprotected left turns with multiple lanes and medians is incredible. The car utilizes the median space very well. [It] feels like more than an improvement. It really almost feels like a feature upgrade. It’s that significant and amazing to experience.
  2. The car has almost no more phantom braking events for me. I never had many to begin with, certainly not as many severe events as other friends report, but I did notice the ones I had and the places they occurred no longer occurred.
  3. Traffic turning across my car’s path no longer triggers a cautious braking event when there’s enough room ahead. The car better recognizes the crossing vehicle’s direction and speed, and my car maintains its speed. Very human-like behavior.
  4. More assertive and smooth acceleration out of turns, especially when entering a higher speed road. Related: improved acceleration from stops. I like this very much, as prior builds often took too long (for my taste anyway) to get up to speed. It still could get up to speed more quickly, but there is [a] notable improvement. 
  5. The dashcam bug has been eliminated!! The prior build would routinely crash the dashcam after I parked and/or charged, requiring either a computer reboot or removal/reinsertion of [the] dashcam thumb drive to fix. No more problems!

In general, Tesla is steadily improving FSD Beta with each update. And Testers are actively experiencing those improvements. However, Tesla’s Full Self-Driving suite still needs more work before it rolls out to the public. 

Are you an FSD Beta tester? I’d like to hear your thoughts on v10.69.2! 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