News
SpaceX's "Christmas tree" is a Raptor engine for the holidays
SpaceX CEO Elon Musk showed off a holiday-themed Raptor engine “Christmas tree” with its very own star on top. Musk noted via a tweet that the company’s Starship propulsion team is “making great progress” building, testing, and refining the Raptor engines that will one day propel the next-generation rocket to Earth orbit and beyond.
On December 13th, Musk revealed that SpaceX is preparing to ship the 17th completed Raptor engine to the company’s McGregor, Texas rocket test and development facilities, the site of several dedicated test stands for the Starship engine. Likely one of the most complex rocket engines ever designed, built, or tested, Raptor relies on an exotic combustion cycle, referring to the specifics of how engines turn their propellant into meaningful thrust.
Raptor uses what is known as full-flow staged combustion (FFSC) and is the first FFSC engine to graduate beyond ground testing and actually fly, thus far having completed two flight tests in July and August 2019 as part of SpaceX’s Starhopper test campaign. In simple terms, the FFSC cycle aims to extract as much energy from a rocket’s propellant as efficiently as possible, resulting in what is theoretically the most efficient possible chemical propulsion from a given fuel and oxidizer combination.
Due to the sheer complexity required to achieve full-flow staged combustion, the engine type is incredibly rare and only two other (once) functional examples exist – one developed by Soviet engineers in the 20th century and the other built, tested, and inexplicably scrapped by NASA in the 2000s. In fact, the Soviet RD-270 engine’s thrust-to-weight ratio is likely second only to SpaceX’s own Merlin 1D engine, an absolutely spectacular achievement for a propulsion bureau operating in the late 1960s.
RD-270 had major development challenges and would likely have taken years of additional hardware-rich (i.e. destructive trial and error) testing to produce an engine actually capable of reliable flight. Before the program was cancelled in 1970, 22 engines were tested and no single RD-270 survived to perform a fourth static fire, a testament to the immense challenge of FFSC engines.
SpaceX appears to have had a much better go of it with Raptor, although many, many engines have definitely been destroyed or irreparably damaged since the full-scale engine’s February 2019 static fire debut. SpaceX CEO Elon Musk says that the 17th completed Raptor engine is almost ready to head to McGregor, Texas to kick off development and acceptance testing.
It remains to be seen when exactly Raptor engines will be mature and reliable enough to perform the 3-10 minute burns needed to send a Starship to orbit, let alone the Moon or Mars, but Musk appears confident that SpaceX is making great progress along those lines.
Per photos and info posted by NASASpaceflight.com earlier today, Raptor engine SN15 is already installed on a recently-reactivated McGregor test stand ahead of its first rocket-related test in almost half a decade.
Formerly used to test Falcon 9 first stages before SpaceX built a new stand for Falcon 9 and Heavy, that tripod stand has been reactivated for the sole purpose of supporting vertical Raptor engine static fire testing, which Musk says will simplify and expedite development by making test conditions much more flight-like. As of now, all subscale and full-scale Raptor engine static fire testing has been performed at horizontal test stands in McGregor, apparently resulting in wear and behavior that would not likely appear if engines were tested vertically.
SpaceX has gone through the same process with its Merlin engine programs, beginning with horizontal testing (far easier and simpler) but ultimately building a number of dedicated vertical test bays to ensure that engine acceptance and development tests can be performed under more flight-like conditions.
According to NASASpaceflight, SpaceX may have already fired up Raptor SN15 on its reactivated tripod test stand earlier this week, kicking off Raptor’s first Starhopper-free vertical static fire testing. It’s now unclear where the twin horizontal Raptor test bays will fit into future engine testing given Musk’s comments. More importantly, every completed Starship and Super Heavy rocket will require several dozen new Raptor engines and every one of those engines will likely need to pass acceptance testing (including static fires) in McGregor before they can be installed on a launch vehicle.
SpaceX’s Falcon 9 rocket already requires 10 engines per new booster and upper stage, a test burden SpaceX has only managed with the help of two Merlin 1D stands and one Merlin Vacuum stand, all vertical. In other words, it’s safe to say that the reactivated tripod stand is likely just the first of several vertical Raptor test stands to come.
Check out Teslarati’s Marketplace! We offer Tesla accessories, including for the Tesla Cybertruck and Tesla Model 3.
Tesla has introduced an enhanced visualization in its Supercharger navigation system, building directly on the Site Maps feature rolled out a few months ago.
This latest software update adds detailed 3D icons that represent specific vehicle models parked at charging stalls, offering drivers a more precise view of site occupancy and layout.
The Site Maps debuted in Tesla’s 2025 Holiday Update, providing 3D overviews of select Supercharger locations with real-time stall availability.
Tesla supplements Holiday Update by sneaking in new Full Self-Driving version
Drivers could see which spots were open, occupied, or out of service when navigating to supported stations.
Now, the system takes this capability further by rendering accurate representations of Tesla vehicles, including distinctions between models such as the Model 3, Model Y, Model S, Model X, and Cybertruck. These icons appear as lifelike 3D renderings, complete with recognizable shapes and proportions that match the actual cars charging at the site:
Supercharger update now shows type of Tesla at charger as well.
Pretty cool. pic.twitter.com/J3NRSIgM0m
— DennisCW | wen my L (@DennisCW_) June 2, 2026
This refinement improves the user experience during road trips and daily charging stops. As drivers approach a Supercharger, the navigation display now shows not just generic occupied markers but identifiable vehicle types plugged into each stall.
Blue indicators highlight active charging sessions, while other visual cues denote availability or maintenance status. The feature integrates seamlessly with the existing map interface, allowing quick assessment of the best available spot based on vehicle size and positioning.
Tesla continues to expand the availability of these detailed Site Maps across its global network. Initially piloted at a limited number of locations, the rollout has progressed steadily, with more stations gaining support in recent software versions.
Owners benefit from better planning, as the system helps identify compatible stalls and reduces uncertainty upon arrival. The update reflects Tesla’s ongoing commitment to refining its navigation and charging ecosystem through iterative software improvements.
In addition to model-specific icons, the enhanced maps maintain all prior functionalities, such as integration with nearby amenities and energy usage predictions. This ensures a comprehensive tool for efficient Supercharging.
As Tesla’s fleet grows and the network scales, such features play a key role in optimizing the overall ownership experience. Future updates may extend similar visualizations to additional sites and incorporate even more data points for drivers.
With this piggyback enhancement, Tesla demonstrates how small but thoughtful additions can elevate an already useful tool, making Supercharger visits smoother and more informed for its customers. The company is expected to broaden the feature’s reach in upcoming releases, further solidifying its leadership in EV charging infrastructure.
Tesla Full Self-Driving v14.3.3 driver monitoring was reportedly scaled back in recent releases, but a new version that was released in the early hours of June 3 aimed to do a better job of keeping those in control of their cars honest, according to release notes.
The release notes for FSD v14.3.3, via Software Version 2026.14.6.7 added:
“Improved driver monitoring system sensitivity with better eye gaze tracking, eye wear handling, and higher accuracy in variable lighting conditions.”
However, Tesla said this was already enabled in the first rollout of FSD v14.3.3 in late May. We tested it anyway, especially as the Standard Speed Profile seemed less-than-worried about what you were doing during operation.
I decided to try out the Hurry and Mad Max Speed Profiles for this test, and it gave me results that I would have expected. Tesla has evidently ramped up driver monitoring based on the Speed Profile you are using to travel.
The more aggressive the Speed Profile, the more on the hook you will be for taking your attention away from the road. Our testing showed that Mad Max was less likely to allow you to do normal things like change music or adjust navigation without getting an on-screen warning or nag from the driver monitoring system.
Hurry Mode Results
On Hurry, the driver monitoring system on FSD v14.3.3, via Software Version 2026.14.6.7, was more restrictive than Standard but less restrictive than Mad Max. I found that I could scroll through music options for a considerable amount of time, more than 30 seconds:
Roughly :31 between first touching the center screen and getting the first nag
— TESLARATI (@Teslarati) June 3, 2026
Standard gave me about 80 seconds of phone scrolling with absolutely no nags or warnings in a previous test. It is worth noting that this was a previous branch of v14.3.3, but Standard is such a goodie-two-shoes on the road that it is my impression it would not change much.
Here’s an 80-second phone nag test on Tesla FSD v14.3.3.
No alerts, no nagging, no annoyance. https://t.co/1dxvTOw5Cn pic.twitter.com/vYViFpjfoK— TESLARATI (@Teslarati) May 29, 2026
Mad Max Results
I spent the majority of the drive on Mad Max to see how it truly reacted to the driver having their attention elsewhere. While I did do a short phone test, I am aiming to steer away from those and use the center screen. I think it is a valid criticism that the phone test is dangerous and, not to mention, illegal in Pennsylvania. Changing the navigation and music is a more reasonable, more responsible, and safer test.
With Mad Max being the fastest and most aggressive Speed Profile, I anticipated this being the quickest mode to give me an alert that I needed to look at the road. That was the case with music:
🎥 Testing Tesla FSD v14.3.3 (via 2026.14.6.7) nags on Mad Max https://t.co/qZALU2OujY pic.twitter.com/XddOJ0D47x
— TESLARATI (@Teslarati) June 3, 2026
As well as adjusting Navigation, when I received two nags:
🎥 Testing Tesla FSD v14.3.3 (via 2026.14.6.7) nag while adjusting navigation
Two nags here https://t.co/qZALU2OujY pic.twitter.com/xa3dtaDG1L— TESLARATI (@Teslarati) June 3, 2026
These nags were more than reasonable, and I think it’s probably good that Tesla is ramping up the driver monitoring. I do believe that it should be relatively strict across all of the Speed Profiles, especially with phone use. When using the center screen, the nag intervals should be based on the speed profile you are utilizing at the time.
These driver monitoring adjustments are a great thing to have while FSD is still under its “Supervised” moniker, but I expect Tesla to continue pushing the limits on what it will allow, especially considering CEO Elon Musk has hinted that phone use is capable with the more recent versions.
You can watch the full drive on YouTube below:
Tesla has responded to the skeptics of its Robotaxi program by launching a massive expansion of the unsupervised program in its initial rollout city of Austin.
The company’s geofence, the enabled area of operation for rides, now covers the entire Austin Metropolitan area, an incredible move just days after media headlines attempted to discredit the ride-hailing service.
Those who have access to the Tesla Robotaxi app on their smartphones can now request a ride in any portion of the Austin Metro area. The company confirmed this on the social media platform X:
Unsupervised Robotaxi now in the entire Austin Metro area https://t.co/eXNBdarvVS
— Tesla Robotaxi (@robotaxi) June 3, 2026
This is Tesla’s fifth expansion of the geofence, with the others occurring in July, early August, late August, and late October 2025. It has remained at that size since October 26, but Tesla has now more than doubled that size.
It is now covering the entire area, including suburbs like Pflugerville and Manor, as well as I-35 highways, Gigafactory Texas, and the Austin-Bergstrom Airport.
The move comes just days after various media outlets highlighted the small fleet size of Tesla’s Robotaxi fleet in Austin, something that is a reasonable criticism but an understandable move on the company’s part to prioritize safety.
Tesla has expanded its Robotaxi geofence many times, but its fleet has remained at a relatively conservative size as the company continues to push safety as its most crucial metric.
The latest expansion is a key indicator of Tesla’s comfort level to expand the ride-hailing service. The move shows Tesla is scaling unsupervised autonomy, as it demonstrates that the company’s Full Self-Driving system has reached sufficient reliability for a broader real-world deployment, which is something the company has worked on extensively.
It also shows Tesla is game for a competition with its rivals in the autonomous ride-hailing sector. Tesla has often matched or exceeded competitors like Waymo in coverage area, despite its smaller fleet. This step highlights Tesla’s iterative, data-driven progress toward a high-margin, app-based Robotaxi network.
It’s not the absolute largest area expansion ever, but achieving full unsupervised operations across a major metro is a key moment in the Robotaxi story. It shifts the program from limited pilot/testing toward a more mature commercial service, while gathering the miles needed for faster growth.
Tesla piggybacks recent Supercharger feature with update that takes it further
Tesla Full Self-Driving v14.3.3 driver monitoring: We tested it
