2022.16.3: should I update?

So I’ll make this quick (don’t want to come off as impatient, as I know A LOT of people have been waiting in line for FSD).

I got my 2022 Model X plaid on June 17th. Didn’t want to enable FSD as I wanted to enjoy the car (with no limits) for a few days. During that time it received a 2022.16.2 update. — I’m not sure what software it was on prior to this.

Since then, I’ve been in the FSD beta queue. Driven over 500+ miles in the queue with 200+ of those being on auto-steer. My current safety score is 100.

I saw an update today, and I thought FINALLY, I’m in the FSD beta fleet. However, looks like it just for 2022.16.3 :/

*(Side note): I am worried that when I “opted in” I (at the time) didn’t have any driver profile selected. I had previously removed all the profiles and never “selected” a profile nor linked one to a keyZ When I finally selected my driver profile it made me “reconfirm” ALL my FSD / autosteer terms and conditions, but didn’t require me to “reopt in to the FSD queue”.

I guess here is my question(s).

1. Should I update to 2022.16.3? Will it make a difference? I know the FSD 10.12.2 is “technically” a downgrade. But I saw “one” install of 10.12.2 (beta) with a previous firmware of 2022.16.2 on TeslaFi (screenshot attached) — maybe it was a bug, but I was holding out hope. I don’t see any from 2022.16.3.

2. You guys think not having a driving profile selected is effecting my ability to get the FSD. I attached a screen shot (below) showing no driver profile attributed to trips, and now the more recent trips having a driver profile. If so, I can always opt out and opt in again. Just would reset all the miles I’ve driven.

Appreciate all the insight in advance. Again, I know many have waited months (if not years) so I get it may feel like I’m jumping the gun. TBH, I would be happy to just be patient if it wasn’t just so dang stressful to keep a 100 safety score all the time!

 

[glide]

That was quick?

 

[McKay]

That was quick?

Sorry?

 

[McKay]

That was quick?

Lol, well it started quick and very “quickly” became not “quick”. Lol, I actually thought I removed that. Oops.

 

[MY1stEV]

I would accept any updates for your car as they become available, especially "dot" releases which are mostly bug fixes.

Admission to the beta program is in batches, and just because you meet the criteria doesn't mean you are automatically in the next batch.

 

[McKay]

I would accept any updates for your car as they become available, especially "dot" releases which are mostly bug fixes.

Admission to the beta program is in batches, and just because you meet the criteria doesn't mean you are automatically in the next batch.

Okay, that is the confirmation I was looking for. Appreciate the feedback. I didn’t want to update and just regret it later cause it “pinched” my chances of getting in the beta sooner!

 

[LowlyOilBurner]

100 score for 3,472miles (since 05.20.22, delivery). Downloaded 16.3 this afternoon. Just gotta wait it out. Honestly, it’s not that hard to maintain a 100 score. A lot easier than it was back in September when I had gotten the beta back when we were on 10.2/.3. It sucks, and I do miss having the beta, but, unfortunately, this is the game we have to play.

 

[EVRider-FL]

(Side note): I am worried that when I “opted in” I (at the time) didn’t have any driver profile selected. I had previously removed all the profiles and never “selected” a profile nor linked one to a keyZ When I finally selected my driver profile it made me “reconfirm” ALL my FSD / autosteer terms and conditions, but didn’t require me to “reopt in to the FSD queue”.

I believe opting in to FSD Beta is not associated with a profile, it‘s associated with the VIN. You will see separate safety scores for each profile. Once you install the FSD Beta, it impacts every driver.