|
|
|
|
|
|
by kube-system
1664 days ago
|
|
|
> 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]). |
|
|
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