-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Elon: FSD Beta tweets
- Thread starter Terminator857
- Start date
n.one.one
Info w/o Drama
Now we have a tablespoonful of new info.
That hasn't been my experience.
- Maybe one in five turns is jerky to the point where I take control.
- It suddenly changes lanes in the "don't change lanes" area by traffic lights.
- It thinks light rail traffic lights are for cars.
- It ignores traffic lights and stop signs randomly.
- It weaves back and forth between garbage cans, aiming right for the next can before suddenly dodging back out at the last possible second, rather than staying to the left as it should.
- It ignores speed bumps 80% of the time.
- It willfully obeys truck speed limits on highways.
- It goes over both edge lines on highways without a signal.
- When it isn't doing stupid things, it is so skittish that I have to intervene with the accelerator constantly to avoid getting honked at.
Both?
Actually, I started watching one of those videos, and within the first fifteen seconds, I saw two mistakes that I would have disengaged for:
- It got uncomfortably close to a car parked on the side of the road.
- After passing that parked car, with another parked car maybe 30 feet ahead, it weaved over to the edge of the road and back out again unnecessarily (with zero cars coming towards it).
I take that back. Watched it again. There was a car coming. The car just parked before it passed. But it started steering back out in front of the car, so still wrong.
EVNow
Well-Known Member
You guys are completely confused.
zero-disengagement <> perfect drive.
Heck, half the humans should be disengaged, the way they drive.
Given that the top causes of accidents are distracted driving, speeding and drunk driving, it's easy to see how FSDb, which does none of these, easily makes cars safer than the average motorist, despite it's many flaws. Since I've been testing FSDb, I've become very much aware of how poorly most people drive.
Knightshade
Well-Known Member
I don't keep stats on jerky turns... they do happen once in a while, but in light/no traffic situations I've never had a reason to take control back--- I do occasionally when it's being jerking say, making a left and there IS another car in the cross-traffic lane as I don't want to freak him out-- it's rare but non zero.
You mean like where the dotted lines go to solid single white? Here at least it's not illegal to change lanes across those.
I did see it do this REALLY early in the beta-- then it'd occasionally "display" them as such but not react to em... haven't had it even do that in quite some time now though.... (disclaimer- this is regular train crossing lights-- we don't have light rail so could be different)
Never had it entirely ignore one-- I've had it stop too short of one (signs mainly not lights- then take forever to creep up enough). And once had it ignore one it wouldn't have seen until going around a sharp corner which was absolutely "wrong" but more an edge case.... ones straight ahead have been reliable for a long while for me.
I'm having trouble picturing this, are cans being left so far from curbs there's drivable space between them and the curb?
This has been VERY hit and miss across versions... for a while it recognized them very reliably-- it has NOT done so in recent versions though.
This one is weird- I've never, in all the time I've had it, seen it recognize ANY non-standard speed limit sign....including ones that actually applied (school zone/time ones for example)
Not even basic AP back in 2018 has ever done that for me.
That's the "in light or no traffic" thing I talk about.
Specifically at stop signs- if there's no traffic it's fine. If there is- esp. when it stops too short and has to slow creep before turning right or something- I have to step in if there's anybody behind me. Otherwise I just let it to its thing.
I mean- a few of the things you list I don't experience but I think they'd be a reasonable concern to anyone to whom they happened (ignoring red lights for example)... the single white might be too high a standard since as I said here anyway that's a legal move.
DanCar
Active Member
This will not happen for another 3 years at the minimum. Where is that roadster?
KArnold
Active Member
<sigh> Another aspirational, no meaning statement? After that, cars will fly!
I really think he's talking to himself. The greatest show on earth!
I really think he's talking to himself. The greatest show on earth!
DanCar
Active Member
Sometimes it seems I disengage every half mile in the city. Not for safety issues though:
- Don't like lane choice
- I want to drive slower/smoother
- I want to drive aggressively
- Don't like the windshield wipers on
- etc...
AlanSubie4Life
Efficiency Obsessed Member
Think about the math here. An FSDb that makes absolutely none of these mistakes might well be FAR more dangerous than the average driver.
(Hypothetically, you might fix the 5% problem completely and make the 95% more than 20x worse. I would say that seems very conceivable with current performance - FSDb has definitely run (attempted to) red lights way more than 20x more often than I do, for example.)
Last edited:
OxBrew
Active Member
There's a sweeping right corner a block from my house where on basic AP the car crosses the double yellow line every time. Sometimes only 6 inches, sometimes 3 feet. It's never not crossed there. It's a well painted line.
It's one of 2 tests I do with every release, just for fun. The other is a block earlier where it can't navigate a fork in the road. Unless there's a lead car, it weaves a bit, then hands off to me while heading straight at the big tree at the point of the fork, yelling to take over, and sounding the collision warning.
Knightshade
Well-Known Member
Well, basic AP isn't intended to handle things like forks (esp on local roads), so that one doesn't surprise me.... the 3 feet over the lane line does though- have any video perchance?
OxBrew
Active Member
Not yet, but I can make one in the next few days.
Yes, this is AP on surface streets, I know it's not supposed to be used this way, and I don't, except as a test.
VanFriscia
Member
FSD does this for me too around a certain tight, blind curve in my daily commute. It's MUCH better now than it used to be, but it still goes over the line a bit more often than not.
This does to me too, but only when there's no cars coming from the other side. Otherwise, it stays quite safe within my lane on the latest version...
I'm curious how many people have "Disengagements" that result in a "strike" against you? Today my car, with my hands on the yoke, disengaged and gave me a warning that I now had a strike (one of five allowed) before my FSD would be removed. So, out of curiosity, how does Tesla mean to compensate me for my $10,000 if they end up taking away my FSD when this was never in my contract or Owners Manual when I purchased the car in 2021. This was something that has just started recently. So I agree that they have the right to "disable" FSD for the remainder of the drive, or whatever small "punishment" they want to incur upon me, but according to a lawyer friend of mine, if I paid for something and they "take it away" then they must apply "recompense" since I never contractually agreed to this. So again, I'm curious how many people are having their FSDb "taken away" and then not being compensated for their purchase?
Your friend that's a lawyer doesn't seem to understand what they are talking about.
1. FSD Beta wasn't paid for, there's no cost for it specifically and it's not for sale. It's an early access program to help develop the software. The strikes are for liability reasons to ensure people are paying attention. When you lose FSD Beta, you still have FSD...or what you paid for. Regardless of any qualms with that statement, it's the way Tesla has structured this.
2. It's only removed for 2 weeks. It used to be an extremely long time.
3. Don't get strikes...I'd say most testers have gone years without a single strike. Yes, there are some that have faulty cameras that have resulted in strikes, but most strikes are due to not following the proper protocol.
4. Strikes have been a part of Beta since the Safety Score testers were admitted in Oct of 2021.
In summary, you wouldn't get refunded anything for a 2 week suspension to a Beta program.
1. FSD Beta wasn't paid for, there's no cost for it specifically and it's not for sale. It's an early access program to help develop the software. The strikes are for liability reasons to ensure people are paying attention. When you lose FSD Beta, you still have FSD...or what you paid for. Regardless of any qualms with that statement, it's the way Tesla has structured this.
2. It's only removed for 2 weeks. It used to be an extremely long time.
3. Don't get strikes...I'd say most testers have gone years without a single strike. Yes, there are some that have faulty cameras that have resulted in strikes, but most strikes are due to not following the proper protocol.
4. Strikes have been a part of Beta since the Safety Score testers were admitted in Oct of 2021.
In summary, you wouldn't get refunded anything for a 2 week suspension to a Beta program.
EVNow
Well-Known Member
Atleast an acknowledgement that it is not "super smooth" now.
Once FSD is super smooth (not just safe), we will roll out a free month trial for all cars in North America.
Similar threads
