valem
Member
Interesting that you had AP cross a double yellow into oncoming traffic.... because when I'm on AP I can't get it to change lane if there is a solid line, even on the highway.
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.
Ooh look, another term. It's not in "general release yet." Earlier it was "wide release."
Even @Knightshade, the Tesla stock multimillionare, can't decide how to refer to the state of FSD's "release"
You can also follow all of that up with the clear argument that a subscription to FSD is not the same thing as buying FSD for $12K
Hmm, you use the word "freeway" but Tesla uses "highway" in the manual, and you keep arguing that words matter and the traffic code is clear what a freeway is, despite Tesla never once using that term in the manual.It's also the most obvious reason it says it's intended for use on controlled access freeways
Except you know this isn't true. Nobody has any idea if Tesla will release this FSD beta. They have no contractual obligation to. They can charge more for it if they want. They can call anything they want city streets autosteer and ship it and be done.It's working toward a product that WILL eventually be released to the whole fleet, completing the final undelivered feature of the current FSD package. But it is not, currently, that thing.
The function and composition of the car does not change because someone else owns it and rents it to you vs direct ownership. "Your car has all the equipment required to be purchased but not rented" is a crazy statement.Any more than renting a car is the same thing as owning a car.
Explain the multiple threads that constantly pop up with people asking how they can get FSD beta if "everyone understands it" and tell me where on Tesla.com I can point people so they can get the official story?Everyone understands it, you just find it funny to pretend you don't.
Except you know this isn't true. Nobody has any idea if Tesla will release this FSD beta.
Me in clear english you somehow didn't understand said:But it is not, currently, that thing
The function and composition of the car does not change because someone else owns it and rents it to you vs direct ownership.
I used it on any and all roads in the Bay Area. you're infos not really correct.Uh...AP is intended for use on divided, controlled access, freeways.
So no place it's intended to be used has double yellow lines with oncoming traffic.
Again, this is user error-operating AP on a road it's explicitly not intended to be used on per the owners manual.
The fact that years later people still get this basic stuff wrong on using wide-release features is a great example of why they choose to limit early testing of unfinished software to a narrow group though.
What a crazy world when we blame customers for being confused by this. Tesla makes none of this clear, and it's particularly broken given every single AP feature is in beta, so how is FSD different. So yeah, when Tesla keeps calling it "FSD beta" they are at fault for confusing people. Where does Tesla say it's "FSD beta narrow release"? Heck, we had titles like this in October: "Tesla officially starts its ‘wider release’ of Full Self-Driving Beta in the US"
This is the real key everyone needs to know. You are NEVER owed access to it, no matter what you paid, no matter how "wide it goes.". Tesla is not selling access to features seen in "FSD beta". The only thing they are selling you is city streets autosteer, which has no defined functionality. Tesla can charge you $12K, start sending FSD beta to people that never paid for anything, and as long as someday they put "city streets autosteer" on your car, they are done.
You get people here going "don't worry, you'll get it someday when it goes "wider"" but that's not for sure. When they say Tesla is not selling access to the FSD beta "narrow release", what they really mean is that there is absolutely zero timeframe or feature set they have sold to anyone, so who knows what you will get someday. There is no promise that what Tesla releases "wider" has anything to do with what you see on YouTube videos today. These people tend to see this as totally fine and buyer beware and will belittle anyone that could be so dumb as to believe because you paid $12K for a feature titled "Full Self Driving Capability" that what you will get is the software called "Full Self Driving".
That's always the easy answer... driver fault. It's a shortcut. Can't blame the software, the software doesn't post on twitter that the car did this or that.It's also great evidence that Tesla is completely disingenuous and likes the fact that people confuse this, and is not taking safety seriously.
When AP2 first came out in 2017, it WOULD NOT TURN ON when not on an approved road. They have the code to do this. They know what kind of road it is. But then in later 2017, they turned off the automatic limit, and now people like you blame the users and try and use it as evidence about how dumb people are.
Explain why Tesla allows you to turn it on when on "explicitly not intended" roads when they could just block it in code they already have?
I used it on any and all roads in the Bay Area. you're infos not really correct.
The "literally quoting" where you talk about the manual using the term "freeway" 6+ times in this thread despite the fact that the Tesla manual doesn't have the word freeway in it a single time?My info is literally quoting the owners manual of the car.
You gonna answer the question as to WHY Tesla allows use on these roads when they can prevent it with a single line of code and have done so in the past?But it does explain that it's user error in cases where it does not work right on different road types than what is intended.
Anyone else get a delayed ding to their safety score for FCW? Yesterday my safety score was 100 and included all results up to my last drive the same day. Today it dropped to 98 and I never used my car. I looked at the details and saw a FCW on 2/21 that was never there before??
I should note software was updated to 2022.4.5.3 last night (from 2022.4.5.1). I did not check the score after, so it may have caused the ding?
Nope, I have a 30 day rolling spreadsheet where I enter my numbers every day. The number for 2/21 was 100 score and 10 miles. As of 2/28 it was still showing that in the app. My spreadsheet also tells me the future numbers for the next 30 days, so I can see what will happen if I don't drive, etc. Then the day after I updated the car I noticed the score had suddenly dropped to 98. It may have dropped right after the update, however I did not check the score then. I went back and checked all the data and found 2/21 had changed to 75 score and 15 miles. After I updated the number in the spreadsheet it shows the score would have dropped to 99 on that day (i.e. 2/21), and then 98 on 2/24, etc.Since the score is based on the last 30 days it could be that a 100% day rolled off and your more recent day was lower so your score dropped.
Ha. That's why the "safety score" showed up just a few days before they started using it to filter the FSD beta list, and why it doesn't use things like speeding or running red lights to reduce your score, but does focus on if you ignore AP alerts or how close you follow. It's also why supposedly feeding it with tons of miles of data, they keep changing how it works.The reason for Safety Score isn’t to filter FSD Beta. It’s to Beta Test Safety Score
Sure, let’s go with that.It's totally there as a good statistical metric on how likely you are to have an accident and would pass an insurance commissioner review as an unbiased actuarial tool, right?