You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
Do you have the latest version? Even in previous versions I was receiving warnings—not autopilot jailNo warning - goes straight to a strike.
I'm going to keep using a defeat device regardless of how it makes you feel. Tens of thousands of people use one. Not a single accident. Don't make a mountain out of a mole hill because you get an immense amount of satisfaction and a sense of productivity playing the moral superiority card.If you don’t use a Cheat device it won’t matter. Just a thought.
I actually didn’t share how I feel as that is irreverent. I offered a suggestion. Would however Love to see your data proven volume and Not an accident lol.I'm going to keep using a defeat device regardless of how it makes you feel. Tens of thousands of people use one. Not a single accident. Don't make a mountain out of a mole hill because you get an immense amount of satisfaction and a sense of productivity playing the moral superiority card.
Confirming this is wrong.No warning - goes straight to a strike.
Trying to dissuade someone from using a device designed to defeat safety features in a public environment is literally morally superior. As in, the position is derived from superior morals.I'm going to keep using a defeat device regardless of how it makes you feel. Tens of thousands of people use one. Not a single accident. Don't make a mountain out of a mole hill because you get an immense amount of satisfaction and a sense of productivity playing the moral superiority card.
Your experience is not consistent with many others, including myself.Confirming this is wrong.
I received an audio and visual cue to remove the defeat device. It was not an instant strike or AP jail.
I’ve gotten 2 disengagements!
One in morning, glanced at screen to see chargers level at destination with no warning visual or audio at all and red disengagement!
4 suddenly forced AP disengagement (red steering wheel on screen) prior to that, no warning at all.
I received two strikes without any warning
I think no-warning strikes are real
I even turned off FSDb after these no-warning disconnects
it’s an example of receiving the scary big red wheel not preceded by a warning
that there are now disconnects without warning
I also received two disengagements with no audio warning,
No warnings what so ever.
I don’t get any audio signal until the final red disengagement screen.
Confirming the same thing happened to me. Warning but no strike.Confirming this is wrong.
I received an audio and visual cue to remove the defeat device. It was not an instant strike or AP jail.
What version of the FSDb software? Meaning is 25.1 or 25.2 still giving the no-warning disconnects/strikes?Confirming this is wrong.
I received an audio and visual cue to remove the defeat device. It was not an instant strike or AP jail.
2022.44.30.5 for me.What version of the FSDb software? Meaning is 25.1 or 25.2 still giving the no-warning disconnects/strikes?
Just want to point out that my comment that you quoted was based on a version 10.69.3.1 prior to the Christmas releases (i.e.not a .25 release). These .25 releases changed the behavior (no idea how, but it is different - for one I think it explicitly mentions the defeat device at the disengagement - I don’t think 10.69.3.1 did though I could be wrong ).about the below involved in some kind of weird conspiracy.
That's not exactly right. With that software version, if the assumption was that of using a nag cheater, there were no nags at all until precisely 10 minutes and then there was a no-warning disconnect/strike. Meaning the part about nags and being satisfied with the scroll wheel during that 10 minutes are not correct. Precisely the opposite. But you understood that in your responses on the post you link.There were verified experiments in a version prior to December, 10.69.3.1, which ended up in “no-warning” strikes (it nagged (not about defeat device), nags were satisfied with scroll wheels, and then after 10 minutes of that, a strike was delivered). Can review the detailed posts where this was carefully tested by a helpful member of the forum - Autopilot buddy code is changed?
I can only go by what was reported in the referenced thread. I did not test this myself. That thread clearly indicates (with his particular test weight) that nags to apply torque were received.That's not exactly right. With that software version, if the assumption was that of using a nag cheater, there were no nags at all until precisely 10 minutes and then there was a no-warning disconnect/strike. Meaning the part about nags and being satisfied with the scroll wheel during that 10 minutes are not correct. Precisely the opposite.
Alan, go back and read your own response on the post you linked. You understood and acknowledged exactly what I am saying, which is in fact the truth.
So with a wheel weight, you'll get a strike after 10 minutes if you don't apply torque manually, no matter what you do with the buttons/scroll wheels, and stalks.
Yes it is noted in the car where FSD is enabled. Says how many and how many left. If you get to the last strike you get locked out for an unknown period. They recently claimed 2 plus weeks but I haven’t seen that confirmed.Since the Driving Score is no longer accessible, how can you check the number of strikes you may have?
Could you lose FSD usage then? If so, would there be a duration for this punishment?
In fact, when driving in heavy traffic, like in LA where you often needto change lane to exit or merge from one freeway to another,you often don't have too much chance to look at the dispaly,while staying focused looking at the cars in front and around you.In this situation you could miss the flashing blue warning,so I prefer then to disengage FSD but this defeat the full purpose of having FSD !!!!