[kube-system]

I'm not sure what the solution is, or whether it is even a design problem at all, rather than a societal/political/licensing problem.

My older vehicles had 3 controls for exterior lighting: parking lights, headlights, high beam. They were simple on-offs with feedback that indicated their current state. If people couldn't see your car, you couldn't see your gauges.

My 2021 Honda has SEVEN pages in the owners manual dedicated just to the headlight operation -- not counting the several other sections it calls out for related information. Some sections are called out as US specific and some called out as Canadian model specific.

Let's take just the high-beams for instance:

Flashing the high beams is a different physical control than turning them on. Activating the auto-high beam functionality is somehow not a separate control, but is done flashing your high beams, and there is a not-very-clear symbol in the instrument panel that indicates the current state. This means that when you flash your high beams, you are also changing the current state of the auto headlights. If you flash it an even number of times you will keep the same state, if you flash them an odd number of times, you change the state. Furthermore if you hold the stick in for 40 seconds, you disable the auto headlight feature entirely. If you hold it in for 30 seconds, you turn it back on. Yes, there are two independent levels of "on" and "off" respectively just for the auto-high beams.

It works perfectly fine when you know what it's doing, but it isn't something that a person would automatically know if they were someone who started driving when you turned on headlights by pulling a knob on the dash.

Besides that one specific gripe, there's 160+ pages dedicated to just to controls and the instrument panel alone.

Anyone who reads a modern 600+ page owners manual will learn something. The problem is that people don't, and sometimes the thing they didn't learn is important.

[wcunning]

I'm late to the party so no one will read this comment, but it's important for posterity. I own an F150 for moving things literally too heavy to move in even a well spec'd SUV. As a result, I cared a lot about things like load tie down points and weight ratings. In many ways, I learned an awful lot about that from the owner's manual, though in many other ways, I wish that they had better information about load placement in the bed and weight ratings of the bed liner in small areas, etc. You really can learn an awful lot that people should know about the limits of their vehicle from reading the manual.

On the other hand, we have legally required boilerplate sections like "how to decode tire ratings" that take up 20 pages, so there's definitely useless bloat.

[nawgz]

What you describe here is clearly insanity, although I am slightly unconvinced owner's manual page count is very relevant.

I read nothing and intuitively understood my car's controls, this is what I also agree should be the clear state, and it seems to me in some sense it should be legislated to prevent what you describe. It is an interesting point though, should each vehicle manufacturer be obligated to put a light stick with some exact set of controls for the headlights in?

[kube-system]

I don't think it is insanity. It's part of the complexity inherent to managing state with auto high beams. My Toyota worked differently but had other complexities. I just looked up a 2021 Legacy manual and it sounds like Subaru High Beam Assist works about the same way as my Toyota did.

The annoying thing about that design is, if I want to turn my high beams on manually, and the car decides that a street light in the distance is a vehicle, it will ignore my request to turn on my high beams when I push the stick forward. I then also have to set my primary headlights to manual mode in order to override the car. This requires turning the knob at the end of the stalk which is not backlit and therefore not legible while driving at night. This is one area where I like the Honda design better: I can always turn my high beams with one operation.

I think the page count is relevant because it is indicative of complexity and is likely inversely related to the number of people who read it.

While I am sure you probably do understand the controls on your vehicle -- I think it is important to note that the people driving around with lights in an improper state at night are also under the impression that they understand their vehicle's controls. They're just mistaken.

I personally wish licensing and enforcement was more stringent. But this is not politically possible in the US.

[nawgz]

> The annoying thing about that design is, if I want to turn my high beams on manually, and the car decides that a street light in the distance is a vehicle, it will ignore my request to turn on my high beams when I push the stick forward. I then also have to set my primary headlights to manual mode in order to override the car. This requires turning the knob at the end of the stalk which is not backlit and therefore not legible while driving at night. This is one area where I like the Honda design better: I can always turn my high beams with one operation.

It's an Outback for what it's worth, but... High beams work directly by pushing the stick forwards. I haven't experienced it denying such a request, only correctly toggling off when traffic is both oncoming and within a reasonable distance, but if it did behave incorrectly in this way, I would simply pull the stick back and push it forwards to re-activate high beams. I don't think there is any complexity in managing state with this implementation, it seems inherently obvious to me it would be this way. I am very surprised with everything else you've written here because it seems quite extraneous.

[kube-system]

> if it did behave incorrectly in this way, I would simply pull the stick back and push it forwards to re-activate high beams

In the Toyota that I had, if it thought there was an oncoming car, asking it to do the same thing again wouldn't result in a different outcome. Maybe Subaru's system is tuned better, or maybe my driving conditions are an edge case.

Either way, this was just an anecdotal tangent to support my above point that vehicle controls are more complex than they used to be. What was once one single boolean value is now a logic tree containing four boolean values ([auto headlight system engaged][vehicle detected ahead][vehicle speed within operational parameters][highbeams commanded by driver]).

[nawgz]

> In the Toyota that I had, if it thought there was an oncoming car, asking it to do the same thing again wouldn't result in a different outcome

Why wouldn't the result of the action the second time be based on exclusively the stick's position and the current state the vehicle is in? Then it is a pure function of time. If they truly mixed up previous states in there, and somehow it's aware that in the history of positions it was at this position and at that time it rejected your request so it will also reject it now, that's braindead and you should phone Toyota and scream at them

My car's headlight's current state is a pure function of time T and position P. That's my mental model and I haven't observed deviations. I will look at these manuals later perhaps to understand if they really argue there are more stateful factors than this