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.

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. 

Advertisement
-

“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.

  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

Lifestyle

Watch Tesla’s “guardian angel” FSD feature take over for collision evasion

Published

on

By

Tesla’s Automatic Collision Evasion feature can be seen in one of the first owner videos of it in action.

Tesla owner Spencer (@scotsrule08) posted on Monday that the feature “worked flawlessly,” saying FSD reengaged itself just as he was about to hit a curb. Ashok Elluswamy, who leads Tesla’s AI team, shared the clip and wrote, “A guardian angel always looking out for you.”

The video arrives in the middle of a staged rollout. Tesla first shipped Automatic Collision Evasion with FSD (Supervised) v14.3.9 in software update 2026.27.6 earlier this month, which Teslarati covered as it reached cars. Update 2026.27.10, which began going out on September 19, carried the feature improvements with FSD v14.3.10, according to release notes tracked by Not a Tesla App. The newer 2026.27.11 build is now reaching another wave of vehicles.


The feature only runs on HW4 vehicles, and it requires an active FSD purchase or subscription with both FSD (Supervised) and Automatic Emergency Braking enabled. HW3 owners receive FSD v14.2 Lite in the same updates, but that build does not include collision evasion.

Tesla’s release notes describe two triggers. The first is an imminent frontal collision that braking alone may not prevent, in which case the car can activate FSD to steer, brake or accelerate around the hazard. That scenario is limited to highways below 85 mph, with no pedestrians or cyclists detected and no slippery road surface. The second covers a driver who appears inattentive, such as reaching into the back seat, or who seems to have switched off FSD by accident. Spencer’s curb clip appears to fall into that second category.

Tesla plans big safety improvements for Full Self-Driving v15

Once the system takes over, the accelerator is muted and light brake input will not cancel the maneuver. Drivers need to apply firm, deliberate steering force to take back control, and the car chimes to hand control back once the danger has passed.

Elluswamy recently noted that earlier hazard prediction, faster reaction time and better collision avoidance would arrive with FSD v15, the next major version.

Continue Reading

News

Tesla Roadster event gets delayed due to unfavorable weather

Published

on

Credit: Tesla

Tesla is delaying its event for the Roadster, moving it from this Thursday, October 1, to Thursday, October 15, due to unfavorable weather.

The company has said it has been tracking the weather for this Thursday closely with local meteorologists, and because the event can only be held outside, Tesla is making the call to delay it:

“We’ve been tracking the weather closely with local meteorologists, but given the severe conditions predicted & because this event can only be held outdoors, we’ve made the difficult decision to reschedule. New date is October 15. Additional details to follow.”

We are sure that this is bringing back PTSD for some Tesla fans, and we know it is not ideal, but this also reveals some things about the event. Tesla said that this can only be held outdoors, meaning it bodes well for the rumors that the vehicle could potentially hover.

Some believe that this was essentially confirmed by the FAA airspace restriction they were granted, but this could have been for a drone show or to keep drones from spying on the event.

Tesla Roadster is available for order once again following brief hold

The Roadster event has been long-awaited, and it is unfortunate that the weather is going to keep us all waiting a little bit longer.

The Tesla Roadster will be unveiled in Waco, Texas.

Continue Reading

Elon Musk

SpaceX turned a heralding moment for Starship into its greatest

Starship reached orbit despite losing an engine, deployed 26 Starlink V3 satellites on Flight 14.

Published

on

By

SpaceX’s Starship reached orbit for the first time on Monday, and for a few nail-biting minutes it looked like it wouldn’t. During ascent on Flight 14, one of Ship 41’s six Raptor engines shut down early, and SpaceX’s livestream host Dan Huot told viewers the team had decided not to commit to orbit. Minutes later, after what Huot described as a lot of conversation in the control room, the final poll came back in favor, and a roughly 19 second burn of a single Raptor pushed the ship into orbit about 170 miles up.

The reversal matters because SpaceX had written the exit ramp into the mission plan. The company said it would only fire the orbital insertion burn if flight controllers confirmed enough backup hardware remained for the deorbit burn, a condition Teslarati laid out ahead of the flight. Losing an engine was exactly the scenario that rule was built for.

Pressing forward fits Elon Musk’s history. Falcon 1 failed three straight times before its fourth launch reached orbit in 2008, with SpaceX nearly out of money, and Starship was developed by flying prototypes until they broke. What changed this year SpaceX going public, and with $SPCX sliding below its IPO price in July when Flight 13 slipped, the short interest climbed significantly, as Teslarati reported at the time. A Starship potentially lost today with revenue generating next-gen Starlink satellites aboard would have landed directly on shareholders.

That pressure showed up after orbit. SpaceX cut a flight planned to last nearly 10 hours to about three, moving splashdown from west of Chile to the North Pacific near Hawaii. SpaceX gave no reason, though Musk said this month the company was being extremely cautious about debris risk. The single Raptor for deorbit worked, and Ship 41 completed its flip and landing burn before breaking apart in the water, an outcome SpaceX expected. Musk has structured SpaceX’s governance to shield long term bets from market pressure.

The payload is the bigger business story. Musk posted that all 26 Starlink V3 satellites deployed and are “operating nominally.” Each V3 is rated for about 1 Tbps of downlink and 160 Gbps of uplink, so this single launch adds roughly 26 Tbps, about 10 times what a Falcon 9 load of V2 Mini satellites adds. The V3 is too large for Falcon 9, making Starship the only vehicle that can build out the planned 100,000 satellite constellation, at up to 60 per flight once it reaches routine service. Unlike the 20 V3 units on Flight 13, which reentered on a suborbital path, these will raise their orbits and could begin serving customers within weeks and bring in hundreds of millions of additional dollars in projected Starlink revenue.

SpaceX has already begun winding down Falcon 9 Starlink launches from Florida in favor of Starship. Reported targets put Flight 15 as early as October 19, leaving about three weeks to diagnose Monday’s engine shutdown before the next orbital attempt.

Continue Reading