EVNow
Well-Known Member
Not sure why they have 80 mph limit now - so, no idea what might fix that. But since there has been no talk of that in 11.x, I would not hold my breath.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Wiki MASTER THREAD: Actual FSD Beta downloads and experiences
- Thread starter jebinc
- Start date
it's probably just a matter of collecting data of vision vs radar performance of AP at around ~80mph. Once vision consistently matches radar, i'm sure they'll open up the next step change. It was similar to when they did the 75->80mph unlock. It will probably happen randomly outside of any FSD related update. Could happen soon, could never happen...(hopefully not)
Who are you and what have you done with "optimistic, every update is mindblowing" powertoold
But jokes aside, I just did a drive on 10.10.2, and i'm actually pretty impressed compared to 10.9. It's smoother, the braking is less jerky, no weird phantom brakes, and changing into a turn lane over the line instead of jerking the wheel as soon as the lane opens are welcome improvements.
Again, just first impressions, but it seems MUCH improved over 10.9. 10.8.1 was good too, but i can't say how it compares to that yet.
Sadly I find that pretty much everything "auto" on my car is better turned off. These cars can do lots of things, just almost none of them well.
EVNow
Well-Known Member
Apparently only wi-fi ? Makes sense given much increased numbers (30x from 10.1).
Car sitting at work and shows waiting for wifi to download the update. I believe this is the first FSD beta update I've had that hasn't downloaded over the cellular connection.
10.10.2 didn't make much difference in my brief testing today. In fact some things seemed worse:
* Freeway exit starts off as 1 lane, widens into 2, the car needs to stay left; it started off sticking to the left as before, but did a wild swerve to the right just as the road widened. Then it swerved back into the left lane. Has not done that before with the same exit, even before FSD beta.
* Left turn with 3 target lanes; leftmost lane is a left turn only, right 2 lanes are straight only. I needed to go straight. The car decided to turn into the left-only lane and stop behind the cars waiting for their arrow.
* 2 right turns around some pylons (tall white ones) it wanted to swerve into them so I disengaged. Previously it would get nervous around them but not try to approach them so closely.
* Couple left turns felt like they might clip the median so I disengaged. Both had a turn lane next to me with more cars; I didn't trust it.
* So much for right-of-way improvements - at 4-way stop it yielded to 2 parked cars (not unusual), quickly recognized that they weren't moving (improvement), but then continued sitting at the stop sign. I let it do so for 5-10 seconds until other cars appeared in the distance, then nudged it through. Haven't had the same issue at that intersection before, but maybe it's a fluke as I've had other intersections in my area sporadically fail the same way.
* Maybe the fault of new maps, but a freeway exit I've taken many times wasn't recognized, and instead of slowing down to 55 or 50 as normal, it kept going 75. After slowing down for some cars ahead it merged left and tried to accelerate back to 75. Finally dropped to 50 as it crossed the threshold where NoA would end in the past.
* Street in my neighborhood is now recognized as 30mph. It's a regular 25mph residential street with speed bumps.
The only true improvement on this drive was one unusual left turn that it has failed at a basically 100% rate; today it was smooth and the car pointed onto the correct street instead of aiming at either oncoming traffic or parked cars.
* Freeway exit starts off as 1 lane, widens into 2, the car needs to stay left; it started off sticking to the left as before, but did a wild swerve to the right just as the road widened. Then it swerved back into the left lane. Has not done that before with the same exit, even before FSD beta.
* Left turn with 3 target lanes; leftmost lane is a left turn only, right 2 lanes are straight only. I needed to go straight. The car decided to turn into the left-only lane and stop behind the cars waiting for their arrow.
* 2 right turns around some pylons (tall white ones) it wanted to swerve into them so I disengaged. Previously it would get nervous around them but not try to approach them so closely.
* Couple left turns felt like they might clip the median so I disengaged. Both had a turn lane next to me with more cars; I didn't trust it.
* So much for right-of-way improvements - at 4-way stop it yielded to 2 parked cars (not unusual), quickly recognized that they weren't moving (improvement), but then continued sitting at the stop sign. I let it do so for 5-10 seconds until other cars appeared in the distance, then nudged it through. Haven't had the same issue at that intersection before, but maybe it's a fluke as I've had other intersections in my area sporadically fail the same way.
* Maybe the fault of new maps, but a freeway exit I've taken many times wasn't recognized, and instead of slowing down to 55 or 50 as normal, it kept going 75. After slowing down for some cars ahead it merged left and tried to accelerate back to 75. Finally dropped to 50 as it crossed the threshold where NoA would end in the past.
* Street in my neighborhood is now recognized as 30mph. It's a regular 25mph residential street with speed bumps.
The only true improvement on this drive was one unusual left turn that it has failed at a basically 100% rate; today it was smooth and the car pointed onto the correct street instead of aiming at either oncoming traffic or parked cars.
EVNow
Well-Known Member
EVNow
Well-Known Member
Those are what they found in simulation / testing. Any particular real word experience may be different. Usually some May see progressm some no difference and some regression. You just hope the former group is larger.
That is why you need to test in realworld.
10.8.1 which itself was not great in some ways, most of which were the excessive false cone detections
jabloomf1230
Minister of Silly Walks
I've only done a few drives with 10.10.2 but I haven't noticed anything significantly different from 10.8.1. Maybe this update just completes the NHTSA's recall demands. Has anyone heard the elusive seatbelt warning chime?
EVNow
Well-Known Member
10.8.1 had a few regressions for me which continued in 10.9. Will have to see what happens with 10.10.
I drove what has become my FSD torture test drive on 10.10.2 last night.
Seems like it has kept most of the bad things from 10.8.1 sadly
Approaching a T junction stop sign where the main road is curved. FSD ignores approaching cars from left and tries to turn right in front of them.
Next T junction where we have right of way, no yield, just a right turn. FSD still comes to a full and complete stop and edges forward before make an extremely slow turn. I usually take this corner at 20mph.
Next is the left turn at the 4way where we have right of way (no road signs). FSD comes to a complete stop again before trying to turn left into someones garden, then overcorrects and cuts the entire oncoming lane to get to the correct lane.
Then another left turn T with full right of way, another full stop and stupidly hesitant turn with lots of stops and wheel spinning.
All that in the space of 400 yards. Every single one completely useless.
On the drive back is was even worse. Literally zig zagging around the corner with wild steering wheel spinning.
I think this version is even worse than 10.8.1 on unmarked roads, driving right down the center and ignoring oncoming traffic.
I let it get to a left turn T junction, as soon as it spotted the road markings for the junction it freaked out an flashed the red steering wheel "Take over immediately".
That little 5 mile drive was 8-10 snapshot disengagements in each direction.
Hopefully will try other drives today, but not feeling good about 10.10.2 right now.
Seems like it has kept most of the bad things from 10.8.1 sadly
Approaching a T junction stop sign where the main road is curved. FSD ignores approaching cars from left and tries to turn right in front of them.
Next T junction where we have right of way, no yield, just a right turn. FSD still comes to a full and complete stop and edges forward before make an extremely slow turn. I usually take this corner at 20mph.
Next is the left turn at the 4way where we have right of way (no road signs). FSD comes to a complete stop again before trying to turn left into someones garden, then overcorrects and cuts the entire oncoming lane to get to the correct lane.
Then another left turn T with full right of way, another full stop and stupidly hesitant turn with lots of stops and wheel spinning.
All that in the space of 400 yards. Every single one completely useless.
On the drive back is was even worse. Literally zig zagging around the corner with wild steering wheel spinning.
I think this version is even worse than 10.8.1 on unmarked roads, driving right down the center and ignoring oncoming traffic.
I let it get to a left turn T junction, as soon as it spotted the road markings for the junction it freaked out an flashed the red steering wheel "Take over immediately".
That little 5 mile drive was 8-10 snapshot disengagements in each direction.
Hopefully will try other drives today, but not feeling good about 10.10.2 right now.
This is what I don’t get. Am I misunderstanding something? It is my “assumption” (I know, I know
) that there are supposed to be improvements albeit small iterations each time on all these areas. Or even SOME of these areas. Why is it that there are so many regressions in most if not ALL these areas with each update. It seems like there is either no progress or that we are moving backwards in most areas.Ski
jabloomf1230
Minister of Silly Walks
I've always assumed that local conditions such as weather, lighting, traffic and mapping inconsistencies tend to obscure most of the improvements from one minor version of FSD beta to the next. No matter how much I try to standardize my drives, the behavior of any version of FSD beta is not all that reproducible. Every so often a version contains a specific improvement that is noticeable, though. One example was the switch from friction braking to regen.This is what I don’t get. Am I misunderstanding something? It is my “assumption” (I know, I know
Ski
Freshtry
MX P100D FSD, Del Apr 2017, MS 75D Del Nov 2017
My wife appropriately called it, “…like being at Disney on Mr Toad’s Wild Ride.”
In fairness, no version of FSD has come close on this particular drive. Sadly for me I drive it twice a day taking the kid to schoolThis is what I don’t get. Am I misunderstanding something? It is my “assumption” (I know, I know
Ski
More encouragingly, I tried another route that 10.8.1 wasn't too bad with, with 10.10.2 it did extremely well indeed.
It managed the whole drive home through many intersections, traffic lights, stupid driver etc and did very well.
I didn't need to use the go pedal to force it move etc or disengage.
The only issue was when it continued accelerating much to late approaching a red light, which mean it has to stop too quickly - if that was me driving it would have qualified me for "aggressive braking" from the the not-safety score.
One niggle was hitting a 40mph coming from a 50mph - it took too long to slow down, which was something the previous versions did a lot.
The flip side was when we we turning right at a light, 10 feet from the light and it went yellow. FSD didn't stop for it and made a perfect turn.
Overall, that drive was much better that the best of the 10.8.1 drives and very confidence inspiring.
EVNow
Well-Known Member
These point to map problems.
In general I think we can say - very hesitant driving points to
- Visual & Map not matching
- Very odd geometry (i.e. more like edge cases)
Pulling out in front of vehicles on curved roads leading into T intersections might not so much be a mapping problem, I think the system has trouble interpreting things on curved roads in general when compared to more perpendicular movements i.e. how the vehicle brakes when vehicles approach in the oncoming lane on curved 2-lane roads.
Trajectory in a curve is probably much more difficult to extrapolate with a high degree of confidence
Trajectory in a curve is probably much more difficult to extrapolate with a high degree of confidence
EVNow
Well-Known Member
True - kind of “edge case” to have T-junction at a curvature.
BTW, FSD/AP rarely brakes on curved roads for traffic coming in opposite direction - otherwise I’d not be using it in Seattle area for 3 years !
Similar threads
