I think the guy is speaking more in conceptual terms that user input isn’t part of the design intent. Obviously FSD has yet to reach a point where it can choose its speed with 100% accuracy and there will be additional refinement with time. The largest fleets (3/Y) are well ahead of the CT fleet in terms of the model being trained. CT doesn’t even have the various drive modes so it is still early.The problem with this thought process (user input is always an error) is that FSD does not yet get the speed right all the time on its own. Its rather offensive and arrogant to imply the driver doesn't know best when it comes to speed.
Here in Texas FSD is frequently reading the speed signs on the frontage roads (roads along side highways) and slowing down to 45mph in the middle of the highway. Its annoying and dangerous.
Not to mention, what if its my preference to reduce my trip time by 10%, why will it not respect my speed settings? This guy is gas lighting us, or they have just made a poor choice when it comes to system design/user interface.
Perhaps, but that is not reality today. FSD chooses speed poorly at least a few times per trip, and Tesla currently accepts 0 liability. I am not in a Cybercab without human controls, I am in a vehicle that should at least attempt to meet the parameters set by its user. If they intend for this to be the behavior, enable it when it works better.You're going to have to get used to FSD choosing the speed, especially when the liability falls upon FSD and not you.
No, because it needs to choose the speed it can operate at. That's what voice notes are for.Don't get me wrong, I enjoy using FSD, but not honoring the user set speed is a deficiency.
Agreed. I turn off FSD super frequently for this. It's terribly annoying. Just go the speed I set. I wonder if the FSD team has done any case studies in aircraft automation. I personally don't actually want "full" self driving, all the time. I want high automation where I still ultimately have control more often than full self driving. I wonder if many others are in the same boat.Perhaps, but that is not reality today. FSD chooses speed poorly at least a few times per trip, and Tesla currently accepts 0 liability. I am not in a Cybercab without human controls, I am in a vehicle that should at least attempt to meet the parameters set by its user. If they intend for this to be the behavior, enable it when it works better.
Don't get me wrong, I enjoy using FSD, but not honoring the user set speed is a deficiency.
Dumb question...No, because it needs to choose the speed it can operate at. That's what voice notes are for.
-Crissa
The liability is still yours as in the drivers. I cannot hold Tesla accountable if FSD screwed up under my watch. IMO, there is just a lot of scope for improvement as with any new tech and it’s definitely happening.You're going to have to get used to FSD choosing the speed, especially when the liability falls upon FSD and not you.
Until then, mark when it's not going fast enough with the voice notes. Remember to say what the speed limit is, the lane width, and what speed you expect it to go.
-Crissa
Agree liability is key. Imagine your car approaches an intersection with green light right-of-way, with level 4 (future coming) fully functional FSD in control. At left crosswalk a mother with baby is walking into path of vehicle, and from right crosswalk an elderly in wheelchair approaches from opposite side. Possibly this conflict is due to faulty traffic light, but regardless, the vehicle cannot stop in time. The FSD programming has 3 choices, swerve left, swerve right, go straight and collide with both. If a driverless vehicle (robotaxi), makes the decision for the vehicle action, lawsuits ensue, it will be a big deal if/when the OEM (Tesla) assumes insurance liability instead of vehicle owner. When FSD is widely adopted/accepted (day is coming, IMO), the liability shift to OEMs from owners will be a paradigm shift in legal, insurance, and economics. OEMs will build this cost into vehicle price, accidents will decrease when FSD causes fewer accidents and are safer, and competition will force OEMs to assume liability since their software determines fault and innocence in accidents. Humans making speed and driving decision over-rides should shift the liability away from OEMs to themselves, which will no doubt discourage over-rides when doing so shifts economjc and ethic liability to the human.You're going to have to get used to FSD choosing the speed, especially when the liability falls upon FSD and not you.
Until then, mark when it's not going fast enough with the voice notes. Remember to say what the speed limit is, the lane width, and what speed you expect it to go.
-Crissa
The first week of FSD my truck attempted to run two red lights. There was no traffic so no big deal. I left voice notes and it’s been good ever since.Just throwing this out there… while in dad you can press the accelerator and speed up to you desired speed I. Case it’s going to slow and it will mostly maintain that speed… I’ve done it multiple times. On the other hand, has anyone had an issue with fsd eating a red light? To be fair, the light is new and was not on the navigation