Photo: @The_Real_Joey_D via X
Tesla's FSD Beta program suffered an important setback after one of the vehicles testing the latest build was involved in a crash. Following the accident, Tesla halted FSD Beta V12.2.1 deployment until the collision conditions were fully investigated.
Tesla has yet to release the FSD Beta V12 to a wider audience, although testing of previous builds seemed to progress as expected. The FSD Beta V12.1 builds were first pushed to non-employee vehicles at the beginning of the year, and the videos shared back then looked promising. With the subsequent updates, Tesla chose a different path by sending the latest FSD Beta update to a randomized group of vehicles, some outside the Wave1 group, usually composed of Tesla employees and fans.
While Tesla's purpose for this decision is unclear, we can only speculate that it wanted feedback from regular customers besides people already familiar with the software development. This has its benefits but also some drawbacks, considering that some unsuspecting Tesla owners might get features that they are not prepared to master. In other cases, they may also try to abuse the FSD Beta features for their five minutes of fame. However, it impacts all other owners when something goes wrong, as appears to be the case with FSD Beta V12 deployment.
The latest version, V12.2.1, arrived on February 18 with the 2024.30.20 software update. Based on a regular Tesla timeline, the build was supposed to be cleared for broader rollout in about two weeks or discarded in case something wasn't right. Teslascope explained in a dedicated thread that the Wave1 test group doesn't spend more time testing a build before moving to a new build and trying new features.
This means that something bad must have happened when there's no apparent progress after two weeks from a software update going to the Wave1 group. This was the case with the V12.2.1 build, which was paused last week due to issues reported with the auto-speed modulation. This caused uncomfortable maneuvers with the potential of causing minor incidents such as being rear-ended. The update was pulled, with the team set to start testing the next iteration of the software.
However, toward the end of February, a car involved in the V12.2.1 testing was involved in a crash, requiring a full internal investigation. Fortunately, nobody was injured, and the Tesla experienced only minor damages. However, this caused further delays, with Tesla halting development until the circumstances of the accident were investigated. Instead of the planned wide rollout this week, there's no timeline for the next FSD Beta iteration.
Rumor has it that the accident was caused by a Tesla owner trying to get FSD to park in a parking lot. Still, Teslascope declined to comment as they were asked not to disclose the details of the accident. If this is true, the crash is technically the driver's fault. However, Tesla is bound to investigate the incident, which is still classified as an FSD crash. This is a classic example of a Tesla owner's actions impacting all other owners, even though they may not have thought so.
While Tesla's purpose for this decision is unclear, we can only speculate that it wanted feedback from regular customers besides people already familiar with the software development. This has its benefits but also some drawbacks, considering that some unsuspecting Tesla owners might get features that they are not prepared to master. In other cases, they may also try to abuse the FSD Beta features for their five minutes of fame. However, it impacts all other owners when something goes wrong, as appears to be the case with FSD Beta V12 deployment.
The latest version, V12.2.1, arrived on February 18 with the 2024.30.20 software update. Based on a regular Tesla timeline, the build was supposed to be cleared for broader rollout in about two weeks or discarded in case something wasn't right. Teslascope explained in a dedicated thread that the Wave1 test group doesn't spend more time testing a build before moving to a new build and trying new features.
This means that something bad must have happened when there's no apparent progress after two weeks from a software update going to the Wave1 group. This was the case with the V12.2.1 build, which was paused last week due to issues reported with the auto-speed modulation. This caused uncomfortable maneuvers with the potential of causing minor incidents such as being rear-ended. The update was pulled, with the team set to start testing the next iteration of the software.
However, toward the end of February, a car involved in the V12.2.1 testing was involved in a crash, requiring a full internal investigation. Fortunately, nobody was injured, and the Tesla experienced only minor damages. However, this caused further delays, with Tesla halting development until the circumstances of the accident were investigated. Instead of the planned wide rollout this week, there's no timeline for the next FSD Beta iteration.
Rumor has it that the accident was caused by a Tesla owner trying to get FSD to park in a parking lot. Still, Teslascope declined to comment as they were asked not to disclose the details of the accident. If this is true, the crash is technically the driver's fault. However, Tesla is bound to investigate the incident, which is still classified as an FSD crash. This is a classic example of a Tesla owner's actions impacting all other owners, even though they may not have thought so.
Here is our reporting on this.
— Teslascope (@teslascope) March 4, 2024
Here is more context + explanation of the current delays of the FSD V12 deployment.
Preface:
Tesla avoids keeping any vehicles enrolled in Wave1 (Tesla's early access program) on a version for over two weeks. Prolonging this testing period…
FSD Beta 12: The One With The Minor Parking Lot Collision
— Arthur’s FSD V12 Videos (@ArthurFromX) February 25, 2024
user Joey (@The_Real_Joey_D) recently shared his experience with a minor mishap involving Full Self-Driving (FSD) technology in a parking lot collision. Despite having a flawless experience with FSD 12 up to that… pic.twitter.com/FBfG3A7lqy
Google News