Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

Automatic High Beams Suck

This site may earn commission on affiliate links.
I have MobileEye and the auto-highs work great. Dim instantly when an oncoming car is in range or I approach somebody from behind and instantly turn high when it's safe for me and other drivers again. Maybe Tesla should not have walked away from MobileEye.

Yes. Sad that AP2 cars turned out to be AP 0.5 in reality. Was really planning on loving my car and Tesla the company but Elon got greedy. An AP1 car today is a real bargain.
 
I just wanted to weigh in on this one (AP2.0). I think that this feature should be considered "Alpha" and turned off by default with a warning that this version of Auto High Beams should not be considered safe for regular use. They are slow to turn on in dark areas, they are slow to turn off when oncoming traffic is visible, and they can blink on and off in certain situations which could be confusing to oncoming traffic.

The next update with improvements could be called "Beta" with the unsafe to use verbiage removed, but should still default to "off".

Updates beyond that could be considered "Production Ready" ideally.

I've tried this feature in different areas and just didn't feel safe with it turned on. I'm surprised by how poorly it is implemented in its current state. Hopefully some more testing and enhancements will be coming soon. Otherwise, the current version is a safety hazard.
 
I just wanted to weigh in on this one (AP2.0). I think that this feature should be considered "Alpha" and turned off by default with a warning that this version of Auto High Beams should not be considered safe for regular use. They are slow to turn on in dark areas, they are slow to turn off when oncoming traffic is visible, and they can blink on and off in certain situations which could be confusing to oncoming traffic.

The next update with improvements could be called "Beta" with the unsafe to use verbiage removed, but should still default to "off".

Updates beyond that could be considered "Production Ready" ideally.

I've tried this feature in different areas and just didn't feel safe with it turned on. I'm surprised by how poorly it is implemented in its current state. Hopefully some more testing and enhancements will be coming soon. Otherwise, the current version is a safety hazard.

I completely agree and feel the same way. Embarrassing for a billion dollar company to release this. I could code similar functionality or better myself at a collegiate level. Unsafe and half-baked.
 
I tried auto again last night. It failed to turn the lights on in a dark stretch on a two lane road. Then an oncoming truck came around the corner, and it switched the high beams on. :rolleyes:
I've said for a long time, Tesla's software "engineers" don't seem to understand simple IF-THEN-ELSE logic. Maybe they also program everything in BASIC? PASCAL? LOGO? SCHEME? Oh wait, that's right, Tesla needs to use fleet learning and an advanced neural network in order to determine when to simply turn high beams on and off... and we should "cut them some slack" as they learn how to re-invent the wheel because Elon Musk couldn't zip up his big boy pants in his pissing contest with Mobileye.

If I were the owner of an AP2 car, I would not be happy. Six months after supposed "parity" with AP1 was promised Tesla still can't figure out how to get high beams and rain sensing wipers to work. The HVAC system still doesn't function properly, cooling like crazy in the mornings and not as much in the afternoons. Their super advanced cooling algorithm that takes into account solar insolation, and who knows what else, is garbage and doesn't understand basic stuff like it's hotter in the afternoon in Arizona than in the morning. Instead of just doing what other makers are doing that just works, Tesla has to step into it by reinventing something that doesn't need to be reinvented.

Tesla lacks one very important thing: Focus.

Tesla has a corporate culture problem, in my opinion. From their communication issues, to CPO problems, to Delivery Specialists who go AWOL, to innumerable and basic software bugs, to continually breaking promises to customers... it seems to me Tesla simply cannot focus on TODAY and getting that right. No, they are constantly distracted with what's coming. The employees at Tesla are constantly eyeing promotions and advancements, making their time at Tesla about climbing the ladder and food chain, or using Tesla as a stepping stone to get to Apple, Google, Amazon, etc. Nobody there seems to care about what's actually in front of them right now.

For Pete's sake, Trip Planner has been in beta now for TWO YEARS!!! It was in early March of 2015 that Elon Musk held his lame "End of Range Anxiety" press conference to announce a POS beta software feature that doesn't even work properly. And here we are, two years later, and it still doesn't work properly and it's still in beta. When, pray tell, will it not be beta and when will it actually work? The same can be said of Autopilot.

It's time customers and owners started judging Tesla not by what they promise, but by what they actually deliver and whether or not it actually works. Tesla wants us to believe it can deliver almost half a million Model 3s per year. This is coming from the same mouth that told us AP would have parity in December, that Trip Planner would end all range anxiety, who thought having the ability to name your car was important, and who believes it's more important to spend time and money creating Easter eggs than it is to deliver a functioning vehicle.
 
