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.
In addition to the snapshot I would send an email to the FSD beta address with the date/time and location plus include a subject description that might get a person/bot's attention. A picture might also help. No idea if this will help you but I've done that twice for intersections where FSD blew thru the Stop sign and both were fixed. Probably just a coincidence but worth a try since it keeps happening to you.Yeah it's weird. The crossing arms are up and are not even visible on the display. The Stop sign clearly is but the car just ignores it. I send a snapshot every time so I hope the engineers can figure out what's going on.
So this sounds like a mapping error. I'm not sure how FSD is at fault here .. it's following the map/route, whereas the non-FSD AP would ignore the map, right or wrong.Driving down Hwy290 from Austin to Houston, previous non FSD AP would drive it pretty well, but every so often the nav would keep jump onto side roads and giving "turn right onto 290" stupid instructions that both myself and AP would ignore and just keep driving along.
Now with the new and improved vision FSD, every time it hits one of those side roads, it detects a 45mph limit, flips from AP to FSD and drops the speed to 45, then flips back to AP and jumps 70mph, over and over again.
LOL maybe the NN is "learning" from another driver in your household...Yeah it's weird. The crossing arms are up and are not even visible on the display. The Stop sign clearly is but the car just ignores it. I send a snapshot every time so I hope the engineers can figure out what's going on.
+1
But I wonder whether the planner would do this if the car was actually going to hit the truck. Basically - why is the planner doing this .... it can't figure out that it may hit the truck on the side or it thinks the chance of hitting the truck are low compared to hitting the curb, so moves to the right a bit ?
Either way - they need to increase the cost of moving to the right so that the car takes a less comfortable but tighter turn that will not cross the line nor hit the curb.
One thing I'd add here is that the turns seem to be tighter. FSD avoided going over the yellow line on couple of turns ... have to watch for more data.
Yes - lot of variability. I suspect many of the "great improvements" or "it sucks now" that we see are actually just such variability.I use FSD almost always on way to work and back, amazing how different the results of the exact same drive with the same version of FSD. I guess I thought you would see similar behavior unless a car or obstacle was detected
OK, I have had this message come up twice so I do know that the interior camera is definitely watching for attentiveness. I got one warning because I was trying to get a snapshot and kept missing the button. Apparently, I was looking at the screen too long and got the warning. Totally appropriate. But still no voice activated snapshot which I am still going to comment on until I get one.Really? It's never alerted me for use of the touchscreen. I have to look out the side of the car for a good ten seconds or so to get dinged.
On that topic - Took me a while but I figured out one on my way home from work - there's a "TRUCK SPEED LIMIT 25" sign, and the 'truck' part is pretty worn, so the car aggressively brakes from 45 to 25.
I think partially visible side lines (and may be center line too) are going to be the issue. If nothing is visible, FSD should treat it as an unmarked road and just drive (ok-ish).Visualizations were pretty reasonable most of the time and predicted double yellow lines even though they weren't actually visible. One time the predicted path was very short as it believed there was no more road, so it slowed down then realized there was more and continued fine. However it seems like FSD Beta currently makes a bunch of micro adjustments for steering and acceleration that results in a bunch of minor slipping.
I think it should. Could be a GPS issue, though. There is one specific point on my daily drive where an Interstate offramp is merging onto the divided highway I'm already on. My FSD beta often (but not always) signals left when it's in the right lane and that merge lane is to its right (or recently, even a bit ahead). Sometimes it will then proceed to change lanes if I don't cancel the signal, but other times it will cancel the signal after about two blinks, perhaps as if it "realizes it's not merging to the left" or "thinks it has completed its merge to the left". Most of my daily Interstate on-ramps and off-ramps have a designated lane, so I don't get to see the behavior for merging from a ramp very often, but I don't think I've noticed it not signaling when I have been in that scenario. That having been said, it's possible I always hit the signal early in that scenario out of pre-FSD beta habit (or like I always hit the signal before switching to turn lanes because FSD beta doesn't currently signal those lane changes).My FSD is doing smooth transitions from one highway to the other but not signaling when it merges into the right lane. Do other people see this? It should turn on the left signal to indicate it is merging into the cars on the freeway's right lane, shouldn't it?
absolutely its at faultSo this sounds like a mapping error. I'm not sure how FSD is at fault here .. it's following the map/route, whereas the non-FSD AP would ignore the map, right or wrong.
Did you report these issues to Tesla ?