You are mixing your metaphors.
But in general if a release doesn't get into wide distribution in a couple of days, they have found some issues.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
FSD Beta 10.11
- Thread starter EVNow
- Start date
But in general if a release doesn't get into wide distribution in a couple of days, they have found some issues.
PACEMD
Active Member
Just collateral damage, no big deal. The FSD-beta contract you signed states you are willing to die for God and Tesla.
Last edited:
I didn't see anything about God in the contract.
PACEMD
Active Member
OMG, it's there alright. Cross my heart and hope to die........
I couldn't agree with you more. I didn't buy a Plaid so I can spend my life in the 2nd or 3rd lane getting passed by minivans . This is insane. The minimum they could do is say when they are allowing additional beta users.. We should all start tweeting a similar message to Elon and the AI team
They keep trickling the release in Canada. Doesn’t bode well for the “found some issues” hypothesis
PACEMD
Active Member
I got FSD-beta in December 2021 with a safety score of 99. I was never penalized for aggressive/fast driving. Anyway, the safety score ain't really the thing, it's just some minimum requirement to get you in the line. It's like sn SAT score. An almost perfect score won't get you into Harvard but it does qualify you to be considered. With FSD-beta you qualify and then you get in when you get in, when they need you. Speculate all we want, it doesn't change a thing.
Last edited:
Every release has some regressions. I noticed a lot of improvements in 10.10.2 but a couple of intersections that fail every time now that we’re fine in 10.8 and 10.9.
BrandonR22
Member
I know this is on the AI Forum, but real quick has anyone experienced absolutely no sound coming from 8.2? Updated last night and have tried many TS steps to no avail. BT, Spotify, TuneIn, even caraoke doesn’t work. Blinker and Hazard noise does however.
Yeah, but that line of thinking made more sense when new entrants joined from the queue on a regular basis in '21. The problem now is that there's a long gap between new entrants and no distinction between the "qualify" and "when we need you" phases, so I'm now stuck perpetually qualifying (and e.g. living in fear of overzealous FCWs that can happen in situations nobody would really find unsafe) without knowing anything about when they need me. I'd really love to be in the beta and I think I could uniquely contribute pretty useful data and reports, but if I un-enroll now, there could be a wide release tomorrow that I failed to get on board with and then I'm back to square one again. I'm stuck in perpetual qualifying limbo and not able to help. They could fix this a few different ways:
1. They could do an approval week (or two?) right after you push the button, then at the end of the approval trial say "Ok, you're approved with a score of 99" and turn off the Safety Score, and eventually move you to beta when it makes sense at some point in the next few months.
2. They could wait until they have a release they're fairly confident can go to a wider batch of testers, and *then* turn on the button and tell everyone they have a week or two to qualify.
3. They could even leave the current mechanisms alone, but communicate more clearly and accurately as to their expected timelines. If someone at Tesla had, back in January, said "given what's going on right now, we *probably* won't enroll more US drivers until at least X" and continued giving best-guess updates as they can, I would never have clicked the button back in January. I'd wait until it looked likely that I'd only have to qualify for a week or two.
On 10.2 currently and noticed some weird stuff with sound on FSD. Sometime when the blinker goes on I get a second on static and the radio / Spotify goes out. It stays out until I reset the car. It doesn't happen every time but does seem to happen about half the drives.
PACEMD
Active Member
They could do anything but the fact is they do what they do. This is not a line of thinking it's just fact. I requested FSD-beta in March of 2021, when the request was by email, when there was first a discussion of pushing FSD-beta to those who requested. I had driven 35k miles with entry into the beta program not even a possibility. The safety score thingy came out months later and I didn't get FSD-beta until December, 9 months after beginning the process. Waiting sucked but I was just glad there was now a method of entering the program. When you are waiting for something you really want it always speeds things up to not give a sh*t..........
Last edited:
BrandonR22
Member
Interesting. Thanks for that. When I say it went out after the software update, it was minutes later that I got back in the car and no audio. Just got off the phone with Support and as I suspected, I have done all TS steps. TikTok, Netflix and Hulu sound all don’t work either. She said to do a service appt and “enginnering will try to roll me back”. She acted funny when I asked her if this is a trend on 8.2.
This the topic were FSD 10.11.1 user feedback is supposed to go, no? Assuming a topic with feedback:
Two observations after limited use: first mile or two fine until an approaching car seemed to trigger a ~15mph slowdown in perhaps a couple seconds and loss of the visualizations with FSD still engaged. Looking at images, path swung slightly toward oncoming car in second frame,. I think the car disengaged and I kept driving.
This is similar to issues in previous versions but different for me in that I don't recall losing the visualizations on this road. What I wonder is how common this is when driving FSD, what causes it, and if this can be corrected.
FSD disconnected:
Second encouraging incident was taking a right turn properly that always previously failed. Previously either overshot the road changing mind about turning or trying to drive into the shrubbery just past a road I always take. I was so pleased!
Two observations after limited use: first mile or two fine until an approaching car seemed to trigger a ~15mph slowdown in perhaps a couple seconds and loss of the visualizations with FSD still engaged. Looking at images, path swung slightly toward oncoming car in second frame,. I think the car disengaged and I kept driving.
This is similar to issues in previous versions but different for me in that I don't recall losing the visualizations on this road. What I wonder is how common this is when driving FSD, what causes it, and if this can be corrected.
FSD disconnected:
Second encouraging incident was taking a right turn properly that always previously failed. Previously either overshot the road changing mind about turning or trying to drive into the shrubbery just past a road I always take. I was so pleased!
PACEMD
Active Member
And the safety score didn't affect my driving at all. As a former NYC taxi driver of some years, I drive rather fast and aggressively. I didn't fundamentally change my driving for a score. I did follow the scoring to see where the software thought there was an issue, mostly out of curiosity. The observations were that I was often too aggressive with left turns, fair enough, when the road is empty I often cut across the lanes and that I was braking too aggressively. Braking? I don't even use no stinkin' brake........that said I'm very glad that scoring has gone away.....
Where are you seeing this? It looks like the release has really slowed according to Teslafi (I know that's not a perfect source, but it's informative)
jebinc
Well-Known Member
Similar threads
- Article
