Connect with us

News

Elon Musk shares Tesla FSD Beta 9.2’s behind-the-scenes technical release notes

Credit: @brandonee916/Twitter

Published

on

Tesla released FSD Beta 9.2 over the weekend, and while the update’s official Release Notes were identical to FSD Beta 9.2, there were a lot of improvements that were rolled out by the company under the hood. These improvements were so notable that Elon Musk stated on Twitter that 9.2’s release had to be moved back a bit to address some last-minute issues. 

The Tesla CEO then decided to share the technical release notes for FSD Beta 9.2, which explains every optimization that has been introduced in the recent update. Based on what Musk has shared, it appears that FSD Beta 9.2 is a massive step up from V9.1, allowing the advanced driver-assist system to navigate through inner-city streets in a safer and more confident manner. 

The following are the technical release notes for FSD Beta 9.2, as shared by CEO Elon Musk on Twitter. 

  • Clear-to-go boost through turns on minor-to-major roads (plan to expand to all roads in V9.3).
  • Improved peek behavior where we are smarter about when to go around the lead vehicle by reasoning about the causes for lead vehicle being slow.
  • V1 of the Multi-modal prediction for where other vehicles expected to drive. This is only partially consumed for now.
  • New Lanes network with 50k more clips (almost double) from the new auto-labeling pipeline.
  • New VRU velocity model with 12% improvement to velocity and better VRU clear-to-go performance. This is the first model trained with “Quantization-Aware-Training”, an improved technique to mitigate int8 quantization.
  • Enabled Inter-SoC synchronous compute scheduling between vision and vector space processes. Planner in the loop is happening in v10.
  • Shadow mode for new crossing/merging targets network which will help improve VRU control. 

Apart from the technical details of FSD Beta 9.2’s release, Elon Musk also hinted at the upcoming updates coming for the advanced driver-assist system. The CEO noted that FSD Beta 9.2 would be followed by V9.3 and V9.4, but after this point, Tesla may already release FSD Beta 10. V10 would feature “significant architecture changes,” as per the CEO. Musk did not explain further, though speculations suggest that FSD Beta 10 would be the update that would transition Tesla into a single FSD stack. 

Lastly, Musk provided some updates on the release date of the FSD Beta Download Button, which has experienced substantial delays. The CEO explained that the “Button” would probably roll out with Beta 10 or V10.1, which, based on the current release cycles of FSD Beta’s updates, would likely be in the next couple of months, barring any unexpected delays.  

“Beta 10 or maybe 10.1. Going to pure vision set us back initially. Vision plus (coarse) radar had us trapped in a local maximum, like a level cap. Pure vision requires fairly advanced real-world AI, but that’s how our whole road system is designed to work: NN’s with vision,” Musk explained. 

Don’t hesitate to contact us with news tips. Just send a message to tips@teslarati.com to give us a heads up. 

Advertisement
-

Simon is an experienced automotive reporter with a passion for electric cars and clean energy. Fascinated by the world envisioned by Elon Musk, he hopes to make it to Mars (at least as a tourist) someday. For stories or tips--or even to just say a simple hello--send a message to his email, simon@teslarati.com or his handle on X, @ResidentSponge.

Advertisement
Comments

Lifestyle

Watch Tesla’s “guardian angel” FSD feature take over for collision evasion

Published

on

By

Tesla’s Automatic Collision Evasion feature can be seen in one of the first owner videos of it in action.

Tesla owner Spencer (@scotsrule08) posted on Monday that the feature “worked flawlessly,” saying FSD reengaged itself just as he was about to hit a curb. Ashok Elluswamy, who leads Tesla’s AI team, shared the clip and wrote, “A guardian angel always looking out for you.”

The video arrives in the middle of a staged rollout. Tesla first shipped Automatic Collision Evasion with FSD (Supervised) v14.3.9 in software update 2026.27.6 earlier this month, which Teslarati covered as it reached cars. Update 2026.27.10, which began going out on September 19, carried the feature improvements with FSD v14.3.10, according to release notes tracked by Not a Tesla App. The newer 2026.27.11 build is now reaching another wave of vehicles.


The feature only runs on HW4 vehicles, and it requires an active FSD purchase or subscription with both FSD (Supervised) and Automatic Emergency Braking enabled. HW3 owners receive FSD v14.2 Lite in the same updates, but that build does not include collision evasion.

Tesla’s release notes describe two triggers. The first is an imminent frontal collision that braking alone may not prevent, in which case the car can activate FSD to steer, brake or accelerate around the hazard. That scenario is limited to highways below 85 mph, with no pedestrians or cyclists detected and no slippery road surface. The second covers a driver who appears inattentive, such as reaching into the back seat, or who seems to have switched off FSD by accident. Spencer’s curb clip appears to fall into that second category.

