Search results

I feel your pain. FSD 12.3.3 on a brand new (400 miles) '24 MX Hit the curb when exiting a traffic circle. No challenging traffic.

Here's another, fresh this morning. FSD 12.3.3 '24 MX Hit the curb when exiting traffic circle - no evasive maneuvers

Total cost per kWh (and we’re on the EV residential rate) commencing at midnight is no less than $0.35 (& realistically more once municipal taxes etc. are multiplied) Superchargers in the vicinity are typically $0.40-$0.50

Wow, I admit I'm conscious of / motivated by the $ savings (who wouldn’t be for ~$30K+) - and California’s high cost of electricity. If my cost to charge @ home was 1/10 California’s actual (as it is in some locations) - I’d definitely charge at home overnight.

Wow. For $2K what an exceptional deal. FUSC has been worth tens of thousands to me. I’d purchase it @ $2K in a heartbeat. Or even $10K+ and still be in profit.

Yes, the current behavior - having to fight the door - is embarrassing. It’s a strong detractor against the brand. Tesla should return this feature to its former glory, exploit wing USS &/or use vision.

Same situation for me. Brand new X - single bench electronic actuator failed after 1 wk. now waiting 2 weeks for a replacement while it’s stuck @ 45 degrees. Bummer for a brand new vehicle.

updates? Can you be specific on what updates would be expected in this case?

Other than unsubstantiated rumors has the front bumper camera yet been delivered to any ModelX?

Do you have the actual generic (no personal info) text of the complete FSD transfer agreement? Can you post it?

Does anyone have the agreement text for either/both of; FSD transfer "Terms/Conditions" FUSC transfer "Terms/Conditions" My SA says I can't see it until I pay a non-refundable deposit on a new order

I admit those 2 days without FSD (reverting to AP) were …. a significant downgrade. I’ve been spoiled for so long.

No change. FSD was disabled, claiming map update required. This persisted for 2..3 days. I rebooted car. Then put it to sleep. No change. Then I posted to this thread to report same. And 2hrs later FSD returned without any change to either FSD or map version.

Less than 2 hrs after I posted to this thread, my FSD has reverted to a working/enabled state & no longer claims a map update is required. No change to reported versions of FSD nor maps.

I’m in the same boat with 11.3.3 And NA-2022.44-14515

Though I anticipate the answer is "nobody knows" .......😏 does anybody actually know which release will next reset FSD strikes?

I appreciate you're trying to help. Rest assured the strike happened during the circumstance originally described.

Not sure, but this is a 2017X (unaware of any recall for steering therein)

Confirmed. Strike applied. Confirmed. No audible warning.

Per title of the thread, FSD (10.69.2.4) has issued multiple strikes while it is stopped at red traffic lights. Torque was applied to steering wheel until the car was no longer in motion. Critically, no audible warning preceded the red wheel of death (FSD strike notice) while the car remained...

2017 X with mcu2, upgraded cameras & active FSD. Most of the time smart summon fails with “Vision system temporarily degraded”. Turning off sentry then turning it back on, sometimes clears this error & subsequently smart summon functions for a period.

I know this thread is the birthplace of “new false hope” but FWIW, TeslaFi is showing only 10% of current FSD participants are new additions. So that might imply Elon’s 60K -> 100K 🤨 window is yet to close. #elonMath

Here's the official certificate, showing time of death for my safety score. .... won't be missed.

It's happening .... 2022.12.3.20 downloading now to my 2017 X with MCU2 & upgraded cameras. Safety score 100. Currently running 2022.12.3.2

PSA - explicitly ask (demand) they keep service mode enabled during calibration drive...... Else you may find yourself bumped out of FSD beta eligibility. https://teslamotorsclub.com/tmc/posts/6659954/

Sorry to report 2022.12.3.20 isn’t an observable step change improvement. It remains timid and indecisive at many intersections (though spins the steering wheel less while pondering). Interventions are still warranted on suburban & well marked roads. It’s still a good 95% solution & I use it at...