Last edited:
Rough crowd. Hopefully one of the software engineers will respond the way I did way back when, when one of my bosses said, "What do you mean that will take at least two weeks to code?? I could do that on my lunch hour." .. I responded, "I'll buy you lunch."

Meaning, of course, that I doubt this group criticizing actually understands the full complexities of what needs to be done. Things like a small hill is probably a challenge, since the ability to look forward is momentarily lost. We have no idea of the architecture and what code has been laid down for the next features to come.

If you don't feel comfortable running early software, don't use it. That seems pretty simple. And if you're upset, ask for your money back. That seems pretty simple, too.

Beating on the engineers when they likely didn't set the schedule? Totally inappropriate, imo.
 
  • Like
Reactions: mblakele
Rough crowd. Hopefully one of the software engineers will respond the way I did way back when, when one of my bosses said, "What do you mean that will take at least two weeks to code?? I could do that on my lunch hour." .. I responded, "I'll buy you lunch."

Meaning, of course, that I doubt this group criticizing actually understands the full complexities of what needs to be done. Things like a small hill is probably a challenge, since the ability to look forward is momentarily lost. We have no idea of the architecture and what code has been laid down for the next features to come.

If you don't feel comfortable running early software, don't use it. That seems pretty simple. And if you're upset, ask for your money back. That seems pretty simple, too.

Beating on the engineers when they likely didn't set the schedule? Totally inappropriate, imo.

Ask for my money back? That was the first thing I tried. They flatly refused and told me "to be patient" everything would work in a few more weeks. That was 6 months ago.
 
Strange thing happened last night. Coming home from a party on the same road that I took the video of my auto high beam functionality, they started sucking. I've never seen them work anything, but close to perfect. I have not installed any updates recently. Do they make minor adjustments to the software on our cars, without us knowing about it, in between the sw installations that we approve? Has anyone else seen this feature go from great to sucky overnight?
 
  • Informative
Reactions: oktane
I just wanted to weigh in on this one (AP2.0). I think that this feature should be considered "Alpha" and turned off by default with a warning that this version of Auto High Beams should not be considered safe for regular use. They are slow to turn on in dark areas, they are slow to turn off when oncoming traffic is visible, and they can blink on and off in certain situations which could be confusing to oncoming traffic.

The next update with improvements could be called "Beta" with the unsafe to use verbiage removed, but should still default to "off".

Updates beyond that could be considered "Production Ready" ideally.

I've tried this feature in different areas and just didn't feel safe with it turned on. I'm surprised by how poorly it is implemented in its current state. Hopefully some more testing and enhancements will be coming soon. Otherwise, the current version is a safety hazard.

I have an AP1 car and the auto high beam works absolutely perfectly 100% of the time. The reason I said he didnt have them switched on was due to the dash headlights "on" green lights and the ghosted out full beam light in the middle not being on...may be an AP2?
 
Rough crowd. Hopefully one of the software engineers will respond the way I did way back when, when one of my bosses said, "What do you mean that will take at least two weeks to code?? I could do that on my lunch hour." .. I responded, "I'll buy you lunch."

Meaning, of course, that I doubt this group criticizing actually understands the full complexities of what needs to be done. Things like a small hill is probably a challenge, since the ability to look forward is momentarily lost. We have no idea of the architecture and what code has been laid down for the next features to come.

If you don't feel comfortable running early software, don't use it. That seems pretty simple. And if you're upset, ask for your money back. That seems pretty simple, too.

Beating on the engineers when they likely didn't set the schedule? Totally inappropriate, imo.

I agree with bonnie in that the engineers probably don't deserve the blame. It is easy to imagine they are doing the best they can.

Tesla the company and the management, though, definitely do. Because it seems obvious they introduced a half-baked product on the market (and probably misled the public in Q4 regarding what EAP/AEB expected/will be in December 2016) for business reasons.
 
  • Love
Reactions: smac
I have an AP1 car and the auto high beam works absolutely perfectly 100% of the time. The reason I said he didnt have them switched on was due to the dash headlights "on" green lights and the ghosted out full beam light in the middle not being on...may be an AP2?

AP2 is a completely different beast when it comes to both the technology and even, surprisingly, many on-screen markings and how they work. So basically pretty much nothing that applies to AP1 applies to AP2, they just have to be considered as completely separate...