Tesla plans big safety improvements for Full Self-Driving v15

Once the system takes over, the accelerator is muted and light brake input will not cancel the maneuver. Drivers need to apply firm, deliberate steering force to take back control, and the car chimes to hand control back once the danger has passed.

Elluswamy recently noted that earlier hazard prediction, faster reaction time and better collision avoidance would arrive with FSD v15, the next major version.

Continue Reading

News

Tesla Roadster event gets delayed due to unfavorable weather

Published

on

Credit: Tesla

Tesla is delaying its event for the Roadster, moving it from this Thursday, October 1, to Thursday, October 15, due to unfavorable weather.

The company has said it has been tracking the weather for this Thursday closely with local meteorologists, and because the event can only be held outside, Tesla is making the call to delay it:

“We’ve been tracking the weather closely with local meteorologists, but given the severe conditions predicted & because this event can only be held outdoors, we’ve made the difficult decision to reschedule. New date is October 15. Additional details to follow.”

We are sure that this is bringing back PTSD for some Tesla fans, and we know it is not ideal, but this also reveals some things about the event. Tesla said that this can only be held outdoors, meaning it bodes well for the rumors that the vehicle could potentially hover.

Some believe that this was essentially confirmed by the FAA airspace restriction they were granted, but this could have been for a drone show or to keep drones from spying on the event.

Tesla Roadster is available for order once again following brief hold

The Roadster event has been long-awaited, and it is unfortunate that the weather is going to keep us all waiting a little bit longer.

The Tesla Roadster will be unveiled in Waco, Texas.

Continue Reading

Elon Musk

SpaceX turned a heralding moment for Starship into its greatest

Starship reached orbit despite losing an engine, deployed 26 Starlink V3 satellites on Flight 14.

Published

on

By

SpaceX’s Starship reached orbit for the first time on Monday, and for a few nail-biting minutes it looked like it wouldn’t. During ascent on Flight 14, one of Ship 41’s six Raptor engines shut down early, and SpaceX’s livestream host Dan Huot told viewers the team had decided not to commit to orbit. Minutes later, after what Huot described as a lot of conversation in the control room, the final poll came back in favor, and a roughly 19 second burn of a single Raptor pushed the ship into orbit about 170 miles up.

The reversal matters because SpaceX had written the exit ramp into the mission plan. The company said it would only fire the orbital insertion burn if flight controllers confirmed enough backup hardware remained for the deorbit burn, a condition Teslarati laid out ahead of the flight. Losing an engine was exactly the scenario that rule was built for.

Pressing forward fits Elon Musk’s history. Falcon 1 failed three straight times before its fourth launch reached orbit in 2008, with SpaceX nearly out of money, and Starship was developed by flying prototypes until they broke. What changed this year SpaceX going public, and with $SPCX sliding below its IPO price in July when Flight 13 slipped, the short interest climbed significantly, as Teslarati reported at the time. A Starship potentially lost today with revenue generating next-gen Starlink satellites aboard would have landed directly on shareholders.

That pressure showed up after orbit. SpaceX cut a flight planned to last nearly 10 hours to about three, moving splashdown from west of Chile to the North Pacific near Hawaii. SpaceX gave no reason, though Musk said this month the company was being extremely cautious about debris risk. The single Raptor for deorbit worked, and Ship 41 completed its flip and landing burn before breaking apart in the water, an outcome SpaceX expected. Musk has structured SpaceX’s governance to shield long term bets from market pressure.

The payload is the bigger business story. Musk posted that all 26 Starlink V3 satellites deployed and are “operating nominally.” Each V3 is rated for about 1 Tbps of downlink and 160 Gbps of uplink, so this single launch adds roughly 26 Tbps, about 10 times what a Falcon 9 load of V2 Mini satellites adds. The V3 is too large for Falcon 9, making Starship the only vehicle that can build out the planned 100,000 satellite constellation, at up to 60 per flight once it reaches routine service. Unlike the 20 V3 units on Flight 13, which reentered on a suborbital path, these will raise their orbits and could begin serving customers within weeks and bring in hundreds of millions of additional dollars in projected Starlink revenue.

SpaceX has already begun winding down Falcon 9 Starlink launches from Florida in favor of Starship. Reported targets put Flight 15 as early as October 19, leaving about three weeks to diagnose Monday’s engine shutdown before the next orbital attempt.

Continue Reading