Maybe? Honestly, I try not to judge based on my perception through the camera because angles can be deceptive. The woman didn’t seem very freaked and neither was Frenchie, and their view is much better than ours.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Hopefully Tesla iterates quick;y on the “pixel height” estimation that Elon mentioned, cause it’s clearly very iffy right now. Frenchie has the car driving towards road closed signs, and oisiaa has his car completely ignore fencing on a ”road” that the GPS shouldn’t have routed him on at all. I really appreciate how much respect this guy has towards his responsibility to monitoring the system and making sure it doesn’t impact other drivers on the road.
Frenchie didn't acknowledge it but I think he seemed a bit flustered afterwards, pretty sure he knew it was a bad move and that he likely should have disengaged. We've also seen his FSD try to merge into a car that was visible in a drivers-side B pillar camera he had mounted for a video and then say that there was "plenty of gap" and sloughing off the person honking as what you'd expect from bad/impatient drivers in Chicago
Someone mentioned the close call in the video comments but he hasn't responded to it yet
Chazman92
Member
#FSDBeta LOTS of Forward Facing Unprotected Left Turns
favo
P3D+ owner
Yeah, I've been thinking that if I were a beta-tester, I'd want it to say the words "creeping" vs. "proceeding" or some such, because you cannot be looking at the screen during those risky maneuvers. People have trouble remembering too many different chimes. (How about "errr?" and "weee!"?
)It seems to take 3 to 4 seconds to clear the intersection, even if it had to stop. All of the gaps were greater than that, but some of them were only 5 seconds which seems a little close. I think it would have made it, just too close for comfort.
favo
P3D+ owner
I assume/hope that also includes pixel depth (i.e., distance from camera). If they can get that to work reliably (99.999%), it should really help avoid running into unknown/unclassified objects. Obviously, this is rule #1 of driving: Don't hit anything. Elon mentioned they need a reasonable way to render unknown objects. I'm thinking just showing red pixels would be OK. If they can turn that into a bounding box, I suppose that would work.
2:40 and 7:40 - those were gaps I would have gone for. But FSD isn’t always aggressive so I don’t blame Chuck for stopping it.
9:15 - If there were a lot more cars behind the oncoming car, I might have gone for that gap by gunning it as the car before it was passing, but in that situation where it was pretty wide open afterwards, I definitely would have waited.
Still don’t like how the Tesla pre-angles itself for turns though. That potentially freaks out both the Tesla driver and oncoming drivers. If the car Stays straight, no one would be worried about it creeping into traffic. Obviously not an easy problem to solve given how long it’s been an issue (I assume trying to do so would break some other bit of turn logic, trying to fix bugs can sometimes be an unending cascade of unintended consequences), but I hope Tesla eventually cracks it. It would make those lefts a lot more comfortable for everyone involved.
stopcrazypp
Well-Known Member
I covered a bit here how the creeping improves visibility for the cameras, so I don't think Tesla will change that behavior.
FSD Beta Videos (and questions for FSD Beta drivers)
It takes about 3 seconds to make the left turn, and 2:40 was about 120m away = 5 seconds while 7:40 was about 100m away = 4 seconds. And the former had traffic coming in the closest lane, so the Tesla would probably be 2 lanes away, but the latter traffic was in the middle lane, so that might have resulted in some braking.
There were actually at least 2 potential opportunities that FSD Beta 10.0.1 might have attempted the left turn during the 7:20 pass:
Here it correctly detected and visualized the further vehicle in the closest lane at about 90m away. However, a few seconds later, a vehicle just within 80m still wasn't visualized resulting in the disengagement:
I wonder if Vision-only production highway velocity/position training hasn't quite made it to FSD Beta 10.0.x city streets neural networks, but maybe that will be addressed as part of the single stack where presumably "city streets" network will also be trained on highway data to be more consistent on moving vehicles that are further away.
powertoold
Active Member
‘Probably because of the camera position. Front cams weren’t pointed at the distant car, only the wide angle and some of the bpillar .
Daniel in SD
(supervised)
This is silly. I can tell it's a lifted Toyota pickup at 80m looking at a screenshot of a YouTube video. There's no way the front cameras are that crappy.
Says Tesla doesn't want them to share all of the videos.
He says he regrets not removing the part where it was headed for a pedestrian from the video.
Says he will be on "good behavior from now on" and be "selective on what he posts"
The twitter clip had 5 million views before being DMCA, I wonder if Tesla contacted him to delete his monorail video.
He says he regrets not removing the part where it was headed for a pedestrian from the video.
Says he will be on "good behavior from now on" and be "selective on what he posts"
The twitter clip had 5 million views before being DMCA, I wonder if Tesla contacted him to delete his monorail video.
Daniel in SD
(supervised)
"Tesla doesn't want a sharing all the clips of the video, just, like, when it looks good" haha.
In Tesla's defense what they probably don't want is people driving like jackasses on public roads while using FSD whether it's posted to YouTube or not.
DMCA takedown is total BS imho. Seems like fair use to me.
Anyone else suspect this wasn't actually a hit and run?
stopcrazypp
Well-Known Member
He was in mid-sentence saying "Tesla lets us share everything on social" then he got cut off as the car was cutting into a lane that was not actually a lane (I guess this is why these shouldn't be streams, but commentary should be narrated separately), then he says "Tesla doesn't want us sharing all of the clips of the videos, um just like when it looks good because they know people take it out of context". So it's a bit self contradictory. And we have seen all sorts of videos where the system does badly, so not really sure what he really means by that. Maybe Tesla doesn't want individual clips, but is ok if you share the whole trip.
As for the take down request, it was initiated by him, not Tesla (as I mentioned in some comments in an article of this). He first asked the person to take it down just due to them violating copyright and not even giving link or a credit, and when the person refused, he contacted Twitter and Twitter took it down (that's why the strike had Twitter on it).
Last edited:
I think you have that backwards.
Wide angle cameras make things look further away than they are. Therefore the lady is closer than she appears to be, and the gap is narrower than it appears to be.
stopcrazypp
Well-Known Member
Just stealing a clip with no credit or link to the original author is not fair use. It's like a lot of clippers that earn revenue just by stealing content by clipping other videos, but usually even they link back to the original author or they do something to make it "transformative" by editing in some way (or maybe adding translations, but even translations don't give you a free pass), not just post a single clip outright.
From Canon’s website:
Attachments
powertoold
Active Member
I also showed an example screenshot of the green container (looking really close to Frenchie's car), which was right next to the pedestrian girl.
Similar threads
