
Stephen Gevers
3.3K posts
















Tesla reportedly testing Apple CarPlay integration: report teslarati.com/tesla-reported…



Yes, no doubt we are headed towards Full Autonomy. Sit in backseat and Post on X all day. BUT, we are not there. We are responsible for OUR vehicle and we want some control for now. Here are 7 examples where not having ability to override the speed control will NOW, in V14, lead to interventions/disengagement. I totally, 110% agree with Profiles (tied to speed) being controlled by Up/Down Scroll Wheel - 10x easier than pushing scroll wheel Left/Right. Proposed, for the meantime: - WHILE in SLOTH, a Left short press should temporarily low FSD speed by -5mph and a long press by -15mph. - WHILE in MAD MAX, a Right short press should temporarily increase FSD speed by +5mph and a long press by +15mph. This "temporary adjustment" would be cancelled upon scrolling Up/Down to a new Profile. @Tesla_AI - you are not paying our tickets and we do not want to Disengage because we cannot control towards the 'correct' speed. When you can correctly identify every speed zone and control 'properly' for every condition, then I think this can be reconsidered. @pduan



Set speed is a legacy concept from cruise control, where a user sets a speed target, and the car tries to match it. In the world of FSD, almost all user inputs are considered errors. The user simply specifies a destination and a driving style (chill, standard, hurry), and FSD will just do the right thing, including driving at the most appropriate speed. Max speed is introduced in case a user wants to impose a speed cap for certain reasons. Max speed is not the same as set speed, and by design, FSD will unlikely accelerate to match it. In most cases, max speed is irrelevant, so we hide it from the UI for simplicity. It will appear if you adjust it with the right scroll wheel or if FSD speed is being capped by it.

























