ChimpledPot
Member
I want 10.2 back. I won’t be able to drive my 1,600 mile road trip I have planned over a month on 10.3. FCWs for cars 200 feet in front of me every 3 seconds.
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.
It is all a conspiracy to jack up the Texas insurance rates to $1,000,000 a month.So many FCW warnings…I’m on Tesla insurance so I still see my score and I’m at a 49 today…and it won’t let me use FSD or even AP.
Oh so you got FSD beta with Tesla Insurance in Texas? Interesting, I'm still waiting.So many FCW warnings…I’m on Tesla insurance so I still see my score and I’m at a 49 today…and it won’t let me use FSD or even AP.
I emailed Tesla too.I emailed FSD beta about the problem, I hope everyone else did as well, cuz posting in here about it does nothing(I don’t think anyway). Is there any other way to communicate this to Tesla????
Same… just now. Some communication indicating they had to pull .2 and will rev 10.3 would help - as is I half expect this is automation booting me from the beta due to myriad (false) FCW events.View attachment 725101
Just got a second update. Assuming this is going to put us back on 10.2.
Same here. I tried and tested the fix of putting the car to sleep to "fix" 10.3 and that appears to have worked. I'm going to hold off on the update that just became available that I presume puts us back to 10.2.I also just got a second update but haven't installed it yet. I managed to force the car to sleep by following suggestions to turn off summon standby and sentry mode and let the car sit for about 30 minutes. It never worked for me before that, but now the autosteer icon is popping up like normal.
Same here with FCWs knocking down my score and then the install of 36.5.1 showing me out of beta and with a now lower Safety Score of 98 due to FCWs during first beta 10.3 drive this morning. Ugh. I have been a 99'er and finally late last night recieved the FSDBeta email notice that they will be pushing FSD Beta Version 10.3 to my 2021 Model S LR, and installed the update early this morning. One short drive with 10.3 and a couple errant FCWs despite nothing around at all (driving in middle lane and no other cars front or back.) Hope this doesn't prevent me from getting right back into beta / 10.3 when it's ready.So we had all the same issues today with false alarms constantly going off and the inability to engage full self driving. I too got the second update and it does appears to have pushed me back to previous version. I noticed that the driver safety score returned to the app which had disappeared after getting the beta. What stinks is my score is now 92 with a very high forward collision warning percentage even though I didn't really have any forward collision events. I was having to drive the whole time and with the car behaving so badly I was driving WAY back from cars. I also had one of those emergency brake events right in the middle of the highway from a forward collision situation that wasn't real.
I hope that the updated score doesn't affect my ability to get 10.3 back once they fix the issues.
Can confirm that the "update" today to 2021.36.5.1 definitely puts you back to 10.2 and with the return of a Safety Score, in my case a lower safety score due to the errant FCWs issue.Same here. I tried and tested the fix of putting the car to sleep to "fix" 10.3 and that appears to have worked. I'm going to hold off on the update that just became available that I presume puts us back to 10.2.
I tried with just my shirt off, no differenceI just tried driving naked, that didn’t help. In case anyone else was gonna try that
Most (including some OG Beta testers) are reporting that with 2021.36.5.1 FSD Beta is gone. They haven't gone back to 10.2. Are you sure you you still have FSD Beta 10.2?Can confirm that the "update" today to 2021.36.5.1 definitely puts you back to 10.2 and with the return of a Safety Score, in my case a lower safety score due to the errant FCWs issue.
I feel like their testing efforts need improved. This was by far the most serious but there and routinely head scratching regressions in random stuff.. They need to start paying attention to these gaps and put someone on improving it.