News
SpaceX fires up Starship and Super Heavy booster hours apart
SpaceX appears to have successfully fired up a Starship and Super Heavy booster hours apart, testing a total of three new Raptor 2 engines on the two rockets.
SpaceX says it completed a two-engine static fire with Starship 24 less than three hours after the company successfully ignited a Raptor 2 engine installed on a rocket prototype for the first time. That earlier test, performed by Super Heavy Booster 7, was also the first time SpaceX used its new Starbase orbital launch site to support a static fire test and the second-ever static fire of a Starship booster prototype. Had the company called it quits after Booster 7 survived its first intentional trial by fire, it would have still been an exceptionally successful day.
But SpaceX wasn’t done.
Instead, after Booster 7’s seemingly flawless single-Raptor static fire at 5:25 pm CDT, SpaceX loaded Starship 24 with a small amount of liquid oxygen and methane propellant and ignited two of the ship’s six engines around 8:18 pm. It was not initially clear how many engines were involved but a tweet from SpaceX later confirmed it was two. More likely than not, one of those engines was a sea level-optimized Raptor with a smaller bell nozzle and the other was a vacuum-optimized Raptor with a much larger nozzle.
Almost ten months ago, Starship 20 – SpaceX’s first potentially orbital-class Starship prototype – began static fire testing in a somewhat similar way. Its first day of static fires began with a single Raptor Vacuum engine and ended with a simultaneous RVac and sea-level Raptor test in October 2021. In some ways, SpaceX has been a bit less cautious with Starship 24, which is the second potentially orbital-class prototype to begin proof testing. Ship 24 already has all six Raptors installed, whereas Ship 20 only had four of six engines installed during its first static fire tests. SpaceX also took about three weeks to progress from Ship 20’s first static fire test to its first static fire of all six engines, whereas it appears that Ship 24 could potentially attempt its first six-engine test just a few days to a week later.
On the other hand, Ship 24’s path to its first static fire was substantially longer than Ship 20’s. Ship 20 completed its first static fire test(s) just 25 days after its first proof test, referring to the process of verifying that the prototype was in good working order before moving on to riskier testing with flammable propellant and intentional ignitions. Ship 20 also completed its first six-engine static fire 46 days after testing began. Ship 24, meanwhile, took 75 days to go from its first proof test to its first static fire – almost three times slower than Ship 20, a prototype that was essentially the first of its kind.
It’s possible that Ship 24’s upgraded Raptor 2 engines are partially or fully to blame. Instead of jumping straight into ‘hot’ Raptor testing like Ship 20, which began that particular campaign with a partial-ignition preburner test, SpaceX put Ship 24 through seven ‘spin-prime’ tests before its first static fire. For Raptor, spin-primes test the ignition step before preburner ignition, which is itself a step before main combustion chamber ignition (where the engine starts to produce meaningful thrust). Raptor startup procedures likely involve flowing high-pressure gaseous helium, nitrogen, or propellant (oxygen/methane) through the engine to spin up its turbopumps, ‘priming’ them for preburner and main combustion chamber ignition.
-
On Raptor 1, the preburners would ignite once a high enough flow rate was achieved, producing hot gas that the main combustion chamber would mix and ignite one last time to start the engine. In a recent interview with Tim Dodd (“The Everyday Astronaut”), CEO Elon Musk revealed that SpaceX was able to “remove torch igniters” from Raptor 2’s main combustion chamber (MCC). It’s unclear if that means that Raptor 2 now has zero MCC igniters, but a major change in the overall ignition process could explain why the start of Ship 24 and Booster 7 engine testing was so sluggish. So could the unintended explosion Booster 7 caused when SpaceX attempted to spin-prime all 33 of its Raptor 2 engines at once.
Regardless, SpaceX has finally crossed that particular Rubicon and, with any luck, Raptor 2 testing will begin to speed up on both Starship 24 and Super Heavy Booster 7. SpaceX has test windows scheduled on August 11th, 15th, and 16th. A warning distributed to Boca Chica, Texas residents on August 10th confirmed that the company intends to perform at least one more static fire test on the 11th.
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.
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.
The sheer scale of TERAFAB is going to be insane.
Elon said it wouldn’t be suitable for anywhere on Giga Texas property because it’s too big:
“We couldn’t possibly fit the Terafab on the GigaTexas campus. It will be far bigger than everything else combined there.
Several… pic.twitter.com/79GbhNNuf4
— TESLARATI (@Teslarati) March 23, 2026
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.”
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.
— Elon Musk (@elonmusk) July 25, 2026
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:
This flight intentionally had much higher acceleration to test how well the heat shield tiles would remain attached at high dynamic pressure.
Test was successful.
— Elon Musk (@elonmusk) July 25, 2026
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.
Tesla claims supplier is holding Cybertruck production hostage
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
