PianoAl
Active Member
Thinking back, do you think it's possible that your car simply noticed that given the speed of the other driver, it had time to make the turn, so it pulled out. IOW, maybe it had nothing to do with the other driver yielding.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
FSD v12.x (end to end AI)
- Thread starter Buckminster
- Start date
-
- Tags
- #fixphantombraking autopilot chill is not chill elon is an ass fix fsd extreme late deceleration fsd does not commit to go fsd does not maintain proper speed fsd hard and late braking fsd jerky driving fsd late deceleration fsd stops too early too quickly fsd stops too far behind line fsd tailgating in city streets
That may be true but as long as this is FSD SUPERVISED it is important for FSD to accept input from the SUPERVISOR and not overrule it. That is the arrogance of elon seeping into the product ("all user input is error") and in this case when we override FSD errors, FSD responds back to us as if saying "la la la la, I'm not listening to you, la la la."
The same is true for speed changes where the system overrides what speed you want or need (in the case of the system insisting on the wrong speed limit.)
It does if you use the Automatic Set Speed Offset ... "Automatic Set Speed Offset allows Autopilot to drive at the speed that it determines is most natural. This considers factors like road type, traffic flow, environmental conditions, speed limit and the selected Full Self-Driving (Supervised) Profile setting (Chill, Average, or Assertive)."
I hear you. There's a long list of improvements needed some of which are downright dangerous. Unfortunately v12 behaves much the same as v11 with a clunky non-human feel of poorly refined/designed heuristics and simulated data. Apparently the team likes to maintain unrefined features so they can later claim neural net implementations are the only way to make it more human like. In any event the improvements have been glacial.
I was thinking about v12 improvements. Maybe acknowledging/responding to road humps, somewhat smoother steering, no more turn right to turn left, occasional improved cross traffic object kinematic estimation, driving narrow roads, rudimentary u-turns, and not overreacting to pedestrians on sidewalks. As in the past, some of these improvements may be at the expense of throwing caution to the wind.
Unfortunately probably not much but I'd like to see them start tackling the growing issue list:
- chill/aggressive mode select tied to accel/decel,
- eliminate tailgating,
- fix erratic speed/auto max,
- fix early turn signal,
- eliminate dry wipe,
- detect and appropriately slow for roadway dips,
- fix lane wandering,
- increase distance margin between wheels and roadway edge/curbs.
- human-like stop sign behavior,
- improved lane selection
I don't think FSD follows close enough. I think that will always be an issue due to driver preferences.
The biggest issue I still have is randomly entering the turn lane and reading minimum signs as the speed limit (made 100x worse with V12, even though it's not V12 on the interstate).
While I agree that following distance can be excessive at times, I largely think it is OK. However, there are times when it really does tailgate way too closely. In some cases, it is a result of how it handles a zipper merge, where it moves over right on the ass of the car in the other lane and takes its sweet time backing off. Fixing that should certainly be higher on the priority list than reducing the following distance.
Just like there are times when it signals at the appropriate point, but currently it usually signals way too early.
Make Minimal Lane Changes setting in the menu the persistent default, not reset defat to no for each drive.
I agree that for the mainstream release that you should be able to set it to default on. But for the early tester release it shouldn't, otherwise they might not get enough testing/feedback on how it performs.
But that would mean that they need to give the people currently classified as "early testers" a way to opt out and get put into the mainstream release path.
Is that even a thing anymore? Feels like no matter your status, early adopter, beta tester, purchase, subscription, free trial etc…. We all get the same supervised junk version
Tell that to the people on 2024.8.x that are still suffering with FSDb 11.4.9.
But I guess we will see when the next version of FSDS comes out. Will early testers be stuck on 2024.3.x while the mainstream path moves to 2024.14.x with the "Spring Update"?
dhanson865
Well-Known Member
Similar here, much smaller town, shorter turn lane
correct behavior for the left turn is to stay left of the gore, but as it approaches the FSD waffles between going left of it or right of it with a lunge to the right at the point so I disengage to get in the left turn lane before it's so late I'll have to cross the solid white lines.
12.3.4
really hoping 12.4 comes before May 6th and fixes a bunch of stuff or I'll drop out of the testing (unless they decide to give me another free month).
Last edited:
I wonder why it’s so hard for Tesla to just post updates on what they’re doing and why they’re doing it. How are random speculations better?Tell that to the people on 2024.8.x that are still suffering with FSDb 11.4.9.
But I guess we will see when the next version of FSDS comes out. Will early testers be stuck on 2024.3.x while the mainstream path moves to 2024.14.x with the "Spring Update"?
An even better idea: have the switch stay where we put it.
Agreed, but it varies of course. We should be able to tune in how closely we'd like to follow more precisely to an appropriate distance for conditions based on the drivers judgment.
That was an option, but as FSD progresses we will get less and less control. At some point, the Auto Max likely will be the only speed setting.
Similar threads
- Article
