Alan said no human would poke out,
In this situation it was not needed unless you were going to do the squeeze. It’s not a big deal to move over a bit like the car did, but if you do it because you intend to go (which is why it did), that is not good. An oncoming vehicle will understand. In this case the Tesla crossed onto the double yellow (and possibly even over it), which is too far, and indicates intent. This is not complicated stuff - it's stuff we do every day.
My point was that fsd's planning is improving. It seems to be doing it more in advance and more gracefully than before.
And my point was that I don't really see any evidence of that. It looks like it can plan to avoid taking right of way from an oncoming car, once it is very close.
I don't understand why Tesla didn't put the camera in the upper left corner of the window so it doesn't have to poke out so much more than a human.
Would definitely be nice in some situations but was not needed here. Tesla will just have to stop a bit further back than a human to get the sight lines, I guess.
it actually saw the oncoming car at around 9:07
And then forgot about it (it disappeared at 9:08, about two seconds after the human first saw it at 9:06) and saw it again a couple seconds later! I’m not sure this observation makes things better! Perhaps this is the reason it did not respond until 9:10? Why is it not consistently visualizing approaching vehicles it has already detected? You can see the path planner does not go to faded blue until 9:10, by the way - it was perhaps fully intending to proceed until then (I'm not sure of the significance of the faded blue vs. dark blue pathing).
What is also apparent in this video is the incredibly fast stop (20-25mph in a couple seconds). Another reason to make the correct decision earlier! Why is the car using the brakes??? (You can't see them in the video, but they are definitely there (you can see elsewhere in the video it's hard to see the brake lights in the visualization with this aspect).)
This is another one of those examples of a very abrupt move happening, which is not apparent in the video (because it's a video). Passengers would be upset. The driver was not in this case, because he knew what was going to happen and he was in control.
I've always felt this way about AP/NoA too. The system has gotten better over time (with a few hiccups in between), but it has made so many of my drives less stressful. FSDb will get there. It's not there yet, but I don't think they are far from decent L2 on local roads.
AP is great most of the time; it's wonderful for long drives, and has improved over time - but I would say even in 2018 it was "close", before a bunch of improvements. I'm not as sure about FSDb (and never have been). In some limited application scenarios, it may be fine, but I just am not seeing the wonderful comfort of being chauffeured around an area with a bunch of intersections. Maybe some day, but I actually think it is kind of far from decent L2 on most local roads. Of course, I hope I'm wrong and they can iron out these difficulties and end up with a nice, natural driving vehicle.
This is obviously wrong and just being contrarian for the sake of hating.
I've made it very clear that my comments are not aimed at being "hating." I just want a system that I want to use, and am able to use with passengers. (Even though I think that's a very difficult task, and not the reason I bought FSD (fortunately).)
And I don't like to claim abilities for FSD Beta that it does not have (yet). We have to be realistic and extremely rigorous (looking at timing and calculating g forces) when analyzing these videos.