You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
Whew, scares the s..t out of me just watching it!~. Nice combo though of the drone, in car nav and FPV
It’s creeping out a little further than it used to. Unfortunately, it’s a little too far. It’s also looking like that median use was a one off fluke.
He seems to be always positive.
You haven’t watched enough of his vids then. He’s been pretty scathing about Beta in some vids.He seems to be always positive.
We should make a list of youtubers here that are consistently positive (like WholeMars ...) and people who aren't pushing a particular line.You haven’t watched enough of his vids then. He’s been pretty scathing about Beta in some vids.
Thanks joelliot.works for me on 2021.36.8.8
Not surprised that FSD Beta 10.6 would be confused at a 5-way crested angled intersection (audio warning - scream):
View attachment 741369
Seems like the predicted path initially favors the (illegal) left turn as something confident in what it "sees" than potentially following other vehicles to where it believes is not a road. Although I wonder if it's generally safe to assume there's a road if other lead vehicles are doing so?
I don’t think this is specific to the bike lane. I sometimes see this behavior with dedicated right turn lanes that are not marked as bike lanes.Anyone else waiting for FSD to cross dashed - bicycle lane when making right turns? Second to last turn to my house is a right turn and FSD refuses to cross into the bicycle lane when preparing and making this turn (even after it becomes dashed) which means my car occupies the whole lane until the very last second. Cars behind me don't expect this behavior and it annoys them and seems dangerous. This assumes no bicyclist, of course.
Yes, I see the same thing with intersections in SF that transition from a relatively flat road to a steep decline beginning immediately after the intersection. The car presumably cannot see that the road continues because of the steep drop off but it handles just fine by assuming, as humans do, that the road continues and we are not just driving off of the edge of the planet.We have a large number of intersections in Seattle where the road is simply not visible because of the steep angle. I guess SF is the same.
I still remember when I came here first, I refused to drive down a road I just couldn't see and turned. Felt like driving off a cliffThe car presumably cannot see that the road continues because of the steep drop off but it handles just fine by assuming, as humans do, that the road continues and we are not just driving off of the edge of the planet.
Thanks joelliot.
When I select "Security" on the app, I get a "Sentry Mode" selection that I can slide the slider to the right. When I do that the red circle lights up to the left of the "Sentry Mode" selection. But, then when I try to then select the "Sentry Mode" option, nothing happens. I thought that by selecting the "Sentry Mode", it would take me to a page showing me the live views (4 of them). Am I not doing this correctly? And, I tried this while my car is parked/locked at a store (ie - not in my garage).
Yeah, here's a couple examples of reasonable path predictions for standard 4-way intersections except facing uphill where neural networks are probably inferring based on the presence of traffic lights/signs, building spacing and other cues:I guess SF is the same