Stuck with .46 update?

[breeves002]

So much misinformation here!

Releases happen every four weeks. That's been going on for more than two years now. The releases are numbered with the week when development of that release is STARTED - they are not pushed out to the public until 4 weeks later, then the next release is started. The only exception to this pattern, based on what they did at the beginning of 2022 and 2023, seems to be a two-week break in the sequence after the new year, probably for holidays.

For the most recent three releases, 2023.42 was STARTED in week 42 (week of 15 Oct) and pushed out four weeks later on 13 Nov, then 2023.46 was started in week 46 (week of 12 Nov) and pushed out four weeks later on 7 Dec, then 2023.50 was started in week 50 (week of 10 Dec). It is now 4 weeks after 2023.50 was started, so it's no coincidence that 2023.50 was just released.

Specifically,

• .46 was NOT released late like you said. In fact, it was a couple of days early.
• .46 was NOT "messed up" like you said. It was perfectly fine. (You're probably thinking of .42, which did have a big bug that affected 3% of users and was fixed in TWO DAYS, but did not affect the overall release schedule at all.)
• .50 was NOT overdue at the time of your post like you said.
• .50 was NOT released late like you predicted. It was released exactly on time.
• "Delays" are NOT "compounding". Releases are being delivered on schedule as always. There is no "delay".

^^^^^What he said. Thanks for explaining this for people who don't understand. When I first got my R1S I was a bit confused at how it all worked but figured it out pretty quickly after doing some light reading.

I also want to emphasize how amazing it is they fixed the issue with .42 so quickly. That was super impressive to me after living with a Mach E where their software updates are horrible and don't always work right. Plus they brick cars fairly often.

Sponsored

 

[tjp74]

(You're probably thinking of .42, which did have a big bug that affected 3% of users and was fixed in TWO DAYS, but did not affect the overall release schedule at all.)

oh man... I mixed up .42 and 46 together. so confused... I assumed .46 was the one I received and it massed up my loaner T which I returned on Nov 21 (don't ask why would you update a loaner car) and then when I eventually got the notification on my own S, I just thought it was the same version fixed with correct certificate or what ever was bricking the system and thinking that will delay rest of release.
but if so, that means I skipped revised 42 (42.01) that was designed for ones that didn't get the original 42 and went straight to 46. is that even possible?

 

[elektrode]

Stuck on you
Got vampire drain deep in my truck that I just can’t lose
Guess there’s no update
Guess I’ll just have to wait

 

[VSG]

if so, that means I skipped revised 42 (42.01) that was designed for ones that didn't get the original 42 and went straight to 46. is that even possible?

Yes, that's possible. Each release seems to be stand-alone, so you can leapfrog releases just as easily as if you installed each and every one on the first day it was available.

Sponsored