News
As OK’s anti-Tesla bill moves forward, its author believes a compromise is possible
The electric vehicle community in the United States took a collective gasp earlier this month when a proposed House Bill in Oklahoma unanimously passed a committee vote. The bill in question, HB 3994, aims to update and change parts of existing Oklahoma statutes related to the state’s auto industry. Now, this may sound harmless enough, but a look at the 70-page bill shows that companies like Tesla could lose out heavily if HB 3994 becomes law.
Tesla is already not allowed to directly sell its cars to consumers in Oklahoma, but HB 3994 could give the company even more headaches. What is particularly alarming with HB 3994’s language is the fact that it could be interpreted as a means to prevent automakers like Tesla from delivering and servicing vehicles in the state. This may result in Oklahoma-based Tesla owners being required to travel out of state just to have their vehicles serviced.
Tesla takes the bill very seriously, with the company urging owners on its Engage page to vote “No” to HB 3994. “If passed, this bill could force Tesla to close its existing locations in Oklahoma and prevent Tesla from shipping cars to anyone in the state, which would force locals to travel out-of-state to service their cars or pick up their new Tesla vehicles. Oklahoma should focus on increasing revenue and jobs in the state, not stifling competition and limiting consumer choice,” Tesla noted on its Engage page.
Oppositions and Risks
To state that Oklahoma-based Tesla owners are passionately trying to prevent HB 3994 from progressing further would be an understatement. Tesla owners are currently lobbying against the bill, with some even heading to the capitol last week to speak with the bill’s author, Representative Mike Dobrinski, who has an extensive background in the state’s auto sector. As per Dobrinski’s LinkedIn page, he was the Owner/Dealer of Dobrinski Chevrolet, Inc. until March 2017, and he was the Dealer/Owner of Dobrinski of Kingfisher, Inc., a Chevrolet-Buick-GMC dealership, until October 2018.
The Tesla owners’ talk with the Representative at the capitol last week was brief, according to information shared with Teslarati. Dobrinski highlighted the idea that HB 3994 is a way to protect Tesla owners in Oklahoma because if the EV maker refuses to cover its customers under warranty, then consumers will have no backup. Such a scenario seems unlikely, however.
It’s not just Tesla owners in the state who are against HB 3994. Oklahoma Senator Mary B. Boren, who drives a Tesla Model 3 herself, has openly criticized the bill. In a short conversation with Teslarati, Senator Boren noted that Oklahoma must let the product and the market decide if the state wants innovation to flourish. Initiatives such as HB 3994, which could result in automakers with no dealerships getting the short end of the stick, are counterproductive.
The Senator’s statements could very well ring true. Just recently, reports emerged that Tesla battery partner Panasonic has decided to acquire a factory site in the United States for the production of high-capacity lithium-ion batteries. Panasonic has reportedly shortlisted its preferred US locations to Oklahoma and Kansas. Senator Boren remarked that the presence of bills like HB 3994 could potentially discourage companies like Panasonic from investing in Oklahoma.
“If you have capitalistic laws being passed to protect a particular industry and their business model and to insulate them from the market demands that require them to adjust, then any innovative industry related to EVs will notice that — and they will notice that cronyism is at play. They will find friendlier environments,” Sen. Boren said.
Insights from HB 3994’s Author
The fact that HB 3994 unanimously passed a committee vote earlier this month shows that the bill is also seeing substantial support, despite its harsh repercussions on companies like Tesla and its local electric vehicle owners. When asked by Teslarati about the rationale behind the controversial bill, Rep. Dobrinski explained that HB 3994 is a request bill from the Oklahoma Auto Dealer Association.
“A request bill from the Oklahoma Auto Dealer Association, it seeks to strengthen the position of franchised dealers from the ever-increasing demands and requirements of their legacy manufacturers. Doing so requires addressing Direct Shippers, including Tesla, that are not currently regulated by the Oklahoma Motor Vehicle Commission like franchised dealers are. Proper legislation and regulation will ensure that existing service facilities may remain open and consumers will have additional protections,” Dobrinski noted.
Interestingly enough, the Representative admitted that while HB 3994 includes provisions that may be used to force Tesla into closing its service centers in the state, he does not expect that part of the bill to make it to HB 3994’s final iteration. “I do not expect that provision to be included in the (bill’s) final language,” Dobrinski later stated.
The Representative deserves praise for his honesty with HB 3994, though one may wonder why the controversial bill’s most heavy-handed provisions were included in the first place. When confronted by Tesla owners online, Dobrinski has maintained that HB 3994 is far from finished, but it has already opened the doors for communication among automotive businesses in the state.
“This bill, as introduced, is far from the finished product. It is forcing engagement from franchise auto dealers, legacy manufacturers, and new EV manufacturers, including Tesla. These folks are all talking now for the first time ever to work on a plan of regulation going forward that ensures competition and improves customer satisfaction under the purview of the Oklahoma Motor Vehicle Commission,” Dobrinski wrote.
A Price for Compromise?
Considering the statements of HB 3994’s author, it appears that the bill could partly be seen as a way to achieve a compromise of sorts between companies like Tesla, electric vehicle owners, and the state’s franchised auto dealerships. However, existing Tesla owners in Oklahoma fear that if HB 3994 passes into law, it could adversely affect not only their ownership experience but also their daily lives.
Cristen Winter Huber, a Tesla owner and a foster mother, is one of them. Being a foster mother, Huber is unable to take her foster children outside Oklahoma without a judge’s permission. According to Huber, the harsher portions of HB 3994 could effectively disrupt her family dynamic, and it might motivate her to leave the state.
“It’s not feasible for my family to drive out of state frequently. I’m a parent and foster parent. I have to get approval from a judge to take my foster child out of state. If I have to leave the state to service my car, I might as well move to a state that welcomes growth and innovation,” Huber said.
Jochen Hoppert, the President of the Tesla Owners Club of Oklahoma, noted that HB 3994 is not only a step in the wrong direction — it can have repercussions far beyond Tesla. The Tesla Club President also stated that so far, the EV maker’s service centers in Oklahoma City and Tulsa are proving that Tesla is serious about supporting its customers.
“Tesla is still not permitted to sell or deliver vehicles from those locations. We hope that will change in the future, yet this anti-competitive bill is clearly a step in the opposite direction. It’s worth noting that this move would not only negatively affect Tesla and the local Tesla community but other up-and-coming electric vehicle manufacturers wishing to do business in the state.
“Rep. Mike Dobrinski, the creator of this bill… has shared his perspective, which includes the notion that this bill would provide benefit to the consumer by allowing the state to manage the presence of warranty, service, and other such things for the consumer as required features of the electric vehicle marketplace. The Tesla service centers in Oklahoma City and Tulsa already demonstrate Tesla’s desire to provide its customers with such services,” Hoppert said.
Following its unanimous committee approval, House Bill 3994 has now advanced to the House Floor. But before the bill could become a law, the Oklahoma Governor would have to approve it first. With this in mind, Tesla owners and electric vehicle advocates still have some time to fight against the bill, or at least lobby for significant changes. Rep. Mike Dobrinski himself has been consistent with the idea that HB 3994 is still open for edits, so it may be a good idea for Tesla owners in the state to push their efforts even more from this point forward.
Those interested in speaking up and supporting Tesla’s efforts against Oklahoma’s HB 3994 could click here.
A copy of Oklahoma HB 3994 could be viewed below.
Hb3994 Int by Simon Alvarez on Scribd
Don’t hesitate to contact us with news tips. Just send a message to simon@teslarati.com to give us a heads up.
News
Tesla Full Self-Driving v14.3.6 review: a rare regression, but some bright spots
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
Musk’s massive Terafab project will get final location soon
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.”
News
Elon Musk reveals SpaceX performed secret Starship test on Flight 13
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.



