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

FSD Beta Videos (and questions for FSD Beta drivers)

This site may earn commission on affiliate links.
Looks like FSD beta doesn't have a good sense of urgency for lane changes as here it ended up slowing down to 16mph instead of speeding up to 40mph set speed to pass this vehicle turning into a driveway. Both the path and lead vehicle predictions could have been smarter in going around for a slightly later lane change once it detected the adjacent vehicle slowing down. The upcoming right turn in navigation was still 0.3 miles away.

View attachment 634795
I am not going to agree or disagree on your assessment since I didn't watch the video. I do think it should be apparent to everyone that FSD will not drive like you or I in some situations so we have to be careful to assume it will. I've noticed Waymo also drives differently then I would. Not bad just different and FSD will be the same once it's reaches parity. (hopefully!). Just waiting for the release of the next beta version before watching any new videos. Come on Tesla!!
 
4:18 - car looks like it’s about to run a red light, forcing Chuck to take over and swerve into the empty right turn.
It looks like FSD beta intentionally ran the red light believing it had already crossed the stop line and entered the intersection, so it was continuing through as if it entered on green, which was actually for the right lane but incorrectly associated to this lane.

stop line.jpg

Notice how the predicted path blue line turns gray too early for a line that's for the school sign, so after FSD beta realizing it's going too fast to stop for this "stop line," it decides to get out of the intersection not realizing it's still before the actual stop line.
 
  • Helpful
Reactions: mhan00
Here is a classic example that needs work BUT can FSD ever react with the passion and understanding a human can? As we have seen FSD needs to start slowing sooner for pedestrians to instill confidence. Barreling towards them and then hard braking may not hit them but it is confusing to pedestrians. Probably an easy fix.

BUT back to this specific situation that is simple to humans. There is a HUGE difference to what we see compared to what FDS sees. Elderly man ahead of wife and committed to crossing and concerned about the speed of car. Woman wanting to cross and CLEALY giving the "are you going to stop and let me cross?" look that we humans understand. However the car only sees a green box that it should not hit but no concern for how close it is and a yellow box that has no relation and has NO empathy for.

In all likelihood FSD would have slowed just enough "bullying" the man to "hurriedly" clear the curb by a few feet and then would have continued forward "cutting" the woman off. To the people it would have been an a$$ hole move and Chuck (you and I) would have felt guilty but FSD would not "care".


Screen Shot 2021-02-08 at 6.38.25 AM.png
 
#FSDBeta 8.1 - 2020.48.35.7 - 4K Drive to Willowbranch Library with Commentary
We almost got some grass cutting action here! o_O

cut grass.jpg

This Park St connection is a bit odd as reflected in the navigation thinking the upcoming action is a left turn 1.4 miles away -- i.e., navigation believes you just need to stay on the current street without needing a right turn. At least on OSM, there's an unnamed "tertiary_link" that connects these two segments of Park St where the intersection of the named Park St segments is where the no-right-turn sign is.
 
It looks like FSD beta intentionally ran the red light believing it had already crossed the stop line and entered the intersection, so it was continuing through as if it entered on green, which was actually for the right lane but incorrectly associated to this lane.

View attachment 634953
Notice how the predicted path blue line turns gray too early for a line that's for the school sign, so after FSD beta realizing it's going too fast to stop for this "stop line," it decides to get out of the intersection not realizing it's still before the actual stop line.
@Chazman92 in today's video, you said the car got confused yesterday wanting to stay straight on Herschel instead of turning right on to St Johns. As shown in the screenshot, navigation knew it wanted to stay on Herschel, so that's why it didn't attempt to get into the right lane as it knew it didn't want to be in a right-turn-only lane. But it did get confused by by either one or both of the green right/up arrow as well as the line drawn for the school sign, so you did end up correctly recovering from the car wanting to drive straight through a red light. I believe previous videos, navigation did want to turn on St Johns, so not sure why this time it wanted to navigate straight.
 
We almost got some grass cutting action here! o_O
This Park St connection is a bit odd as reflected in the navigation thinking the upcoming action is a left turn 1.4 miles away -- i.e., navigation believes you just need to stay on the current street without needing a right turn. At least on OSM, there's an unnamed "tertiary_link" that connects these two segments of Park St where the intersection of the named Park St segments is where the no-right-turn sign is.

One of the segments of Park Street ( Way: ‪Park Street‬ (‪682970835‬) | OpenStreetMap ) was tagged one-way in the wrong direction. Not sure if that was related to the odd navigation choice, but I just set the direction correctly.
 
Not sure if FSD beta was being overly cautious or this is how people should react when going through this curved intersection without guiding stripes:

View attachment 635673
Here the car slowed down to 24mph instead of up to 45mph because it wasn't sure if the adjacent vehicle would stay in its lane.

Personally, I think that's defensive driving behavior because the adjacent vehicles also slowed down. FSD beta kept a consistent distance behind the Volvo adjacent to it.
 
  • Helpful
Reactions: mikes_fsd