Hey Elon since V11 has been stuck in the next month to a week or two cycle for 60 weeks now can we get a 10.420.x update so we can retire this 10.69 thread. Also the way V11 is (not) going maybe rename it lucky V13.
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 seem to me Elon has been putting the big stall on this whole time. The hardware has never been good enough for true FSD. The software can only do so much. ie: stall and feed slowly and keep the company $ rolling in at any cost.Hey Elon since V11 has been stuck in the next month to a week or two cycle for 60 weeks now can we get a 10.420.x update so we can retire this 10.69 thread. Also the way V11 is (not) going maybe rename it lucky V13.
Another push of 10.69.25.2 right now. TeslaFi up to 139 pending&installed and Teslascope 44, so about 3% rollout so far instead of yesterday's 1%.55 pending installs of 10.69.25.2 on TeslaFi right now. Roughly 1% of its FSD Beta fleet… Teslascope shows 19 pending also around 1%.
Even bigger push now. TeslaFi showing 494 pending&installed while Teslascope 130 so nearly 10% rollout now.Another push of 10.69.25.2 right now. TeslaFi up to 139 pending&installed and Teslascope 44, so about 3% rollout so far instead of yesterday's 1%.
We know some employees are now on V11.2 so at least they upgraded those employees from V11.1. Hopefully we'll see V11.3 rolled out sometime next week to the FSDb influencers.It seem to me Elon has been putting the big stall on this whole time. The hardware has never been good enough for true FSD. The software can only do so much. ie: stall and feed slowly and keep the company $ rolling in at any cost.
I just received notice that this version is available to install. But I probably won't be taking a drive to test it until this weekend.Even bigger push now. TeslaFi showing 494 pending&installed while Teslascope 130 so nearly 10% rollout now.
I just received notice that this version is available to install. But I probably won't be taking a drive to test it until this weekend.
Just downloaded it also... here's to hoping it's better!!Yeah. Mine is downloading. Since I had to park my car across from my house and not on my driveway as neighbors are doing roofing and siding work it's little slower. Pleasures of urban living
DittoJust downloaded it also... here's to hoping it's better!!
There are what appear to be all new release notes.Ditto
Just downloaded it also... here's to hoping it's better!!
It's my all new Time Masheen... and it craves electrolytes!!it will be better if you give your electric car more electrolytes. maybe autowiper AI will improve with brawndo as wiper fluid.
Reverse or backing up? It looks more like a tiny rollback . It even does it once before it reaches the farthest point. We have seen this much or more rollback posted previously in YouTube videos calming "Reverse".Surprised no one posted this, yet. Evidently 10.69.25.2 can reverse:
Edit: Video referenced in the tweet thread so you can judge for yourself. It's very slight, so the jury is still out
Surprised no one posted this, yet. Evidently 10.69.25.2 can reverse:
Edit: Video referenced in the tweet thread so you can judge for yourself. It's very slight, so the jury is still out
That looked odd to me. For one, there was no reason to back up as the car was not encroaching into traffic. The car was still a bit from the road. Second, the car did more of a slight back and forth wobble, not really backing up IMO. And the car stayed in D, so I don't know if that counts as reversing.
I suspect that V11 is just v10.69 with a feature flag switched or #define set that disables the mode switch to the legacy highway stack when entering a highway. It is reasonable to assume that all development going into v10.69 would have to also be present in v11, with the exception of changes to the legacy highway stack (and changes to that code are probably nonexistent anyway). So the entire branch probably consists of nothing more than some build settings changes on the same code base to flip the flag and show a different version number.If so it's curious they are spending resources fixing the 69 path when V11 is apparently so good and its release imminent. Path 69 remains hospice appropriate.