eli_
Member
Yeah this is bad if they're breaking basic safety features like AEB, could be a recall-sort of issue.
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.
How tho?Just turn off AEB if you’re still on 10.3. It will resolve the issue
Sure, except for how AEB is a useful feature when implemented correctly, so I do not plan to disable it (nor do I plan to drive the car with the current build). Definitely glad that others are reporting it here, so that we can make decisions accordingly though!Just turn off AEB if you’re still on 10.3. It will resolve the issue
You do it in the AP menu. But you have to disable AEB before EVERY trip.Where do I disable FCW and AEB? I’m stuck on 36.5.2 and no install for 36.5.1. I have to go to work tomorrow and I’m worried!
I'm not going to touch any of that, because who knows if it'll reset something on the backend. Better to just leave it be and hopefully they'll just push a new build by VIN.Ok, my car reverted to 35.2, which under the current circumstances, is probably the safest thing to do. Should I request FSD beta again? I haven't done so, because I don't want to have to deal with the Saftey Scored again. Still, I am wondering whether we will be pushed a fixed 10.3 or not, if we don't request it and still have at least a 99 safety score. Wouldn't it be nice if Tesla would tell us what to expect and what we need to do?
I hope Elon stops listening to sycophants. Though, in this case I don’t think it had anything to do with that guy.Something went wrong here, probably due to Whole Mars Catalog, et al, pressure.
I'm still on 10.3. It's interesting Tesla seems to have chosen a work-around, although I wish they had given us a heads-up. AEB and FCW switches were both turned on in software (FCW to medium) earlier today. Now I'm still on 10.3 and both switches are set to off, and no one from my crew has touched them. Tesla must be turning off the misbehaving code as a quick fix. Maybe it's taking a while because they have to prepare a different set of changes for each hardware combination.Ok, my car reverted to 35.2, which under the current circumstances, is probably the safest thing to do. Should I request FSD beta again? I haven't done so, because I don't want to have to deal with the Saftey Scored again. Still, I am wondering whether we will be pushed a fixed 10.3 or not, if we don't request it and still have at least a 99 safety score. Wouldn't it be nice if Tesla would tell us what to expect and what we need to do?
Had 99 since friday morning no update eitherHas anyone gotten to 99-100 score over 100 miles this morning and gotten either FSD Beta 10.2 or 10.3? I just hit a score of 100 over 100 miles driven (after a reset yesterday) but no update yet. Sounds like with the issues from the 10.3 update leading to phantom FCW and braking I am not sure I want it until this issue is resolved.
I mean we used to drive around in cars for decades before AEB was a thing. You’re not going to die if you turn it off. But I agree, once it’s fixed, you can just turn it back onSure, except for how AEB is a useful feature when implemented correctly, so I do not plan to disable it (nor do I plan to drive the car with the current build). Definitely glad that others are reporting it here, so that we can make decisions accordingly though!
It’s better to not drive if there is no (working) AEB feature, if I do not have to (which I do not today, fortunately).
Normally I would say it calls into question the wisdom of frequent OTA updates…but this is a “alpha” type program so I guess you could argue that people should expect this. Not clear that that is a winning argument though.
In the end you have to have good QA I guess regardless of how frequently the updates are done. But normally they would do just a few carefully vetted vehicles, look for regressions, etc. then expand the rollout. Something went wrong here, probably due to Whole Mars Catalog, et al, pressure.
In the autopilot settings page. AEB random braking on 10.3 is really dangerous right now. I’d highly recommend turning it off, or downgrading off 10.3 if you can’t drive without AEBHow tho?
And apparently it turns on for every drive (normally - no idea what current behavior is), it is thought to be so important.But I agree, once it’s fixed, you can just turn it back on
Of course. I mean, I have Track Mode on my car; it’s not going to spontaneously crash without nannies. But I don’t need to go out, and this means I definitely am not going to go out and “try out” 10.3 (which sounds like hot garbage anyway, as fully expected). I’d feel pretty dumb if I chose today to not pay attention and pile into someone, totaling my car, when it would have been a fender bender with AEB enabled. Not that I have ever been in an accident where I hit someone, or have ever had AEB engage, but there’s a first time for everything!I mean we used to drive around in cars for decades before AEB was a thing.
I've always turned off FCW and AEB...it is dangerous and useless 99% of the time. It only caused me problems, never saved me from anything.I'm still on 10.3. It's interesting Tesla seems to have chosen a work-around, although I wish they had given us a heads-up. AEB and FCW switches were both turned on in software (FCW to medium) earlier today. Now I'm still on 10.3 and both switches are set to off, and no one from my crew has touched them. Tesla must be turning off the misbehaving code as a quick fix. Maybe it's taking a while because they have to prepare a different set of changes for each hardware combination.
For reference, my car is a May 2019 AWD 3.
It's the weekend. We shouldn't expect PR/legal to work on the weekend, just the FSD engineersThe silence from Tesla on this is really crappy
I just checked my 10.3, and the AEB and FCW switches are both set to off. I have to admit I don't recall their status when I did my drive this afternoon. I never experienced any of the issues with AEB or FCE on this 30 mile drive that I had been reading about but I'm wondering if perhaps these switches had already been automatically turned off by the time I took the FSD maiden voyage. The 10.2 had begun its download (I noticed it was up to 30%), and I didn't look at the App for several hours. I was surprised to find that 10.2 was not there to install and that I was still on 10.3, as I have later read happened to a lot of folks.I'm still on 10.3. It's interesting Tesla seems to have chosen a work-around, although I wish they had given us a heads-up. AEB and FCW switches were both turned on in software (FCW to medium) earlier today. Now I'm still on 10.3 and both switches are set to off, and no one from my crew has touched them. Tesla must be turning off the misbehaving code as a quick fix. Maybe it's taking a while because they have to prepare a different set of changes for each hardware combination.
For reference, my car is a May 2019 AWD 3.
That’s a horrible excuse. Why would you expect FSD engineers to work on the weekends but everyone else gets a free pass when there’s a major issue? They are pushing software updates over the weekend that are nearly causing accidents. This isn’t a small company we’re talking about here. Someone needs to get their ass out of bed or Elon can do his usual twitter PR.It's the weekend. We shouldn't expect PR/legal to work on the weekend, just the FSD engineers