News
SpaceX begins installing new ‘Raptor 2’ engines on Super Heavy booster
SpaceX has begun installing new ‘Raptor 2’ engines on Super Heavy Booster 7 after the prototype completed a range of tests and returned to the company’s South Texas ‘Starbase’ rocket factory.
Earlier this month, SpaceX transported Booster 7 (B7) in the opposite direction, returning the 67-meter (~220 ft) tall rocket to Starbase’s orbital launch site (OLS) for the second time after it was forced to head back to the factory for repairs. Repairs completed, SpaceX dove headfirst into the process of verifying that the booster had been returned to full health and immediately filled its tanks to the brim with at least 3000 tons (>6.5M lb) of liquid nitrogen and oxygen – better known as a cryogenic proof test.
Less than 48 hours after completing its first post-repair test, Booster 7 sailed through another full cryoproof test without losing a beat. On May 13th, two days later, SpaceX attached a crane to Super Heavy B7 and removed it from the orbital launch mount before rolling the rocket back to Starbase’s build site on May 14th. Without official confirmation, which is increasingly rare, it was impossible to determine the results of the testing with certainty, but the speed of the process and Booster 7’s rapid launch mount removal made the two most extreme outcomes the most likely.
A quick return to the build site could have been explained by a significant vehicle failure or a major issue with SpaceX’s repair job – no point in continuing to test a vehicle that can’t be fully tested. On the exact opposite hand, a near-perfect test campaign in which all objectives were more or less achieved without major hiccups could also explain the quick return. In general, the evidence was in favor of the more optimistic explanation. Had a major issue been uncovered during the first post-repair cryoproof, it’s difficult to imagine that SpaceX would have completed the exact same test – in full less than 48 hours later.
However, SpaceX moved an in-situ Raptor engine installation stand towards Booster 7 and the orbital launch mount shortly before testing restarted, hinting – for the moment – that the company wanted to begin installing Raptor engines immediately after cryoproof testing. But mid-way through testing, the stand was moved back to its storage area and Super Heavy was instead removed from the mount and returned to the factory, adding a little uncertainty.
Concerns were immediately assuaged on May 17th when SpaceX was spotted moving Raptor engines from a production tent to the ‘megabay’ assembly building containing Booster 7. While the location of the new bay makes it difficult to peek inside from public viewpoints, preventing direct confirmation, it’s very likely SpaceX has begun installing new Raptor 2 engines on Super Heavy B7.
Additionally, confirming some of the more optimistic speculation about SpaceX’s decision to move Booster 7 back to build site, two of the three Raptor engines spotted on May 17th were also labeled “E26” and “E28.” Unless SpaceX’s engine numbering conventions have changed, the labels identify the engines as three of 20 ‘Raptor Boost’ engines that will ultimately populate the outer ring of Super Heavy B7’s aft end. More importantly, the installation of any Raptor Boost 2 (RB2) engines likely indicates that SpaceX has decided to install a full set of 33 Raptors on the booster before kicking off static fire testing.
To limit risk, SpaceX could have begun test-firing Booster 7 with just 1-3 Raptor engines installed and gradually added more as confidence grew. Instead, SpaceX appears to have accepted the added risk of losing 33 brand-new Raptor 2 engines in one fell swoop in return for the possibility of a much faster test campaign. If there are no major surprises during static fire testing, in other words, Booster 7 could be ready for flight far more quickly if the process begins with all 33 engines already installed. Installing Booster 7’s Raptors, heat shield, and aerocovers will be easier back at the build site.
Doing it all at once should also help prevent Booster 7 from suffering Booster 4’s fate and wallowing, unfinished, for months without completing a single useful test. If the gamble works, the first stage of a two-stage Starship could be ready for an orbital launch attempt in just a few months. If the gamble fails and Booster 7 is damaged, destroyed, or otherwise unable to pass the necessary tests, SpaceX will simply move on to Booster 8 sooner than later, having wasted less time on a more cautious Booster 7 test campaign.
-
It’s unclear how long it will take SpaceX to install all 33 Raptors, construct a heat shield around those engines, and finish buttoning up the rest of Booster 7. In an adjacent assembly bay, SpaceX appears to have nearly finished assembling a similarly upgraded Starship – Ship 24 – that’s first in line to ride Booster 7 into space. The company has also tentatively requested road closures for three 12-hour test windows on May 23rd, 24th, and 25th that either vehicle could use.
Tesla briefly offered one Robotaxi part in its Parts Catalog for your personal car, only to remove it just a short time after it was first noticed.
Tesla’s Robotaxi camera washer apparatus was briefly available for purchase on the company’s Online Parts Catalog. The camera washer was first noticed on Model Y Robotaxi vehicles about six months ago in Austin.
🚨 Tesla looks to have installed Camera Washers on the side repeater cameras on Robotaxis in Austin
pic.twitter.com/xemRtDtlRR— TESLARATI (@Teslarati) January 23, 2026
First noticed by Not a Tesla App, the Camera Washer entries appeared for the new “Juniper” Model Y under a category called “Halo,” which has also now disappeared. Interestingly, Halo probably is related to Tesla’s internal “Project Halo,” which was a project that aimed to retrofit customer-owned Model Ys into functional Robotaxis.
This hardware addition would likely be required for the vehicle to operate as a Robotaxi, as the Camera Washer seems to be a non-negotiable part of the vision-based system Tesla utilizes for self-driving efforts.
However, this part has since been removed and is no longer visible on the EPC.
Now the true question lingers: Why would Tesla add this Camera Washer to the Model Y parts catalog? Is it planning to make it available for owners to utilize on their own cars for personal use, or will it become a prerequisite for Robotaxi operation in customer-owned cars?
While discussing the upgrade options for Hardware 3 vehicles during the Q1 Earnings Call, Tesla CEO Elon Musk had said that the company could establish small, satellite shops that would upgrade cameras and self-driving computers. Perhaps this same strategy could be utilized for vehicles that want to be included in Robotaxi but do not have the correct hardware.
AI4 is currently represented as capable of unsupervised self-driving, and the same was said about HW3 at one point, only for Tesla to admit last quarter that it would, unfortunately, not be possible. Perhaps AI4 vehicles might need this camera washer as a prerequisite, just as HW3 cars will need that camera and computer upgrade.
This could be the first hint of that’s where we are headed.
Tesla has started rolling out a broader change to the ride experience for its Robotaxi fleet by silencing turn signals, but the change is certainly polarizing.
Tesla has generally made it clear that its purpose-built ride-hailing platform, Robotaxi, will cater to the rider in nearly every way possible. This includes having climate preferences, music, and other personal settings loaded up in the car as the rider enters.
But Tesla is taking it a step further by muting turn signal chimes altogether, a change that appears to be a way to make the ride more peaceful:
Tesla has finally turned off the blinker/turn signal noises in their Model Y Robotaxis.
This is a small update, but will definitely be noticeable for riders. It didn’t really make much sense to leave the turn signal sound on when it’s Unsupervised. pic.twitter.com/ITwx60PAMO
— Sawyer Merritt (@SawyerMerritt) July 27, 2026
However, there are a handful of people who are not thrilled about this change. Turn signals are a conditioned part of the human mind for those who ride in a car regularly.
Taking a turn without one feels strange and odd, and not hearing it click while activated could set off some alarms for riders, who might use the noise as confirmation that other drivers know of their intention to turn.
I kind of like it being on, threw me off when riding with Zoox who has had it disabled
— Dan Burkland (@DBurkland) July 27, 2026
Turn signal noises are still audible in customer cars, so if you use FSD in your personal vehicle, you will still hear the turn signal.
The move is certainly one that is unique, but not one that separates it from other ride-sharing services. In a normal car, the clicking sound confirms to the driver that the blinker is active. In a fully driverless Robotaxi, that feedback serves no purpose for passengers, other than peace of mind.
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.
I think Tesla FSD v14.3.6 is a regression from previous .3 branches
This version in particular has been incredibly hesitant, jerky, and indecisive at times. There’s actually been two drives that I have decided to not used FSD for the remainder of the trip. These were local trips… pic.twitter.com/YobHDOKRS6
— TESLARATI (@Teslarati) July 26, 2026
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.
I don’t want to get anyone excited but my Tesla running FSD v14.3.6 just:
✅ Pulled into an entrance at my local Sheetz that I routinely pull into manually but FSD never has entered
✅ Pulled into my assigned parking space at home despite many other spots being vacant https://t.co/ZUShvknTWO pic.twitter.com/83O5a2S0eh
— TESLARATI (@Teslarati) July 24, 2026
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.
Tesla briefly offered this Robotaxi part for your personal car
Tesla Robotaxi gets sweeping but polarizing change
