Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

Wiki MASTER THREAD: Actual FSD Beta downloads and experiences

This site may earn commission on affiliate links.
As I said earlier - never is a long time. Fairly sure it will drive better than many Uber drivers in our lifetime.
I think it will get a lot better when they attach some memory/persistence to the models like Elon recently mentioned. Right now it jitters around a lot because all the model predictions are based on instantaneous video frames, and it doesn't accumulate over time and converge to a stable output. If the vehicle sees a curb or lane marker on the other side of the intersection it ceases to exist the instant it gets occluded by traffic. It's kind of amazing that it's able to drive at all on these jittery models.
 
anyone else experienced an issue with gradually reducing speed limits - where the car correctly spots the speed limit changes 75-70-55 for instance - but doesn't actually slow down. This has had me doing 75 in a 55 several times.
It reduces the set speed but maintains its current traveling speed, only slowing down if its blocked by a car in front.

Also, the auto high beam setting that is re-enabled each time it flips from old stack AP (speed limits above 65) and new stack AP (speed limits below 65)
Yes. Multiple times today.
 
I had this not so edge case happen to me today. What should it do for a wife load coming from the opposite direction? I passed the escort car and then disengaged FSD as I could see the load was in my lane (2 lane highway). As we were both moving at 60mph in opposite directions I did want to wait to see what it would do.

It has to be able to move over well in advance of the oncoming wide load.
 
I have a couple of hundred miles on 10.4 so far and have some observations to expand on from my initial assessment. I understand that just because FSD has a success in one location or edge case, it will not always succeed. Still, watching the NN and understanding its capabilities is amazing. It also tried to drive into a truck at 20 mph on a pretty easy section of road, scaring both of us pretty good. It also ran a red light when turning right on red badly enough I cut someone off significantly.

My 40 mile commute so far usually has less than 12 times I need to intervene to accelerate, brake or change the path of the car. I do drive during hours that the traffic is less, but still is bay area traffic. It consists of a one-lane unmarked road for 2 miles, city streets for about 5 miles, Highway 17 for 20 miles, and freeway 85 for about 10 miles.

Things I love not included with my previous list:
FSD avoided a lane-splitting motorcycle, by getting over to the left in the lane.
FSD avoided debris in the road from a landslide. It may have rendered a grey line inside the normal red lines.
On high-speed curves over highway 17, FSD will account for bump steer, and compensate ahead of time. AP before had sickening side to side motion over bumps in curves, especially with my MPP Sport coilovers.
In general, FSD takes high speed corners over 17 at a more appropriate speed. I have learned to be patient and allow it to go 45 mph at times in the slow lane around tight curves. The real test will be when I come around the corner at speed, and a landslide, or disabled car is in the lane in front of me. Those tests are few and far between, and it takes titanium huevos to let the car figure out such situations. Going around the corners at a speed slow enough to catch such a danger is appropriate at this point.

Things I hate
FSD keeps changing my choice of recommended speed. Also when switching stacks I have to spend energy remembering how the car will act and need input in each case. Specifically that the speed limit is reset by FSD or switching stacks so many times, my input seems like it's not trusted. If you trust me with Beta trust me with the speed control when switching stacks.
The slowdown -speedup -slowdown pattern gets pretty old. I had a co-worker who drove just like this every day, and it's frustrating but humanlike lol. It seems better in 10.4
One time on my home road, the car did not recognize a dog however, 2 other times it has recognized and rendered a small animal of some kind. Room for improvement here. Luckily there are tons of dog walkers on my road, so it's a good test case.
Accelerating toward a driveway, without regard for suspension compression or the damage that might do. Entering driveways should always be done with some speed sensitivity.
Sometimes the car doesn't know when it's appropriate to stop. If FSD stops too early, and traffic is turning right with FSD behind 1 or 2 cars, it sometimes gets confused by those cars turning right on red, thinking it's safe to just jump out there and turn as well. This is maybe related is the problem of stopping in the wrong place, often too early for stop signs that are in a difficult to recognize place.
Waits way too long to use the turn signal for other traffic to recognize FSD intent. When merging, or turning right FSD is often at the very last minute using the blinker.
FSD Positions itself in the wrong place in the lane when turning. It is often 2-3 feet to the left for a right turn and vice versa. It's great for towing a trailer I guess. More trailer testing is needed.

Things that seem better in 10.4
Lane-keeping for unmarked one lane roads seems to keep the car closer to the correct side, while still allowing some driving in the middle.
General confidence in decisions, when it's feeling confident.
Less of the uneven speed keeping, less slowdowns for no reason.
 
I had this not so edge case happen to me today. What should it do for a wife load coming from the opposite direction? I passed the escort car and then disengaged FSD as I could see the load was in my lane (2 lane highway). As we were both moving at 60mph in opposite directions I did want to wait to see what it would do.

It has to be able to move over well in advance of the oncoming wide load.
Okay was it the WIFE or the ESCORT that did this. I say leave the wife.
 
I can confirm FSD Beta 10.4 slowed down to 18mph for (white chevron) speed humps and 6mph for (yellow) speed bumps while also visualizing them. I found this "challenge mode" ;) test for FSD Beta:
View attachment 730757
Both speed bumps + crosswalk in between + stop sign visualized. Just missing the 15mph sign although map data did already know it should be 15mph.

View attachment 730760View attachment 730761

Speed hump with horizontal lines before and chevron on top seem to get detected fine. Although I did get this false positive where the sidewalk was detected as a speed bump.
I’m getting speed bump visuals but still no slowdown.
 
  • Informative
Reactions: FSDtester#1
I think it will get a lot better when they attach some memory/persistence to the models like Elon recently mentioned. Right now it jitters around a lot because all the model predictions are based on instantaneous video frames, and it doesn't accumulate over time and converge to a stable output. If the vehicle sees a curb or lane marker on the other side of the intersection it ceases to exist the instant it gets occluded by traffic. It's kind of amazing that it's able to drive at all on these jittery models.
I may be confusing FSD Beta release notes with Karpathy presentations about unreleased capabilities, but I thought they had already added some of this temporal context? Specifically they talked about the model continuing to persist occluded objects, and some kind of short term 'memory' for road markings seen earlier. That may have all been forward looking stuff.....
 
  • Like
Reactions: Battpower and eli_