CharleyBC
Active Member
Pretty sure I have, but I can't swear to it. We're heading off on a road trip soon. That'll give us 100 for sure.Drive 100 miles on AP.
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.
Pretty sure I have, but I can't swear to it. We're heading off on a road trip soon. That'll give us 100 for sure.Drive 100 miles on AP.
Is the safety score visible in the app? If so, it would tell you how many AP miles you have driven.Pretty sure I have, but I can't swear to it. We're heading off on a road trip soon. That'll give us 100 for sure.
Oooo! It is. I think that disappeared last year after I first qualified. Though I'm failing to find AP miles. Anyway, I'll soon surpass 100 miles if I haven't already since the repair.Is the safety score visible in the app? If so, it would tell you how many AP miles you have driven.
Got in in May with a 92. Rumor has it that it'll open to people with 80's in the near future, but who knows?Oooo! It is. I think that disappeared last year after I first qualified. Though I'm failing to find AP miles. Anyway, I'll soon surpass 100 miles if I haven't already since the repair.
I see I got dinged hard for a forward collision alert yesterday that wasn't even my fault. I was in my lane, and a bike was in the bike lane. The cyclist was deliberately sweeping back and forth in this ongoing series of S curves, just for fun, I guess. He was staying wholly in the bike lane. But the car freaked, probably extrapolating one of his leftward sweeps as coming in front of the car. Oh, the injustice of a false conviction!
So if I in fact have to requalify, what is the current minimum safety score?
Tap the little information i in the upper right corner.Though I'm failing to find AP miles.
“Shortly”…. Is that like “probably” and “two weeks”?He said "shortly after AI Day," not "the day after AI Day."
I thought this too when I watched a video about it but........it is about the SAME as driving an unmarked road except MUCH safer. On unmarked roads you have VRU's on both sides roads, often occluded and must navigate. On a road with advisory bike lanes you aren't required to drive in the middle (stripped and NOT solid) and can move to the side but MUST yield to VRU's. The lines are just there as a visual cue that guides you away from the MUCH more dangers sides of the road which are highly likely to have VRUs. So while at first it looks like a stupid or counterintuitive idea, in actuality all unmarked roads would be much safer if they were painted this way. It is totally impractical to just widen all residual type roads to make them safe for VRUs and have 2 lanes of detected car travel.People complain about how FSD handles unmarked roads with driving down the center, but it is like it was designed to work with "advisory bike lanes" where both directions of traffic drive down the center of the road while bikes get to use the lanes on either side:
Some of the stupidest road design I have ever seen.
“Possible” to roll out FSD beta worldwide by end of year.
Big update coming next month
V11 single stack with parking lot coming before end of the year.
To follow up on this, this week has been the complete opposite. Absolutely awful drives. Seeing a lot of the same issues people are reporting.The last three days, I’ve had “Whole Mars Catalog” drives. No interventions or disengagements. Even did a “Chuck style” unprotected left turn, used the center turn lane, did great. A couple odd things that need some work, but all in all, pretty decent.
I was just going to comment on @LowlyOilBurner ’s post about how inconsistent 69.2.2 seems to be. Your theory would help explain that inconsistency.Y'know, I'm beginning to wonder. The general idea has been that we get the firmware download, it has its algorithms, neural and otherwise, and we drive the vehicles around the landscape, seeing how the algorithms do, reporting back to Tesla with the video icon as we go.
There's also those of us whose data gets uploaded to Tesla on demand; so, for example, they can compare how we drive vs. how the car would drive. And any such inspection could easily be done sans human hands or eyeballs, all the better to figure out how the algorithms are working.
However, I'm going to add a snivvy: It might be possible that parameters of the system software are being modified by Tesla over time. So, one day, one wakes up and the parameters are that way; the next day, one wakes up, and the parameters are this way. Why do this? To get an idea how the parameter variation affects the car's autonomous driving performance, of course. Done across a large fleet, different areas, different weather, different traffic loads, this would possibly give Tesla even more data on how to Make It All Work.
And might explain why some days everything seems to work beautifully and other days, not so much.
If Tesla is doing this (and that's a big if), well, I guess I don't mind. We're out here doing our testing bit, that's what we've volunteered for. I suppose that the car and driver could get into Big Trouble this way; but that's true of driving around in a true beta software load in any case.
Comments?
However, I'm going to add a snivvy: It might be possible that parameters of the system software are being modified by Tesla over time. So, one day, one wakes up and the parameters are that way; the next day, one wakes up, and the parameters are this way.
Comments?
True but it's certainly not inconceivable that Tesla has various parameters that can be tweaked/pushed without notification - i.e. change this value from 14.6% to 14.9%, affecting positively component A with some potential negative impact to other components. Easily pushed over any network, very small in bandwidth. Those could hypothetically survive a boot. Sure you likely don't introduce any new features this way but modification of parameters designed to be adjustable certainly could be. Perhaps @verygreen knows better but it actually sounds like a smart approach to me.Nothing except a full firmware upgrade can survive a reboot- so that'd be a pretty fragile system.
True but it's certainly not inconceivable that Tesla has various parameters that can be tweaked/pushed without notification - i.e. change this value from 14.6% to 14.9%, affecting positively component A with some potential negative impact to other components. Easily pushed over any network, very small in bandwidth. Those could hypothetically survive a boot.
Sure you likely don't introduce any new features this way but modification of parameters designed to be adjustable certainly could be. Perhaps @verygreen knows better but it actually sounds like a smart approach to me.
I thought that might be the case. Perhaps I should take a video in a couple different cases showing such action.Nope. Mine definitely still slows if I scroll down max speed.... NOTE- it is pretty quick to reset max speed if it sees a sign though