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.
“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.
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.
“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.
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.
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.
Investor's Corner
Tesla has a Cybercab problem nobody saw coming
Tesla’s Cybercab line now builds robotaxis faster than Tesla can deploy them, Lars Moravy says.
Tesla’s Cybercab line in Texas can now build the two seat robotaxi faster than the company can put it into service, according to Lars Moravy, Tesla’s Vice President of Vehicle Engineering. “We don’t run every day because the line can run so fast. It’s currently outpacing our deployments,” Moravy said in a new Cybercab deep dive from Munro Live. “So, it’s a bit of a race right now. Who’s going to go faster? Right now the manufacturing line’s ahead.”
Tesla’s official Robotaxi account shared a Cybercab analysis video on X on Monday, calling it a “Cybercab engineering deep dive.” Moravy’s comments go further than what he told analysts on the Q3 earnings call last week, when he said the Cybercab line’s listed capacity of more than 125,000 units a year undersells what it can actually run.
The tour shows where that speed comes from. Tesla’s unboxed process splits the Cybercab into front, rear, side and center modules that are built and tested on their own before they meet on a short final line. That final line has just 25 fully automated stations, which Tesla’s team estimated is a fifth to a tenth of what a Model Y needs. The full line is about 78% automated, the framing line is already at 100%, and the layout uses roughly 50% less floor space per vehicle. The stated goal is “100% automation in 10 second cycle time,” or one finished Cybercab every 10 seconds.
Tesla also deleted the paint shop. Only the side modules are coated, and the exterior panels get their color inside the molding machine. Engineers said the car is designed to run at least 500,000 miles, which matters for a vehicle that will spend most of its day carrying riders.
The battery got the same treatment. The Cybercab uses an 88S6P pack of 4680 cells in a steel enclosure, a first for Tesla, with each module potted separately so a single failed module can be swapped instead of the whole pack. Wireless battery management boards replace a wiring harness, and new contactors are fast enough to drop the pyro fuse entirely. Tesla’s battery director graded the pack an A minus, compared with a D for the Model Y structural pack and a B minus for Cybertruck. Up front, the drive unit runs an 11:1 gear ratio versus roughly 9:1 on most Teslas, since the Cybercab does not need a high top speed.
Cybercab engineering deep dive — Robotaxi (@robotaxi) October 26, 2026
The deployment side is now the bottleneck Moravy described. Tesla had more than 50 Cybercabs working the Formula 1 weekend in Austin, and Texas records show 463 Cybercabs registered. Tesla said on its earnings call that Cybercab service will launch in Dallas next month, and Moravy said the company is aiming to get Cybercabs to customers by the end of 2026. Every unit built so far has gone into Tesla’s own fleet since the line moved into volume production in April.
Munro Live also asked when it could get a Cybercab to tear down. Tesla’s answer: “Not yet.”
SpaceX’s Raptor engine family has steadily increased sea-level thrust while simultaneously reducing mass, turning iterative engineering gains into substantially higher performance for the Super Heavy booster. CEO Elon Musk shed more light on how powerful Raptor 4 will be, and it’s pretty crazy.
Raptor 1 delivered 185 metric tons of thrust at roughly 2,080 kilograms, while Raptor 2 raised that to 230 tons while cutting mass to about 1,630 kilograms. SpaceX data for Raptor 3 lists a target of 280 tons at 1,525 kilograms (with further reductions in associated vehicle hardware), while operational flight ratings have been cited near 250 tons.
This morning, Elon Musk stated that Raptor 4 is expected to reach 300 tons of sea-level thrust at roughly the same mass as Raptor 3. Across these versions, thrust has risen by more than 60 percent from the first engines while engine mass has fallen, producing a sharp improvement in thrust-to-weight ratio. This is a true testament to how great SpaceX engineering has been:
🚀 Elon says Raptor 4 will make 300 tons of thrust at sea level at roughly the same mass as Raptor 3.
How far Raptor has come:
Raptor 1: 185 tf, 2,080 kg
Raptor 2: 230 tf, 1,630 kg
Raptor 3: 250 tf, 1,525 kg
Raptor 4: 300 tf33 on Super Heavy = ~9,900 tf, nearly 3x Saturn V https://t.co/HQDswZhyvL
— TESLARATI (@Teslarati) October 26, 2026
With 33 engines on SuperHeavy, the jump from earlier versions to a 300-ton Raptor 4 would produce roughly 9,900 metric tons of total liftoff thrust, nearly three times the Saturn V’s approximately 3,400 metric tons from its five F-1 engines.
This is not just a larger number on a data sheet, either, as sea-level thrust is the force available the moment the vehicle leaves the pad. This is when it is heaviest and still deep in Earth’s gravity well and dense atmosphere.
Higher levels of sea-level thrust directly improves the initial thrust-to-weight ratio of the full stack. A higher ratio produces faster acceleration off the pad, which shortens the time the rocket has to spend fighting gravity, and gravity losses during the first minute or two of the flight are a major drain on total available delta-v. Every second shaved off of that early climb preserves more propellant energy for reaching orbital velocity or for carrying extra payload.
Because Super Heavy’s engine count is constrained by vehicle diameter and packing density, increasing thrust per engine is the most straightforward way to raise total liftoff performance without redesigning the booster structure or design.
The same-mass target for Raptor 4 is equally important. Holding engine mass roughly constant while raising thrust improves the engine’s own thrust-to-weight ratio and reduces the structural and propellant mass fraction that must be carried solely to support the engines.
Earlier Raptor iterations also simplified or eliminated extensive vehicle-side hardware such as heat shields. These gains compound: more force for less installed mass leaves additional capacity for propellant, payload, or operational margins such as engine-out capability.
For Starship’s architecture, the practical effects are large. Greater liftoff thrust supports heavier vehicles, larger propellant loads, and higher payloads to low Earth orbit, figures SpaceX has targeted in the 100-plus-ton reusable range. That capacity underpins orbital refueling, lunar missions, and eventual Mars cargo and crew flights.
Continued growth in sea-level thrust therefore tightens the gap between theoretical rocket performance and the high flight rates and reusability needed to make large-scale space transport practical.
Tesla has expanded its Tesla Assisted Driving (TAD) suite to its tenth European country, as Latvia joined a growing list of European Union member states authorizing the company’s advanced driver assistance technology.
Tesla Europe announced this morning that the system is now approved in Latvia, with a software rollout to begin soon.
The approval and rollout follow recognition of a provisional European type approval originally granted by the Netherlands’ RDW authority on April 10.
🚨 Latvia has just received approval for Tesla Full Self-Driving (Supervised)
This is the 10th country in the EU to gain approval:
1. Netherlands — 10 April 2026 (original RDW approval)
2. Lithuania — 20 May 2026
3. Estonia — 29 May 2026
4. Denmark — 9 June 2026
5. Belgium — 10 June 2026
6. Slovenia — 7 September 2026
7. Czechia — 21 September 2026
8. Croatia — 29 September 2026
9. Slovakia — 16 October 2026— TESLARATI (@Teslarati) October 26, 2026
Latvia’s Road Traffic Safety Directorate (CSDD) evaluated the Dutch documentation, coordinated with the other national authorities, and reviewed updates from Tesla. These included tightened limits on speed offsets, automatic resets of any manual speed adjustments after each trip, and stronger driver monitoring.
In Europe, the feature is marketed as Tesla Assisted Driving after a recent rule change that labeled the name “Full Self-Driving” as misleading.
The system remains an SAE Level 2 driver assistance tool, not unsupervised autonomy. It can control speed, steering, braking, lane changes, and intersections while following a navigation route. Drivers need not keep their hands on the wheel at all times, yet they must continuously monitor the road and be prepared to intervene immediately.
The sequence of EU recognitions began with the Netherlands in April and continued through Lithuania, Estonia, Denmark, Belgium, Slovenia, Czechia, Croatia, and Slovakia. Most have relied on mutual recognition of the single Dutch provisional approval rather than independent national testing.
These national clearances do not yet constitute bloc-wide authorization. An EU-wide decision requires a qualified majority in the Technical Committee on Motor Vehicles: at least 15 of 27 member states representing 65 percent of the EU population. Larger markets, like Germany, France, and Italy, remain under review, and a vote is expected this December.
However, for Latvian Tesla owners with compatible vehicles and software, the imminent rollout expands access to the supervised system while underscoring that attentive human oversight remains essential.
Tesla has a Cybercab problem nobody saw coming
How SpaceX Is raising Raptor’s sea-level thrust while holding engine mass steady
