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.
Hmm.. is it time for AP1 owners to file a class action suit?
![]()
Congrats!(to hold my new granddaughter!!)
I just got the 2017.42.1 update as well. Will report back once I get a chance to try everything out.
Ditto - +1 day with 2017.42.1 and so far Homelink also working fine.So far so good with Homelink... although this one will take a few days to test out to know for sure
Wow. Sorry to hear that I had the the best drive of my time with my 2017 s on .42 . It is happy in every road I have around here in Virginia, freeways included, light and heavy traffic) It is wierd the variability that seems to be from car to car. Have you tried a reboot? Or talked to the service center ? They might have a suggestion . . I’m Now worried if another .xx release might set me back. For me this one .42 is greatI went from .40 to .42 today.... terrible leap backwards for me in AP usability on my freeway commute. It's so weird why and how a release can actually be noticeably worse or better for some people. I was hoping after 50 miles or so it would get good again but carpool lane driving for me in now unusable again... annoying
Every time I got a new update....every single time, the first 20 miles was always horrible....then around 50 miles later, it got much much betterI went from .40 to .42 today.... terrible leap backwards for me in AP usability on my freeway commute. It's so weird why and how a release can actually be noticeably worse or better for some people. I was hoping after 50 miles or so it would get good again but carpool lane driving for me in now unusable again... annoying
This has to be placebo. There is no ongoing learning within your car on each release. Perhaps you just get used to what it feels like.Every time I got a new update....every single time, the first 20 miles was always horrible....then around 50 miles later, it got much much better
The general consensus is that 42.1 was merely a bug fix for a bug that only effected to AP2.5. (SAS)Blah, I just got 2017.42 a88c8d5 on Wednesday - is that because I have a crummy old 2.0 car?
Wow, AP 2.0 has def taken a very noticeable leap forward. Like a boss. I live up on a bluff, at the end of a windy 4 mile road. Today my X drove all the way down the hill on AP2, including navigating a fairly challenging spot where a side road merges in such a way that it's confusing which is the main road. Sixty mile drive to Portland today (to hold my new granddaughter!!) and handled the drive both ways - lots of curves, a couple construction zones, and no swerving towards trucks in adjacent lanes. No taking the edge of curves, right through the center.
I tend to agree that the "learning" is happening on Tesla's servers. However, it's entirely possible that there is some hardware calibration required after every update to address differences in camera angles. A brand new vehicle is unable to use AP until calibration is complete, so this seems entirely possible to me. Even when AP is active, I'm sure the calibration is on-going and continues to improve for a while longer.This has to be placebo. There is no ongoing learning within your car on each release. Perhaps you just get used to what it feels like.
No one can definitively answer that question, but one possibility is that Tesla simply hasn't developed a standard offset yet that applies across updates. Instead, they use a "mild" learning algorithm to help calibrate the camera after each update. There is the possibility that the updates are complex enough that calculating a standard offset is not possible (eg. if they've changed to a new algorithm). All speculation of course.Hm.... I would have thought 'calibration' would stick with the car and not need to be redone. Why wouldn't it? Someone convince me why this needs to be redone each time. I sure understand on a new car, but each firmware release? They can't create physical hardware offsets and write them out somewhere that's not overwritten each time?