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.
Good 'ole Cambridge...why am I not surprised with this new announcement..
Drivers no longer have the right to turn right on red in Cambridge
Drivers aren’t legally allowed to turn right on red anymore in Cambridge, Massachusetts. State law allows drivers to make right turns at red lights unless otherwise noted by “No turn on red” signs. Those signs now bar the maneuver at every traffic light in Cambridge. Two years ago, city leaders...www.nbcboston.com
AP and FSD do follow way too close...
Even with the following distance set to the maximum, TACC/AP follows too closely. I observed the same with the FSDS trial with that same setting and FSDS set to chill.Just follow my motto: It's not illegal if you don't get caught!
I know you can change the following distance when in AP (see screenshot below from the manual). Is there a way to adjust it when in FSD? Does the setting made in AP carry over to FSD? When I was using FSD on the trial, it seemed to carry this setting from AP to FSD, but I never thought to test it.
In theory, an automated driver can be programmed to know, based on GPS location, what traffic laws regarding right turn on red, default speed limits, etc. apply to that area.Humans are geofenced, in a very generalized way. We get comfortable with our local traffic laws, how our intersections work, how our roundabouts work, being able to turn on red, or being in the intersection when the light turns red, etc. If you go on a cross-country road trip, it's very likely you'll run afoul of local traffic laws unintentionally. Hopefully you have an understanding officer that pulls you over and explains the differences, letting you go with a warning.
You and I have different parameters as I keep mine set at 3 (which on average is a 2 second following distance) or 4 if it is raining. I have never had to panic-stop override TACC for safety issues (or if I did in the past, it has been a VERY long time). And I have used AP on probably 90+% of the 90K miles on my 3.Even with the following distance set to the maximum, TACC/AP follows too closely.
I have it set to 7, which seems closer than 2 seconds.You and I have different parameters as I keep mine set at 3 (which on average is a 2 second following distance) or 4 if it is raining.
Even with the following distance set to the maximum, TACC/AP follows too closely
You and I have different parameters as I keep mine set at 3
I have it set to 7, which seems closer than 2 seconds.
Damn you: now I have to try 7...I tried 7 the next time I was in the car on a road trip...
Why, do you save time by driving closer to the car in front ?!As a 2-3 user, I remember last time I read this and I tried 7 the next time I was in the car on a road trip, and my wife and kids were like "why are you staying so far back from the car in front of you" within just a few minutes, it was that odd.
Yes! That would be the right thing to do, and communicating that info would be great ADAS for regular driving.In theory, an automated driver can be programmed to know, based on GPS location, what traffic laws regarding right turn on red, default speed limits, etc. apply to that area.
You need to turn on FSD, let it fail in the usual spot, disengage and press the talk button to send a short message to Tesla about it. Once they know about the problem YOU are having, it might get fixed sooner.Unfortunately, as I said, I'm seldom on time so don't want to have to take the time to pull off the highway, park, then start off again, hoping problems will be fixed.
FSDS drives 42 MPH in a 35 MPH speed trap zone here (near Tesla's Palo Alto engineering offices) and drifts left onto the double yellow line, both mistakes requiring overrides.Please add a post if, after a few weeks, you stop using it because it is faster to drive from point A to B on your own.
Also the phone-key finally detects who's getting into the driver seat and auto-selects the right driver profile.
I don't have wifi at my parking spot so any voice messages go into the ether.You need to turn on FSD, let it fail in the usual spot, disengage and press the talk button to send a short message to Tesla about it. Once they know about the problem YOU are having, it might get fixed sooner.
Just wanted to update this - I recalibrated the cameras (which took a LOOONG time) and 12.3.6's behaviour was greatly improved. It feels much smoother and more respectful of distances to curbs, the roadside, and other cars. I'm now actually having quite a few zero disengagement drives.Same here! First short drive was uneventful, with the exception that it accelerates from every stop like it’s a dire emergency. That part feels very unnatural.
ETA: Another drive and the acceleration really is annoying, rather than tapering the acceleration as it approaches the speed limit it accelerates hard right up to it, then actually has to dip into the regen to keep from going over. Very awkward and unnatural. And when approaching slowed or stopped traffic, it doesn't slow down until the last second and then brakes hard. In only a few kms, I had to disengage about 3 times. C'mon Tesla, this stuff should be the low hanging fruit and even 11.4.x did it better. As many others have also noted, it seems paralyzed with indecision at an intersection with no other traffic. Also, when entering a school zone (which it doesn't recognize) I scrolled that speed limit down to 30km/h from 50 - which it immediately reset to 50 and accelerated hard back up, forcing another disengagement rather than fight with it.
It still feels very, very beta.