I upgraded FSD yesterday on car #2 (2018 X. Not the vehicle that brought me to this thread). FWIW the updated vehicle has been in FSD since Dec 2021. It has recently tended to receive updates early in the “public” FSD queue. I haven’t figured out if there’s something causative involved in this...

Precisely. I thought that was standard procedure but I know better now.

Impact on my safety score.(recall it’s relevant for more than FSD and it was (only) Tesla service who degraded it). I get you’re frustrated …. and in good company.

Alas no. I tried @KArnold recommended method to ignore a false FCW and it completely reset my score, so this further mishap by Tesla service has a substantial impact. What a horrible 5 months it’s been. I’ll opt out as soon as I get the car back from Tesla service. And hope I can get the score...

Word of warning. Look what happened to my safety score (@ 100, for 5 months) when i left my car with Tesla service for brake replacement yesterday (they had it all day yesterday & today, I’m yet to collect). I guess someone at Tesla service was testing the brakes (without service mode enabled)...

Put simply: I have two cars - built ~1yr apart, ~same spec except for battery size. I drive them both, ~daily. Without exaggeration - I dread driving the car without FSD (enrolled in FSD beta queue / SS) and I love driving the car with FSD. $0.02

I disagree, but appreciate your perspective / opinion. We have FSD on the 2nd car - it's phenomenal. Truly a safety/convenience win in our circumstance, once the limits are understood by the driver. I use it every chance I get over the past ~5 months & much prefer; a car with no safety score...

~1000 TeslaFi cars just got pushed 2022.4.5.21 I got (re)pushed 2022.8.2 Yup.

I don’t know if you meant it this way or not - but this is by far, the funniest thing I’ve read on the internet, today.

You're right. I should have instead said the 2022.4.5.x branch (not 2021, sorry).

Hahah ... you got me ....this is what I've been reduced to. That said, I currently don't suffer any tangible downside from remaining on the 2021 branch.

To be clear, I received the 2022.8.2 update (2017 upgraded RCCB X) : but am not installing it, in case this later fork migrates vehicle subsystems (in particular ECU firmwares) which are subsequently incompatible with the 2021 branch. As posted above, I have previously had a software update...

2022.4.5.18 here …… call me superstitious (or perhaps just gullible, that would do).

Intresting. My SS has definitely been penalized for hard braking while TACC remains active (eg. precisely the scenario you describe). AP is the only state that I've found prevents hard braking from being recorded against SS. I haven't (for obvious reasons) attempted to re-confirm this behavior...

You’re making my point for me. SS has rewarded you for prioritizing your attention toward behaviors such as these (&/or running yellows), reducing safety for all. You are a better driver than autopilot. Your braking in these circumstances would be less aberrant (as experienced by other road...

Tesla’s “safety” score encourages drivers to run these lights by penalizing this class of braking.

Not sure if there's particularly rich data here, but it might suggest otherwise

Don't read too much into it - FWIW, I had my RCCB cameras installed a few days before the last (US) FSD intake, and still didn't make the cut (100SS) 🤷‍♂️ .........deep breaths........

FWIW, 2022.4.5.18 is being pushed exclusively to AP3 cars.🤓

It’s not. I too received this same update / notice. (2017 X) 😞

Good sleuthing. Thanks for clarifying.

You’re right @rajbsn - typo on my part. 🤦‍♂️

🤞 For the geeks : Thus far, all the (newly FSD) Canadian cars are upgrading from 2022.4.5.3 Don’t fret (yet). That doesn’t imply a lot - as the 4.5.3 build was predominantly distributed in Canada.

True. That said, FWIW 4.5.5 was deployed exclusively to AP3 vehicles (unlike 8.2 which includes all vehicles, even Mobileye). You might infer this is because it required something AP3 vehicles could provide (eg. FSD / shadow recording), or silently fixed something unique to AP3 vehicles (HW3)...