OK, Nag.
Last month the SO and I took a trip down to Florida and back with the M3, 10.69.3.1 (I think) and all. Yep, nags.
So, let's talk about that.
First off, my general anti-nag bit has been to drive with one hand. That would work for a while, like, say, an hour or two. And then the car would get picky and start complaining. Switch hands. Stop for a while, then start up again.
This wasn't entirely consistent on a day-to-day basis. One day, complaints right off. Another day: Long delay before a complaint.
So, started experimenting. First off: My long-term habit has been to drive with two hands. With the beginning of the nag regime, started driving one-handed. So, went back to two hands. Interesting: On releases before 69.3.1, two hands got one a nag very quickly. On the release used to FL and back.. it didn't. But, eventually, it would get there.
As you all have noted, leaning to one side quiets the nags a bit, but then they come back. So, tried gently moving the steering wheel back and forth. Lean to the right, then lean to the left, and so on. 95% of the time, that worked. Humans are creatures of habit, so if one gets in the habit of doing that back-and-forth motion, eventually one stops thinking about it and the habit takes over.
But what about that 5%? Well, this is why the FSDb is beta software release. Once in a while, it would start nagging, even with the back-and-forth. And on one or two notable drives, it nagged no matter what I did: One hand left, one hand right, back and forth, and, yeah, I was looking out the front. Eventually on two of these (if memory serves) broke lock on the FSDb and inadvertently intervened. Which didn't involve swerving all over the road or anything, but was irritating. Funny bit: After sweating the next XX miles until the next scheduled meal/supercharge, started up the car again - and it didn't do that overly-sensitive bit.
I know that the general opinion around here is that when one gets a software load, that software load is Fixed in Stone and what you get is what you get, and what you get doesn't change until the next software load. I'm the maniac who suspects that Tesla is moving sliders around on a day-by-day or drive-by-drive basis, then collecting data to see how well whatever-it-is-that-they'd-like-to-know-about is working. Given that the whole driver-is-paying-attention algorithm is very much a work in progress over at Tesla, I wouldn't be surprised if this nag vs. no-nag algorithm is something they have a burning desire to improve.. and if that means running rats through the maze (that's us), well, that's what they'll do.
Mind you, there were days on that trip when I could go a couple hundred miles sans beep or boop, but would get the occasional blue flash from the screen when the car began to get irritated.
I haven't been driving around as much since getting back (at least, not in this car), so therefore can't attest to the nags or lack of on the short trips I've been doing. But it does seem that the first few miles of chasing around on FSDb always seems to have a distinct lack of nags. Probably while the algorithm is getting its data integrated.
Fun. Will be interesting to see what the next one or two point releases will be like.
www.ioniqforum.com
