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

News

Tesla FSD Beta 10.69.2.3 observations from testers

(Credit: Tesla)

Published

on

Tesla FSD version 10.69.2.3 rolled out shortly after AI Day. The latest update of Tesla’s Full Self Driving software delivers minor bug fixes. Some testers have received v10.69.2.3 and shared their observations with Teslarati

As previously noted, 10.69.2.3 is a relatively small update that addresses some minor bugs in FSD Beta. As it sometimes goes with software bug fixes, some Beta testers mentioned a new issue in the latest version that appeared to be a step or two backward. 

Road Obstacle Detection Issues

A few testers in Tesla’s FSD Beta Program reported experiencing road obstacle detection issues when their vehicles would not register particular objects in their path or directly ahead. 

For instance, beta tester Jonathan shared that his vehicle did not recognize or avoid dead animals on the road. Another beta tester experienced similar issues with gates in his community.

“One day coming back from work I decided to see if it can get me close to the proximity of my house. I live in a gated community. The vehicle made the turn into the drive entry of the community which has two swing gates. Vehicle was almost going to go through the closed gates,” FSD Beta user Sean shared with Teslarati. “I had to tap the breaks and override the system to make it stop. It didn’t see the gates as obstacles or road blocks. I have tried this a couple of times during daylight and night time and result is the same.”

After Tesla released v10.69.2.2, a few beta testers observed that their vehicles recognized and avoided construction work sites and similar obstacles on the road. 

Left and Right Turns

A couple of beta testers mentioned issues with left and right turns, specifically during intersections. The most prominent issue FSD Tesla drivers raised about turns was their cars’ hesitation during intersections. Testers highlighted that their cars’ hesitation during intersections isn’t really a big issue until they consider the other drivers on the road. 

Advertisement
-
-

“Hesitates too long at intersections presumably trying to determine if/when it’s safe to proceed. This only matters to me when there are cars behind me. I feel intense pressure to push the car through (and I do). Humans do not have patience to wait on its time-table,” noted Terry, another FSD Beta tester.

FSD Beta user Dr. Rahaman made similar observations. He noted that his Tesla would creep forward after stopping at an intersection on a red light and would take a left or right turn too slowly, sometimes irritating the drivers behind him. Dr. Rahaman specifically observed that his car entered left turn lanes late without a signal. In the past, the Tesla owner has noted that the car’s turn signals sporadically turn off and on at some intersections or turns. 

Lane Selection Issues

Tesla FSD v.10.69.2.3 doesn’t appear to address the largest issue multiple testers have pointed out over the past few weeks: lane selection. One beta tester seemed to sum up the sentiments most drivers in the Tesla FSD program have regarding lane selection. 

“Lane selection sometimes just plain wrong and dumb. Causes driving task to be harder for itself than it needs to be because it realizes (eventually, usually) it’s in the wrong lane too late and then has to get over which is harder with traffic and unlike a human who can gesture, the car can give no such signals as to its self-made predicament,” the tester commented.  

“Also, it sometimes gets into turn lane just late enough that cars behind me assume I’m continuing straight and swoop in behind me and get over immediately causing it to be even harder for my car to get over into that lane now because all slots are occupied and the road is about to end at a light,” he added. 

Other Issues

Some other less prominent issues that a few FSD Beta testers have noted are listed below. 

1. Lane Positioning – The car hugs the double yellow lines too closely on narrow roads or sticks to the middle of the road when no lines are present. 

2. Wide turns – The Tesla car takes wide turns, far from the curb. One tester observed that his car risked hitting the guard rails and other obstacles with its wide turn. 

Advertisement
-
-

3. Turn Lane Issues – The car still mistakes turn lanes for driving lanes

Some testers still report experiencing phantom braking and jerkiness while taking turns. However, the one observation that seems to stick out among others came from beta tester Neeraj. 

“Drives as if everyone is going to follow the rules 100% and is not accommodating or accounting for those who may not be going 100% as they should,” he said about FSD Beta. 

