FSD 10.8.1 Resets Suspensions

[Shmoe]

Whoa guys... FSD Beta 10.8.1 release notes!!

"The update also resets FSD beta for those that were suspended. “We have reset the ‘Forced Autopilot Disengagements’ counter on your vehicle to 0,” explains Tesla. Those on FSD beta are tracked using Tesla’s Safety Score and improper usage means suspension from the program, if five occurrences of ‘Forced Autopilot Disengagements’ occur."

 

[Tam]

Whoa guys... FSD Beta 10.8.1 release notes!!

...Those on FSD beta are tracked using Tesla’s Safety Score...

The release note does not say the suspension is based on Safety Score. It is based on Forced Autopilot Disengagement. Forced Autopilot Disengagement is based on audio and visual warnings.

 

[Shmoe]

I didn’t write that. It came from an article. That wasn’t the point anyways though. I’m aware the safety score disappears. I’m more focused on suspension reset.

 

[boaterva]

No one is suspended based on the score, it’s on too many AP ‘ignores’ or ‘not paying attention’ according to the in-cabin camera or because the camera can’t see your eyes because you have a hat on. It was too sensitive on several releases and either locked people out or gave them two strikes.

The assumption is that the algorithm has been tuned and 10.8.1 is resetting strikes to start over (and give you five now, not only three).

 

[Shmoe]

Well aware of that. Just pretend that isn’t there. Focus on the suspension reset.

 

[Treydwg]

Anyone know when your autopilot counter is reset? I believe I have 2 now for pushing on accelerator while in autopilot. SMH!! I am on the new software 44.30.10 as of yesterday. My counter was reset on the previous version I guess from the updates on that version which is much more precise on watching the drivers attentiveness.

 

[Zoomit]

Anyone know when your autopilot counter is reset? I believe I have 2 now for pushing on accelerator while in autopilot. SMH!! I am on the new software 44.30.10 as of yesterday. My counter was reset on the previous version I guess from the updates on that version which is much more precise on watching the drivers attentiveness.

Check the Autopilot tab to see your count. I’m also on 10.9 and accidentally pushed beyond 80mph limit while using FSDb today. AP was disabled for the remainder of the trip, but my strike count is still zero.

 

[Treydwg]

Check the Autopilot tab to see your count. I’m also on 10.9 and accidentally pushed beyond 80mph limit while using FSDb today. AP was disabled for the remainder of the trip, but my strike count is still zero.

Oh really?! Let me check mine then. I did not know the counter is there for us to review.

 

[Treydwg]

Oh really?! Let me check mine then. I did not know the counter is there for us to review.

Thanks again! I’m actually at zero. I guess accelerating while in fsd autopilot does not count against you.

 

[Treydwg]

Oh really?! Let me check mine then. I did not know the counter is there for us to review.

Check the Autopilot tab to see your count. I’m also on 10.9 and accidentally pushed beyond 80mph limit while using FSDb today. AP was disabled for the remainder of the trip, but my strike count is still zero.

Just checked, and I’m at zero. I guess accelerating in fsd autopilot does not count against you?

 

[CaptUAL]

Models S Plaid is still 3, not 5.

 

[Slimvaio]

Models S Plaid is still 3, not 5.

Did you get 5 disengagements before the reset and now only have 3 chances?