The bounty is endless praise from me.
Now I'm gonna have that song stuck in my mind for the rest of the day. My whole family is gonna suffer for that.
Challenge accepted.
H2O is wet 2......
I agree but are we talking true in the flesh north? Coriolis was a southpaw, you know.......
Chin up, I just use the North Star.......
Well, now that the Cybertruck can cross the oceans we're up sh*t's-creek, without lanes........
You're very welcome......Now I'm gonna have that song stuck in my mind for the rest of the day. My whole family is gonna suffer for that.
Thank you!
A key part of the challenge is you can't be trying to get the strike. We're searching high and low for video captures of the spurious strikes which apparently occur without warning, and while using the system correctly! They've never been documented on video, yet apparently occur all the time.
Well, it's happened multiple times for me, consistently and constantly on this version of FSDb, I'll relate the story in detail a bit later, no time just now. Never happened before like this without warning, just a sudden red screen out of the blue, as it were, then flashing blue twice for fractions of a second after the red screen, followed by an immediate strike, with no chance at all for corrections, and where I have to stop the car to reset. Driving interstate with NOA but new version of FSDb, 69.3.1, 2022.36.20. Driving exactly the same with NOA as most of my 50k-plus miles of interstate commute. I'm not even close to alone on this. It is indeed a thing. And I'm not a noted FSD complainer, I only paid 6k and have low expectations. I only need/want it to drive me back and forth to work, on the interstate, something it's always done well, until now. Not the only thing that sucks out loud with this update. Later. And video? Sorry but I don't have a mounted cab video. The inherent car videos aren't going to show a thing.
Wonder if there was some weird server issue that might’ve caused it. There was no warning or anything prior to the yelling, beeping, and the large grab the yoke and steer manually message…. I wonder if any sort of server transition to v11 could’ve messed with the matrix
Well something, that matrix is seriously altered. Just strikes, without warning, and no known cause from my experience with previous 56k miles of FSD/NOA. I had one strike previously, I've had over 20 since the update. FSDb suspended until the next update. I get on the interstate, drive as I have always with NOA, watch the screen, 8-12 miles and bam, a strike that cannot be corrected. I can still use NOA it just doesn't work. Coming home on Tuesday I had to stop 9 times to reset.
wonder if it has anything to do with the “single stack”
I kinda think you have something wrong with your cabin camera, like a loose wire or something.
I don't care if you expect it or not. It does in fact happed. I didn't expect it either.
There is nothing wrong with my cameras, I drove to work 150 miles with NOA functioning as always, updated the software, and driving home was not the same. You can try to dismiss this all you want, but it's not a sudden breakdown of equipment and me not driving correctly. This is precisely why I was hesitant to post this.....It is in fact a thing.
