Hopefully they feel comfortable rolling it to a few more users outside of California where things get a bit more real.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
FSD v12.x (end to end AI)
- Thread starter Buckminster
- Start date
-
- Tags
- #fixphantombraking autopilot chill is not chill elon is an ass fix fsd extreme late deceleration fsd does not commit to go fsd does not maintain proper speed fsd hard and late braking fsd jerky driving fsd late deceleration fsd stops too early too quickly fsd stops too far behind line fsd tailgating in city streets
I just disagree with highlighting that as slow. Certainly quicker than my V11 build. The bike is barely past the car and it starts thru the intersection.
Let's not let perfect be the enemy of good.
stopcrazypp
Well-Known Member
Yep, you can once again thank the defeat device creators and users. The steering torque detection also got worse because of the whole defeat device mitigations they had to do.
I'd have a hard time calling that a rolling stop, that was no stop at all lol just slowing down to take the turn at a comfortable speed
05:35 for a timestamp
This is an example of cheaters making things worse for everyone.
A typical rollout sans the influencers for a week since it was only one influencer. Now it goes out to about 1% random and Tesla watches for a week for any unintended bugs. They we likely get an update (12.2.2) and then rollout to more like 5% to test for a week. I say it is looking good and fast if anything. Hopefully most of us will see 12.2.3 in near no time at all.
It's a long tradition and why we have other inconveniences like locks, passwords and lawyers.
DanCar
Active Member
The V12 drive from FSD Arthur with some event times. Originally posted by @replicant, and some of these observations have been made upthread.
00:25 Nags can no longer be defeated with either scroll wheel
03:16 Driver requires wiper use before FSD
03:42 Rolls right turn at stop light. (5 mph)
03:42 Right turn, immediate move to left for left turn.
04:46 Slowing for railroad crossing (35 to 30 mph)
04:52 Slowing for speed bump (34 to 18 mph)
05:09 Accelerator intervention for left turn at stop sign
05:41 Rolls right turn at stop sign (10 mph)
00:25 Nags can no longer be defeated with either scroll wheel
03:16 Driver requires wiper use before FSD
03:42 Rolls right turn at stop light. (5 mph)
03:42 Right turn, immediate move to left for left turn.
04:46 Slowing for railroad crossing (35 to 30 mph)
04:52 Slowing for speed bump (34 to 18 mph)
05:09 Accelerator intervention for left turn at stop sign
05:41 Rolls right turn at stop sign (10 mph)
AlanSubie4Life
Efficiency Obsessed Member
Not exactly. I think the various defeats and workarounds and sitting in the backseat, etc. pushed Tesla to use the cabin camera, and make it work for attention monitoring.
This is a benefit for everyone - we definitely want the car to know when we are looking at the road. Long term it is safer for everyone. You can imagine that monitoring being a huge safety improvement even when not using FSD! (Not done yet, but in future…)
The wheel torquing is more arguable. Though it really shouldn’t be worse - it’s been proposed for a long time that Tesla distinguish a wheel weight from a person’s hand. It’s probably quite a different signature.
I personally don’t find the torquing to be a problem most of the time. Every now and again it seems to enter a weird mode where it really does not seem to detect torque no matter what, but seems more like a bug and goes away after disengaging. And it does not happen often (once every week or two).
AlanSubie4Life
Efficiency Obsessed Member
Presumably this is going to lead to a recall. Either that or there won’t be further rollout until this is sorted out. Recall not assured if the release is really limited and quickly patched.
Yes. I think the reason I get V12 is Tesla needs more people to test in San Diego. Unlike SF, traffic in SD city streets is very fast. 50, 55mph on main street is normal. I disengage this morning because V12 still moved too close and too fast to the creeping line on a 50 mph street with heavy traffic and big trucks. I saw the creeping line too close to traffic on the screen. V11 had the same issue.
Last edited:
City street navigation in general is better. But there is a regression.
V12 failed to turn from street to my work place parking lot. It moved to a the turn lane then turned early and run about 1/2 foot over the gate dividing island. V11 did not move to the turn lane (because it's too short) and turn correctly.
V12 has a good behavior with right or left turn. When waiting for it's turn to make turn, it turns right away when the last car is about to enter the intersection. It's very natural and safe.
Yep, it slowed to 10mph which is a bit faster than a rolling stop. Twice the blue path line appeared to indicate it planned to stop. Maybe with the line so far behind the stop sign FSD 'forget' there was a stop sign? Some similar T intersection training data likely has no stop signs so there could be valid reasons to barrel though. What is v12's 'memory' retention? The downside might be the longer it holds onto old stimuli the slower it might respond to new stimuli.
I agree that there will likely be a few issues needing training data set tweaking before it goes full release. Tesla wants to get this one as good as it can be.
Last edited:
Similar threads
