ÆCIII
Well-known member
IMO, the software engineer should not put out a statement like that without more context (such as "in concept", newer versions/builds will adjust to surroundings better", etc.), because as @Pops put it, the way it's worded it comes across as arrogant and it also makes the implementation sound like it's dumb and we're just going to have to live with it.
One some road trips as recent as August, for me FSD would refuse to adjust to a max-speed setting of 60mph, on a wide road purely straight for at least three miles in front of me, in a fairly rural area with no cars or known hazards around. It would often slip the speed down to 54mph and stay there, causing people behind to wonder WTH is going on and they'd pass me after getting annoyed. If I would nudge with the accelerator, the FSD would keep the max speed that way for a few seconds, but then start dropping back down. So, I'd have to keep repeatedly pressing on the accelerator, which got annoying and ultimately caused me to disengage and just drive it myself. Note this was not on an interstate or freeway but on a very wide nice straight for miles two-lane road in a sparsely populated area.
I'm definitely going to be checking the latest versions/builds for this same behavior on my next road trip.
So FSD does still indeed have some deficiencies in evaluating safe max speeds. I hope in future builds they improve on it. This is one of the areas FSD is being overly cautious in my opinion.
FSD is also a little too aggressive or under-cautious in other behavior areas. Major example of that right now is how FSD does lane changes on the highway, where it sweeps too close in front of another vehicle, while technically there is room but unless there is a tight traffic situation making it a tight squeeze, FSD should get ahead giving vehicles more clearance for courtesy instead of crossing lanes right in front of them for no reason, because it comes across as an intentional insult to some drivers. Earlier this week I had a driver get angry at me for that very reason.
I've also still not seen FSD detect, observe, nor reduce speed for a school zone yet in the hours when reduced speed is required.
Both FSD (and FSD programmers) still have some "learning" to do. Careful consideration of others to avoid behaving arrogantly should be a primary requirement. Giving other drivers room when changing lanes, or considerately including context when making harsh sounding statements, are examples of this.
FSD is still improving and making great strides, but some things seem like they should've obviously been mastered by FSD by now but they aren't. But we're looking at those things from a human perspective, while from a programming perspective, things that seem obvious often are not nearly that simple at all.
I think FSD will eventually get to where most of us really like it and will use it a lot. But, for that to happen (in addition to the improvements we're already seeing) I think the programmers need to allow FSD, AI, or themselves to eliminate these type obvious sore spots that annoy most drivers, while also allowing more control limits to be set in the FSD options to customize FSD behavior for one's comfort or preference level.
Let's hope the 'culture' within the FSD development team is emotionally intelligent enough to be considerate of us everyday drivers. Some of us actually do give proper turn signals, heed warning signs, keep attention/lanes, check blind spots and mirrors, and avoid placing distractions in the drivers view, while also staying within a reasonably safe speed. That engineer's statement makes it sound like the FSD development team is a little disconnected from us, so again I hope that statement was just one of limited context. We need the FSD development team to be able to relate to us and our driving, if they're ever going to make FSD a substitute option that we'll be comfortable using on a regular basis.
But considering the liability burdens and possibly what NHTSA is specifying, I wouldn't be surprised if the programmers' hands aren't tied at least a little bit for some things, which would explain possibly why we don't see certain options or why some of the above things are still happening.
- ÆCIII
One some road trips as recent as August, for me FSD would refuse to adjust to a max-speed setting of 60mph, on a wide road purely straight for at least three miles in front of me, in a fairly rural area with no cars or known hazards around. It would often slip the speed down to 54mph and stay there, causing people behind to wonder WTH is going on and they'd pass me after getting annoyed. If I would nudge with the accelerator, the FSD would keep the max speed that way for a few seconds, but then start dropping back down. So, I'd have to keep repeatedly pressing on the accelerator, which got annoying and ultimately caused me to disengage and just drive it myself. Note this was not on an interstate or freeway but on a very wide nice straight for miles two-lane road in a sparsely populated area.
I'm definitely going to be checking the latest versions/builds for this same behavior on my next road trip.
So FSD does still indeed have some deficiencies in evaluating safe max speeds. I hope in future builds they improve on it. This is one of the areas FSD is being overly cautious in my opinion.
FSD is also a little too aggressive or under-cautious in other behavior areas. Major example of that right now is how FSD does lane changes on the highway, where it sweeps too close in front of another vehicle, while technically there is room but unless there is a tight traffic situation making it a tight squeeze, FSD should get ahead giving vehicles more clearance for courtesy instead of crossing lanes right in front of them for no reason, because it comes across as an intentional insult to some drivers. Earlier this week I had a driver get angry at me for that very reason.
I've also still not seen FSD detect, observe, nor reduce speed for a school zone yet in the hours when reduced speed is required.
Both FSD (and FSD programmers) still have some "learning" to do. Careful consideration of others to avoid behaving arrogantly should be a primary requirement. Giving other drivers room when changing lanes, or considerately including context when making harsh sounding statements, are examples of this.
FSD is still improving and making great strides, but some things seem like they should've obviously been mastered by FSD by now but they aren't. But we're looking at those things from a human perspective, while from a programming perspective, things that seem obvious often are not nearly that simple at all.
I think FSD will eventually get to where most of us really like it and will use it a lot. But, for that to happen (in addition to the improvements we're already seeing) I think the programmers need to allow FSD, AI, or themselves to eliminate these type obvious sore spots that annoy most drivers, while also allowing more control limits to be set in the FSD options to customize FSD behavior for one's comfort or preference level.
Let's hope the 'culture' within the FSD development team is emotionally intelligent enough to be considerate of us everyday drivers. Some of us actually do give proper turn signals, heed warning signs, keep attention/lanes, check blind spots and mirrors, and avoid placing distractions in the drivers view, while also staying within a reasonably safe speed. That engineer's statement makes it sound like the FSD development team is a little disconnected from us, so again I hope that statement was just one of limited context. We need the FSD development team to be able to relate to us and our driving, if they're ever going to make FSD a substitute option that we'll be comfortable using on a regular basis.
But considering the liability burdens and possibly what NHTSA is specifying, I wouldn't be surprised if the programmers' hands aren't tied at least a little bit for some things, which would explain possibly why we don't see certain options or why some of the above things are still happening.
- ÆCIII
Sponsored
Last edited:
