Smh2210
Member
My wishlist for 10.3 is:
- Ability to recognize flashing yellow arrows and proceed through when safe
- Moving into the turn lane quicker across multiple lanes
- Toning down the speeds into turns
NoHas anyone received 10.3?
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.
My wishlist for 10.3 is:
- Ability to recognize flashing yellow arrows and proceed through when safe
- Moving into the turn lane quicker across multiple lanes
- Toning down the speeds into turns
NoHas anyone received 10.3?
Bruh I drove 1400 miles last weekend to try to get to 100 and only got to 99
nope, no update from 10.2 to 10.3 for me.Fsd 10.3 beta download status ? Did anyone get it yet ?
I’m thinking the same thing. I was thinking about doing this cute trick, but then I was thinking: I’ve driven 2,6XXmiles since 9.25.21 to get to a 99, why risk possibly throwing all that away not to get “it” when 99’s are theoretically next in line? I’ll wait it out. What a few more days/weeks/months/years?I'm thinking Tesla will catch on to the opt out/opt in hack pretty soon.
I don't think it's magical thinking to believe that the car's NN can be optimized. They probably haven't tried very hard as they've been more focused on just getting it to work. And truthfully, I don't see Tesla spending a lot of time on optimization for HW3 as they would rather spend that energy on migrating to HW4. So it's probably a moot point.Well, we know it's not capable TODAY because the current code needs to borrow significant compute from node B to run at all.
I know a few people think Tesla can somehow magically add a bunch more, better, capabilities (which from the current beta it clearly still needs) yet somehow drastically reduce the compute needed to do it... but when you ask how they just waive their hands and say optimization.... which seems like pretty magical thinking to me.
Tesla thought HW2 had enough compute for L4. Then they thought 2.5 did. Then they thought 3 did. Ultimately until they actually solve it, they don't know how much compute they need. It's possible even HW4 isn't enough, but we have no real info on that at all. We do have a fair bit on 3 and the vast preponderance of evidence is that it's insufficient.
The ideal case for Tesla is if they can get "perfect" L2 out of HW3 using both nodes... because we know HW4 is about 3x the compute, so that would mean they could run the "perfect" code in a single node with room to spare on HW4 and that could then support L4 since it could run redundant code on both nodes. But again from the current state of the beta, they're not there yet.[/B]
So, Monday. Maybe.Elon:
Regression in some left turns at traffic lights found by internal QA in 10.3. Fix in work, probably releasing tomorrow.
That’s my thought too. Let’s be honest folks they put the safety score system in place for a reason… Even if it does have some bugs in it (eg someone cuts you off etc). So if you have a low score like someone said they were at 74 - then drive more miles and pay closer attention.I’m thinking the same thing. I was thinking about doing this cute trick, but then I was thinking: I’ve driven 2,6XXmiles since 9.25.21 to get to a 99, why risk possibly throwing all that away not to get “it” when 99’s are theoretically next in line? I’ll wait it out. What a few more days/weeks/months/years?