GlmnAlyAirCar
Active Member
Why would you signal when two lanes merge into one? There is no ambiguity there.
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.
Why would you signal when two lanes merge into one? There is no ambiguity there.
Ran past this intersection a couple times today and 10.12.2 seems to handle it without stopping short. So definitely possible it did react to the car... will have to see once I get 10.69.x on mineIt is my experience that the FSD beta can routinely stop short on random uphill/downhill sections in this area. Sometimes it will pull up correctly, sometimes it will stop short and pull up before proceeding as normal. Might go try this same intersection on 10.12.2 out of curiosity...
Why would you signal when two lanes merge into one? There is no ambiguity there.
Ouch! So much for Elon wanting open and honest discussion on Twitter!Elon laying down the law (or at minimum his strong opinion).
View attachment 844214
Why would you signal when two lanes merge into one? There is no ambiguity there.
When your lane is the one merging, you should signal out of courtesy, and FSD should aspire to be "better than average human", right?For merges in which the sign indicates that a lane ends, anybody in the lane that is ending is changing lanes, so should either signal or yield to the traffic in the other lane with right of way.
But even in an alternate merge, there are decisions to make, so it can be helpful to make it clear to the person behind that you're ready to take the merged lane and they shouldn't try to overtake.
I don't get why the geometry and acceleration needed to do Chuck's turn wasn't nailed down in simulation. It's clear that the car had more problems than just live traffic & intersection perception in pre-10.69 versions. It stuttered left & right, hesitated, drove slowly across oncoming traffic. Don't they simulate and solve?Tesla/Elon focusing on Chuck's ULT was a great move from their perspective purely because of the focus on that turn and the reception now received, this is really top tier marketing. Throw in a price increase on the back of the release to YouTube reviewers and a tweetstorm and man, it doesn't get any better. I'm honestly in awe at the effectiveness.
My pessimistic self says this should be worrying because Tesla needed to secretly send a team to this turn after Chuck has been grinding away at it for over a year. And Tesla very clearly does not want people to know it's happening, in no small part because I think it pokes holes in the idea that mass public testing is even required in the first place. Chuck was doing that, pressing the camera button endlessly as we all watched, and now it's magically solved after we know Tesla had a team there.
The mystery and lack of understanding around this technology plays heavily in Tesla's favor
I see you got laughed at for saying this, but I think it's right and I posted a very similar opinion up thread.Not an attempt to move goalposts, but when Elon says "we going to solve Chuck's turn 100%" the statement might not mean they're going to solve it 100% of the time, just that they're going to solve it some percent of the time, 100% guaranteed. The nature of neural networks makes "100%" a near-impossibility, just like human brains will never drive perfectly 100% of the time.
Virtually all issues that FSD has today existed in Oct 2020. Tesla will work them when and if they decide to work them. You don't necessarily work all the simple ones first.I wonder if Elon Musk knows that James Locke has been sending back video snapshots of FSD Beta not signaling for 2 lanes merging into 1 as recently as March 2022 but also going back now literally years to December 2020 (and probably October 2020). I would not be surprised if Tesla has over 1TB of video snapshots (with actual ongoing costs to Tesla) from his vehicle just for this one priority problem of his to use the turn signal.
Hopefully this doesn't mean 10.69.1/.2 will be delayed for the rest of us.
Simulation is not a substitute for the real thing. It's a tool that (hopefully) reduces the amount of real world testing.I don't get why the geometry and acceleration needed to do Chuck's turn wasn't nailed down in simulation. It's clear that the car had more problems than just live traffic & intersection perception in pre-10.69 versions. It stuttered left & right, hesitated, drove slowly across oncoming traffic. Don't they simulate and solve?
Huh? How was Tesla trying to hide their activities? Did I miss where they asked/requested that Chuck not share that he saw Tesla testing his turn?My pessimistic self says this should be worrying because Tesla needed to secretly send a team to this turn after Chuck has been grinding away at it for over a year. And Tesla very clearly does not want people to know it's happening,
Simulation is also needed and will be more important as the march of 9's increases. Need to simulate the unlikely events that don't occur irl much.Simulation is not a substitute for the real thing. It's a tool that (hopefully) reduces the amount of real world testing.
Well they have touted the quality of their simulation environment. I would expect that upon arriving at Chuck's turn, a well-prepared software version would just have to map the intersection, look at the traffic and have a pretty good idea how to proceed. I would say it didn't appear to be well-prepared at all, so why wasn't simulation done beforehand. Or why wasn't it very effective? Seemingly anyway.Simulation is not a substitute for the real thing. It's a tool that (hopefully) reduces the amount of real world testing.
Maybe I'm moreso just thinking about Chuck trying to respect their privacy, although he tweeted that they were clearly given a "when confronted by Chuck" coaching in terms of what they can say.Huh? How was Tesla trying to hide their activities? Did I miss where they asked/requested that Chuck not share that he saw Tesla testing his turn?
But seems like you would work the broad spectrum problems first before working on the more particular issues. For example, I would think there are a lot more people experiencing, for example:Virtually all issues that FSD has today existed in Oct 2020. Tesla will work them when and if they decide to work them. You don't necessarily work all the simple ones first.
If all it took was simulation, then there wouldn't be 100,000 beta testers.Well they have touted the quality of their simulation environment. I would expect that upon arriving at Chuck's turn, a well-prepared software version would just have to map the intersection, look at the traffic and have a pretty good idea how to proceed. I would say it didn't appear to be well-prepared at all, so why wasn't simulation done beforehand. Or why wasn't it very effective? Seemingly anyway.
It’s hugely improved, but not solved, to be clear. And maybe with another couple weeks of tweaking it will work every time; I don’t know. We’ve seen two clear failures so far (one other debatable).and now it's magically solved
George Carlin summed up this syndrome a long time ago:This is one of the things that bothers me here. Calling people idiots and morons for making a mistake as if you and others on here never made a driving mistake. Just one more person to put on ignore.
Yeah well, you & I are missing understanding each other here. I'm saying simulate then test, for some reason I'm getting the sense you feel I'm saying all it takes is simulation. What I'm suggesting is their simulation seems poor if the car can't perform acceptably in live testing, on something that really should already have been ironed out in simulation.If all it took was simulation, then there wouldn't be 100,000 beta testers.