Though I anticipate the answer is "nobody knows" .......
does anybody actually know which release will next reset FSD strikes?
does anybody actually know which release will next reset FSD strikes?
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
When is strike reset?
- Thread starter dogldogl
- Start date
AlanSubie4Life
Efficiency Obsessed Member
There's no reason for one since it's nearly impossible to get a strike (assuming proper use) with a properly functioning car, and they were just reset.Though I anticipate the answer is "nobody knows" .......
Well thatās not true for me. Iāve gotten two strikes because I rest my elbow on the door by the window and that didnāt put enough force on wheelā¦ and when I drive on long stretches of highway I am not constantly checking the screenā¦ I watching the road.
+1Though I anticipate the answer is "nobody knows" .......
Callahan27
Member
I received two strikes without any warning. I had a hat on both times and am guessing the camera couldnāt see my eyes. There was no warning just the red warning and a strike. Stopped wearing hat and havenāt had any issues since
AlanSubie4Life
Efficiency Obsessed Member
Iāll have to try wearing a hat! And keep my video camera rolling.
Still searching for an elusive video - not a single one exists showing how strikes occur with full context.
valem
Member
That's what I thought too.
I got FSD beta on 6/4/22 and never got a forced disengagement/strike until this week when I had 2 in the past 3 days.
Both while on NoA (highway) and not on FSDb
Both times it happened I was slightly pressing the go pedal to "coast" rather than regen on the downside of an overpass.
AlanSubie4Life
Efficiency Obsessed Member
valem
Member
Yes and with no warning. I ended up with 2 of these in 3 days so I'm on my last one.
I am afraid to lose FSD so for now I stopped using NoA or FSDB.
From now on I am going to engage it only if I am recording a video.
I really hope it doesn't happen again, but if it does and I end up in FSD jail, at least I will have video evidence.
AlanSubie4Life
Efficiency Obsessed Member
Sounds like a good plan.
I do wonder whether the monitoring in cars without the cabin camera is poorly vetted somehow, or more strict. Seems hard to understand how it could be more strict about the wheel torque though. Probably just defective somehow.
Video would be great in any case.
Iāve driven for hours now with FSD Beta 10.69.3.1, freeways mostly, and no issues. Torque nag has shown on occasion, but when I had altered the torque for one reason or another (due to conditions or whatever). In general, does not show up, though; in the steady state the unbalanced torque at 9 and 3 just dismisses it robustly, so it never shows.
valem
Member
The following is not my video, sadly I have not been using FSDb since the 2 strikes. I want to use it on video only in case it happens again but with all the attachments I have I can't find a good spot to show both the whole wheel and the display behind it. The camera would need to be where my face is.
Anyway, here's someone that ended up with the big takeover immediately message and a strike.
This is nothing like what I experienced... he doesn't keep his hands on the wheel in his video, and he had several "hands on the wheel" messages that he acknowledged mostly with scroll wheels.
In my case my hand was resting on the wheel, and I never had any "hands on the wheel" messages before the take over and disable message.
Why do you think he got the strike? Too many "hands on wheel" reminders?
short video - take over message only
full video - sped up
Last edited:
PACEMD
Active Member
The issue is with the new software for standard non-FSD AP or FSD/FSDb NOA. Meaning the separate highway software. Not specific to FSD or FSDb. I even turned off FSDb after these no-warning disconnects but still using NOA got a strike which counted against FSDb use.
AlanSubie4Life
Efficiency Obsessed Member
No idea really. Probably scroll wheels not enough to satisfy.
I would have liked to have had audio at regular speed of the original video though it was pretty long. Just to see how many beeps he got.
But probably scroll wheels insufficient.
Last edited:
PACEMD
Active Member
I should add that I do not know if by turning off NOA and FSDb and just using standard AP, if a strike under those settings would count against FSDb. It might.........I suspect it would........
valem
Member
I haven't tried myself, but read from several people that even if FSD is turned off in the AP settings, a forced disengagement on NoA would count against FSDb strike.
I don't know if NoA is also turned off though. Not willing to try it
PACEMD
Active Member
I can definitively tell you that turning off the FSDb setting and leaving on the NOA setting will allow a strike to count against FSDb use. If also turning off the NOA setting will or will not do the same I have no way of knowing or testing, now that I am in FSDb suspension land.......
PACEMD
Active Member
If you get a strike with FSDb and NOA turned off and using just standard AP please let us know......
Similar threads
