Volkswagen has a long and storied tradition of building world-class vehicles. While they have managed to make a legacy off of offering affordable, stylish, and effectively-performing models for 84 years, their next big challenge comes in the tall task of creating and engineering electric vehicles that are functional. While this sounds like an easy task for the legendary German car company, it has encountered several problems over the course of its MEB platform’s development. The narrative of the problem solving has changed several times in the past year.
The software issues for Volkswagen have been evident since the initial development of the ID. family of vehicles. Now, Volkswagen has been relatively transparent regarding the issues with its software in the past. Recently, there has been a trend, however, in how the company’s software project is being portrayed because for a while, Volkswagen was pawning off its software as “fixed.” It is obvious this isn’t the case.
Yesterday, a report came out that indicated CEO Herbert Diess was interested in keeping the software fixes in-house and that he wasn’t interested in having some other company, whether it be another automaker or a tech company, fix the issues they were encountering. It doesn’t seem like a great idea to push the software problems onto another company, especially if Volkswagen attempts to set the precedent that it is a leader in electric powertrains and EV manufacturing. The only real way to establish any sort of narrative that proves your worthiness in this sector is to solve things yourself, it seems. If Tesla had given its software issues early on to Apple or Microsoft, for example, to fix, you can bet they wouldn’t be looked at as some automotive marvel. They’d just be another company out there trying to establish a presence in a quickly growing field of EV competitors. The vertical integration that Tesla has been able to display, through not only its hardware but also through its development of software. The complete expertise in software especially is advantageous in the event of Software Updates being rolled out in an Over-the-Air fashion as Tesla does. When even the smallest bug or issue is revealed in the coding, engineers can quickly solve the problem and roll out a new update in a matter of minutes.
Diess is right, it is absolutely imperative that Volkswagen solves these issues in-house. However, there needs to be more consistency in the story that is being portrayed, in my opinion. For the past year, we’ve heard that Volkswagen has admitted Tesla has a 10-year advantage, then the ID.3 software issues were worse than initially reported, then that software was so bad it had moved onto other vehicles.
A big thanks to our long-time supporters and new subscribers! Thank you.
I use this newsletter to share my thoughts on what is going on in the Tesla world. If you want to talk to me directly, you can email me or reach me on Twitter. I don’t bite, be sure to reach out!
Then, all of a sudden, Volkswagen suddenly made Markus Duesmann, the ICE-supportive CEO of Audi, the person responsible for solving the software issues. Finally, the company came out in December and claimed that it had overcome all of the issues it had with the ID. family’s software.
It all seems like a plan to save face, and it should be. Volkswagen has held this reputation for years for making quality gas cars. Apart from the Dieselgate scandal, which inevitably tarnished the reputation of the company, Volkswagen has done a reasonably good job of creating cars that are dependable. My first car was a Volkswagen with 198,000 miles on it. It was dependable, and I was sad to see it go when I finally had to say goodbye.
However, it is quite alarming to see that Volkswagen is still years away from solving these issues. For a year, there have been so many different narratives regarding the company’s software, and it seems like a cause that perhaps just needs more time. There is no doubt in the world that they can figure it out eventually, but is it worth keeping the faith for five or ten more years? Is it worth waiting until 2025, 2030, or even longer to have effective electric vehicle software just to say “We developed it ourselves!”
It seems like the big issue coming to fruition now is the fact that Volkswagen has set another narrative forward that it will be ready to deliver software updates this Summer. All I have to say is, the electric vehicle community has a great memory, they are very unforgiving, and they don’t want to hear excuses. If Volkswagen cannot figure out a way to develop effective software for its vehicles by the Summer, roll out OTA updates, and provide proof that its vehicles are worth a damn, it may be time to consider other options.
Diess has a great relationship with Elon Musk, and it may not be too late to consider seeking help from Tesla in this sense. I don’t think it would be the worst thing in the world to have a guy who is your friend and the CEO of the most successful EV company in the world help your company solve some issues. Volkswagen would gain plenty of credibility with Tesla’s software infrastructure if it chooses to go that way. I hope they can somehow solve the issues in-house, but I am more prone to believe that if things don’t come around this Summer like VW has promised with the OTA updates, it will be a bad look once again, and VW could remain the laughing stock of the EV industry.
“If we want to retain our independence, we have to be able to develop the software in the car ourselves. This is the only way for us to guarantee long-term success,” Diess said. Is that a hill VW is willing to die on?
On behalf of the entire Teslarati team, we’re working hard behind the scenes on bringing you more personalized members benefits, and can’t thank you enough for your continued support!
Elon Musk
SpaceX Starship Version 3 booster crumples in early testing
Photos of the incident’s aftermath suggest that Booster 18 will likely be retired.
SpaceX’s new Starship first-stage booster, Booster 18, suffered major damage early Friday during its first round of testing in Starbase, Texas, just one day after rolling out of the factory.
Based on videos of the incident, the lower section of the rocket booster appeared to crumple during a pressurization test. Photos of the incident’s aftermath suggest that Booster 18 will likely be retired.
Booster test failure
SpaceX began structural and propellant-system verification tests on Booster 18 Thursday night at the Massey’s Test Site, only a few miles from Starbase’s production facilities, as noted in an Ars Technica report. At 4:04 a.m. CT on Friday, a livestream from LabPadre Space captured the booster’s lower half experiencing a sudden destructive event around its liquid oxygen tank section. Post-incident images, shared on X by @StarshipGazer, showed notable deformation in the booster’s lower structure.
Neither SpaceX nor Elon Musk had commented as of Friday morning, but the vehicle’s condition suggests it is likely a complete loss. This is quite unfortunate, as Booster 18 is already part of the Starship V3 program, which includes design fixes and upgrades intended to improve reliability. While SpaceX maintains a rather rapid Starship production line in Starbase, Booster 18 was generally expected to validate the improvements implemented in the V3 program.
Tight deadlines
SpaceX needs Starship boosters and upper stages to begin demonstrating rapid reuse, tower catches, and early operational Starlink missions over the next two years. More critically, NASA’s Artemis program depends on an on-orbit refueling test in the second half of 2026, a requirement for the vehicle’s expected crewed lunar landing around 2028.
While SpaceX is known for diagnosing failures quickly and returning to testing at unmatched speed, losing the newest-generation booster at the very start of its campaign highlights the immense challenge involved in scaling Starship into a reliable, high-cadence launch system. SpaceX, however, is known for getting things done quickly, so it would not be a surprise if the company manages to figure out what happened to Booster 18 in the near future.
News
Tesla FSD (Supervised) is about to go on “widespread” release
In a comment last October, Elon Musk stated that FSD V14.2 is “for widespread use.”
Tesla has begun rolling out Full Self-Driving (Supervised) V14.2, and with this, the wide release of the system could very well begin.
The update introduces a new high-resolution vision encoder, expanded emergency-vehicle handling, smarter routing, new parking options, and more refined driving behavior, among other improvements.
FSD V14.2 improvements
FSD (Supervised) V14.2’s release notes highlight a fully upgraded neural-network vision encoder capable of reading higher-resolution features, giving the system improved awareness of emergency vehicles, road obstacles, and even human gestures. Tesla also expanded its emergency-vehicle protocols, adding controlled pull-overs and yielding behavior for police cars, fire trucks, and ambulances, among others.
A deeper integration of navigation and routing into the vision network now allows the system to respond to blocked roads or detours in real time. The update also enhances decision-making in several complex scenarios, including unprotected turns, lane changes, vehicle cut-ins, and interactions with school buses. All in all, these improvements should help FSD (Supervised) V14.2 perform in a very smooth and comfortable manner.
Elon Musk’s predicted wide release
The significance of V14.2 grows when paired with Elon Musk’s comments from October. While responding to FSD tester AI DRIVR, who praised V14.1.2 for fixing “95% of indecisive lane changes and braking” and who noted that it was time for FSD to go on wide release, Musk stated that “14.2 for widespread use.”
FSD V14 has so far received a substantial amount of positive reviews from Tesla owners, many of whom have stated that the system now drives better than some human drivers as it is confident, cautious, and considerate at the same time. With V14.2 now rolling out, it remains to be seen if the update also makes it to the company’s wide FSD fleet, which is still populated by a large number of HW3 vehicles.
News
Tesla FSD V14.2 starts rolling out to initial batch of vehicles
It would likely only be a matter of time before FSD V14.2 videos are posted and shared on social media.
Tesla has begun pushing Full Self-Driving (Supervised) v14.2 to its initial batch of vehicles. The update was initially observed by Tesla owners and veteran FSD users on social media platform X on Friday.
So far, reports of the update have been shared by Model Y owners in California whose vehicles are equipped with the company’s AI4 hardware, though it would not be surprising if more Tesla owners across the country receive the update as well.
Based on the release notes of the update, key improvements in FSD V14.2 include a revamped neural network for better detection of emergency vehicles, obstacles, and human gestures, as well as options to select arrival spots.
It would likely only be a matter of time before FSD V14.2 videos are posted and shared on social media.
Following are the release notes of FSD (Supervised) V14.2, as shared on X by longtime FSD tester Whole Mars Catalog.
Release Notes
2025.38.9.5
Currently Installed
FSD (Supervised) v14.2
Full Self-Driving (Supervised) v14.2 includes:
- Upgraded the neural network vision encoder, leveraging higher resolution features to further improve scenarios like handling emergency vehicles, obstacles on the road, and human gestures.
- Added Arrival Options for you to select where FSD should park: in a Parking Lot, on the Street, in a Driveway, in a Parking Garage, or at the Curbside.
- Added handling to pull over or yield for emergency vehicles (e.g. police cars, fire trucks, ambulances.
- Added navigation and routing into the vision-based neural network for real-time handling of blocked roads and detours.
- Added additional Speed Profile to further customize driving style preference.
- Improved handling for static and dynamic gates.
- Improved offsetting for road debris (e.g. tires, tree branches, boxes).
- Improve handling of several scenarios including: unprotected turns, lane changes, vehicle cut-ins, and school busses.
- Improved FSD’s ability to manage system faults and improve scenarios like handling emergency vehicles, obstacles on the road, and human gestures.
- Added Arrival Options for you to select where FSD should park: in a Parking Lot, on the Street, in a Driveway, in a Parking Garage, or at the Curbside.
- Added handling to pull over or yield for emergency vehicles (e.g. police cars, fire trucks, ambulances).
- Added navigation and routing into the vision-based neural network for real-time handling of blocked roads and detours.
- Added additional Speed Profile to further customize driving style preference.
- Improved handling for static and dynamic gates.
- Improved offsetting for road debris (e.g. tires, tree branches, boxes).
- Improve handling of several scenarios, including unprotected turns, lane changes, vehicle cut-ins, and school buses.
- Improved FSD’s ability to manage system faults and recover smoothly from degraded operation for enhanced reliability.
- Added alerting for residue build-up on interior windshield that may impact front camera visibility. If affected, visit Service for cleaning!
Upcoming Improvements:
- Overall smoothness and sentience
- Parking spot selection and parking quality
SpaceX Starship Version 3 booster crumples in early testing
Tesla FSD (Supervised) is about to go on “widespread” release