FSD Beta still has a ways to go before 100% autonomous version rolls out to the general public. Observations and tests from beta testers help Tesla improve FSD. Elon Musk teased more significant improvements in the next update, 10.69.3. Tesla hopes to release a ‘supervised’ FSD version by the end of the year. 

Have you tried out FSD Beta 10.69.2.3 yet? 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

News

Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots

Published

on

Credit: Tesla

Tesla released Full Self-Driving version 14.3.6 last week, and after what was potentially one of the best FSD releases in v14.3.5, there has been a bit of a regression. While there are some bright spots, the changes made to v14.3.6 seem to have backtracked some behaviors.

Overall, it is hard to really complain about FSD in any sense; it has revolutionized how I travel literally anywhere. According to my self-driving app, the last time I went a day without using it was 59 days ago.

However, I think it’s also important to recognize when things are just plain bad with FSD. There are times it does truly mind-boggling things, and I’ll dive into those here. Additionally, I only had these issues on local roads, not on highways. Highway operation, generally, is always incredible other than the occasional complaint about speed or left lane camping.

With those things being said, my personal experience may not represent others’ experiences. A handful of people have said they have had a similar experience on v14.3.6, while others have said it is more than normal.

Turning Hesitancy, Inaccuracy

I’ve noticed more inaccuracy turning into multi-lane stretches of road than in any version I can remember. I’ve had at least three instances of FSD turning into a stretch of roadway that has two or more lanes, and not selecting a lane confidently as it has in past versions.

Instead, the car will drive over one of the dashed road lines, and the steering wheel will jerk back and forth before picking the lane. It should be said that it has always picked the correct lane when choosing based on the navigation, but it is still very indecisive. The steering wheel jerking is reminiscent of some of the later versions of v13.

I admit I really hate to see the steering wheel jerking come back. However, I think when Tesla releases v14.3.7, it won’t be present. When there are occurrences of it in FSD versions, it is usually resolved by the following release.

FSD Disregards Manual Turn Signals

This is my biggest bone to pick with FSD other than Navigation issues, but this one seems like it would be such an easy fix.

If Tesla is going to put the word “Supervised” on the end of “Full Self-Driving,” then when I tell the car to do something, it should do it. If I input an increase in speed by pressing the accelerator, the car will immediately respond. It does not disregard my input because it feels it is traveling at the right speed.

FSD should never disobey and turn off turn signals that the driver inputs. Trying to direct the car into the correct lane, I had initiated the left turn signal not once, not twice, but three times, with the car turning it off all three times and continuing in a lane that would end in just one block. The only solution at this point would be to zipper merge.

This goes back to the fact that self-driving’s biggest bottleneck might be rider preference. A zipper merge might have been more than reasonable, might have saved me time that I spent sitting through an additional light cycle, and might be something many drivers would do. I was in no hurry, I traditionally do not try to zipper merge because it feels inconsiderate, and lastly, the car should have just followed my input.

This caused me to disengage and drive manually the rest of the way home. Sometimes I just do not need FSD to try to pass every car it can at intersections.

Bird Braking is a Thing of the Past

The big complaint with recent versions of Full Self-Driving has been what we’ve coined as “bird braking,” which is when the car will brake suddenly as a bird flies past.

There have been zero issues with this so far in v14.3.6, which is an excellent improvement.

FSD Might Already Be Taking Note of Driver Preferences

Another thing I have noticed over the past few days is that v14.3.6 seems to already be taking my preferences with navigation into account.

This is something that is supposed to be rolling out with the Summer Update, but I have a hunch it’s already present and might have been included in this v14.3.6 build. On Friday, FSD pulled into an entrance to a local convenience store that it had never attempted to go into before.

Typically, I manually pull into this entrance because it avoids heavy cross traffic at the main entrance. FSD has always chosen that congested main entrance.

Additionally, FSD has pulled into my assigned parking spot at my townhouse community on multiple occasions with this release. This is something that used to happen ocassionally, but not consistently.

It also navigated back to the same convenience store last night, drove through crazy cars scrambling to gas pumps, navigated out of the parking lot correctly, drove me home, and, once again, parked in my assigned spot.

