Mkl @MklOnX

Great post. Couple problems: 1. In software and systems engineering, having a well bounded override/preference is the correct pattern when a system is not yet perfect or removal of an override creates a lack of trust or causes failures (illegally speeding) 2. You’re having a false dichotomy with the “solve the problem” and “provide a control” view. You can have both because providing a control produces valuable supervised data for preference learning… 3. Trying to argue that someone can maliciously do 5 MPH in an 80 MPH zone as an excuse to not have a max speed control is like arguing a person driving a car shouldn’t have a brake pedal because a driver might slam on the brake at the wrong moment. 4. Removing user control too early is just as bad as giving too much control. You can reduce people’s trust in the system, cause higher disengagement, and inevitably frustrate people when they receive a speeding ticket causing them to have bad viewpoints of Tesla long term. I completely agree that Maximum Speed Control is not going to solve the underlying problem, but disagree it is counterproductive and something to be eliminated immediately. FSD should have maximum speed control until such time as better model versions supersede the need for it.

What you need to do is offer the ability for users to correct the listed speed limit by tapping the speed sign image on their screen so they can set the correct speed for that road. The model can’t even read all speed signage types, like “END ## MPH” signs as an example. You also need to hurry up and start lobbying for speed limit exemptions at the federal level so people aren’t getting tickets/citations because of your team’s inability to train the model to control vehicle speed properly.

@elonmusk @t_blom So it will finally back into my driveway instead of always pulling in?

Looks like Tesla is experiencing a server-side issue with Navigation currently. Several people are reporting full LTE but “Navigating without connectivity” @Tesla @DirtyTesLa @wholemars

@JSX423 @FSDyinzer @Tesla_AI It also can’t read “END ## MPH” signs either

I’d like to see if there’s any changes in your FSD behavior after a camera recalibration. Mine had all the same issues you’re experiencing (in 14.3.2) before I did a camera recalibration and it’s been mostly smooth since then with a minor hiccup here and then (now on 14.3.3 and still smooth after recalibration).

@FSDyinzer @MyLifeCoachMark Try a camera recalibration! I had those exact same issues on 14.3.2 and had several major critical disengagements until I did a recalibration. Since then, I’ve not had any of those issues and 14.3.2 and now 14.3.3 have been a lot better!

@ChuckCook Chuck, can you add "END ## Speed Limit" signs to your test protocol? FSD has been unable to read them properly and I'm still noticing 14.3.2 isn't able to recognize them. Example:

@wholemars Loving FSD 14.3.2 so far, everything is faster and the prior Stop-Sign slow behavior has decreased massively. They still need work on the car being able to recognize certain road signage like the END 35 MPH below, hopefully V15 brings that in finally!

@BLKMDL3 Still waiting on FSD to finally be able to recognize and act on these types of speed signs

@mikepat711 @AIDRIVR @DirtyTesLa @ChuckCook @JoeTegtmeyer @Teslarati @SawyerMerritt @teslascope @battleangelviv Great accounts to see the latest updates rolling out, but there are several accounts/people that do a better deep dive analysis (some on other platforms) that break it all down on the technical/engineering side while speculating what’s next/needed for FSD moving forward.

@mikepat711 Don't forget "END XX MPH" signs where there's no listed sign to change to!

@wholemars Tesla leases do not permit renting out your vehicle or using it for Uber Also, if the value of autonomy was greater than the price, the saturation rate of subscriptions would be higher than the purported 12-13% I see people claiming today

@wholemars @elonmusk I been calling that for years 😅 Next up on the chopping block: FSD Transfers

@EZebroni 👀

@EZebroni 👀😂

Demand forecasting is great and all, but you still need to have a density threshold goal every year. It sucks driving into a rural area and worrying about having enough range to get back home because there’s not enough superchargers in a region. You’re stuck going to point B and having to drive back to point A without being able to go to point C or D because there’s simply not enough density of SC’s yet. Tesla needs more small site locations for underserved communities in rural areas. You won’t find that in the data because the voting system is demand based—not density of availability based.

@Otunbakush1 Neither. Mine is already on when I go to open the door.

Now imagine, you’re the captain of an Airbus A321 and get to relax while the plane follows your navigation and perfectly taxis, flys, lands, and parks at the selected gate. Become incapacitated? No problem, it’ll just land itself at the nearest airport. Make Full Self Flying the next FSD…