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.
I've tried my best to get my autopilot to fail in weird and wonderful ways and places to try and convince the mothership to send me this latest version so I can do my winding road test but alas I haven't gotten a notification and still am on .36 (which was objectively better than .34 on my winding test.)
Oh I'm quite sure they don't react that way... however, logic like that never stops me trying!I honestly don't think the mothership reacts in that way to fails on your car. Heck if anything, that would arguably be contrary to their claim that the data is anonymized and not identifiable….
Count yourself lucky that you're on .36 though — I'm still on .34.
it's because they don't "blink" back on...they transition or "fade" up (lol, don't know how to say it) to full bright.Forgot one issue, auto high beams.
The are quite specific to dim but are way to slow to fire up again after oncoming trafic passed. Between 2-3 seconds, must be fixed!
I usually practice engaging when at the side of oncoming car, meaning no driving in the dark. 3 seconds at 90 km/h in pitch black is just not good enough.
i noticed a message i've never seen pop up before, forgive me if people have noticed it in the past.
i tried to engage TACC/AP at only 18mph in a residential area at around the same time a bike crossed the road like 500'/1 block in front of me. i got a message that said: "Autopilot Unavailable" and just below that in smaller letters it said: "Object Detected In Path"
i couldn't grab a photo as the message stayed up for only about 2-3 seconds...so, is this something new?
Yep, 17.38 is now obsolete and now a subbranch is new. Wonder if it really fixes something in it or what. 17.38.4.
The logic seems weird. If it really fixed something in 17.38, you’d think every car on 38 would instantly get 17.38.4.
Definitely we need a spy on the dev team.Unless they are A/B (or A/B/C/D) testing between 17.34, 36, 38, and 38.4…..
The new statistics they collect seem to paint a much deeper picture of autopilot performance. It very well could be the reason why they seem to spend more time testing instead of rolling things out suddenly.
A/B testing on real cars on the road? What are we, guinea pigs? First they let us test the beta software for them, now they are testing on us.Unless they are A/B (or A/B/C/D) testing between 17.34, 36, 38, and 38.4…..
The new statistics they collect seem to paint a much deeper picture of autopilot performance. It very well could be the reason why they seem to spend more time testing instead of rolling things out suddenly.
They should remove the fade also. High beams don't need to be elegant.
….
Count yourself lucky that you're on .36 though — I'm still on .34.
...The touchscreen bit is really great for Tesla, because the established manufacturers are still trying to figure out this whole software thing... that level of software/hardware/UI integration is still beyond them... but not for long, watch out Tesla!...
You can thank Tesla for many things (assuming other companies adopt them too). Things like OTA, EV mass adoption, fast charging, large touch screens, etc. It's just taking them a long time to see the light...so true! the new Porsche Mission E is supposed to updated via OTA updates. can't wait, it can only get better from here.