As previously stated, this release just seems to have a few things that need to be brought to Tesla’s attention, and also to make others who use FSD aware of some things that I’ve experienced. I look forward to the next release that will remedy these issues, just as Tesla has always done in the past.

Continue Reading

Elon Musk

Musk’s massive Terafab project will get final location soon

Published

on

Credit: SpaceX

Elon Musk’s massive Terafab project, which will be the first true conglomeration between each of his major entities, is set to get its final location soon, the CEO said on Tesla’s recent earnings call.

“The Terafab, we expect to announce a location soon, and provide more details about our plans in that regard. We’ll leave that to the product, the launch announcement rather than try to squeeze it into an earnings call,” Musk said last Wednesday.

Tesla Terafab set for launch: Inside the $20B AI chip factory that will reshape the auto industry

Terafab was announced by Musk back in March and was essentially a massive, vertically integrated semiconductor manufacturing project that would provide all the chips the three companies needed for their AI initiatives without needing third-party companies.

The plant will produce over 1 terawatt of AI compute each year, and will help back up projects like Optimus, Full Self-Driving, and other AI-based projects that Musk’s companies are working on.

In April, less than a month after the project was launched, Intel announced it would join the project, contributing manufacturing expertise and consulting to Terafab as a whole. Intel is one of three chip manufacturers that produce sub-5 nanometer chips at scale. TSMC and Samsung are the other two.

However, there was no true indication of where Terafab would end up, but most believe it will likely be somewhere in Texas. Business Insider has reported that SpaceX plans to build out Terafab in Grimes County, Texas, but this is unconfirmed.

Musk confirmed recently that it would not be on Giga Texas property, as it is simply too large.

Terafab holds much of Musk’s grand ambitions for the future within its construct. It holds so much responsibility for the future and the biggest projects that Musk’s companies can imagine.

“I think this is a very big announcement and it deserves to have its own day in the spotlight and not be squeezed into an earnings call,” he said. “I do think Terafab is going to be an amazing initiative and a necessary one, and one without which we will be constrained in our ability to scale Optimus production, because we simply won’t have enough AI chips.”

He continued by stating that Terafab is necessary for scaling Optimus, which Musk said could be the biggest product of any kind of all time. “It’s crucial to solve that, and we’ll have to solve memory, logic, and packaging in order to scale Optimus.”

Continue Reading

News

Elon Musk reveals SpaceX performed secret Starship test on Flight 13

Published

on

Credit: SpaceX

SpaceX performed a secret test on a specific portion of Starship with its recent 13th test flight last week, CEO Elon Musk revealed.

Starship’s 13th test flight took place last Friday, and in many aspects, it was one of the most overwhelmingly successful launches in the project’s history.

All of the mission objectives were met without incident, both the Super Heavy Booster and Ship managed to perform safe splashdowns in the Gulf of America and the Indian Ocean, respectively, and the deployment of Starlink satellites came and went without any complications.

However, there was more on the agenda for SpaceX with Flight 13. Musk revealed an internal test of the ship’s heat shield tiles, as the space exploration company wanted to push them to the limits after previous issues.

Many noticed that Starship’s initial launch seemed to be more accelerated than normal, and that was not a mistake. Musk revealed that SpaceX decided to give Flight 13 an intentionally aggressive acceleration rate in an effort to test how well the tiles would remain attached to the ship:

SpaceX had issues with some of the heat shield tiles remaining attached early on in the Starship program. The first six test flights presented some kind of anomaly with them, so the company’s big focus with them was to figure out a way to keep them intact through the duration of the flight.

Things truly improved as Flight 10 showed that ceramic tiles generally stayed attached to the ship far better due to refined attachment, as SpaceX utilized pins instead of adhesives. Flights 10 through 13 truly showed some clear progress with the heat shield tiles, and this latest test seems to be where some real progress was noticed, especially by Musk.

The 13th Starship launch last Friday was the second with Starship V3, SpaceX’s latest and greatest iteration of the spacecraft. Goals and ambitions are getting even grander as the project continues to progress. Musk has already hinted that SpaceX will likely try to catch Starship with Flight 14.

Continue Reading