Silicon Desert
Well-Known Member
Frankly, I hope no one with a following distance of "!" ever gets behind me.
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.
I don't have FSD, just EAP. But the ability to follow at a reasonable distance and smoothness isn't even related to EAP - it's really just how the car behaves while using TACC.Do you even Beta, bro?
(sorry, I had to haha)
I use the Beta for all of my driving, and the approximately half-second latency is painfully obvious in numerous scenarios.
It may not be across the board and may only affect certain NNs, but it’s definitely there. It’s most obvious when there are vehicles up ahead driving perpendicular to you or otherwise could be in your way. A lot of times I’ll know the car will be out of the way by the time we cross their path before the Beta realizes this leading to unnecessary braking. I’ve also seen it happen with traffic signals in rare cases (eg like in Chuck’s traffic light phantom braking video).
Radar-equipped cars, including mine, have been doing that for years.No. Vision is just not as accurate as radar for monitoring precise distance and speed differential so that’s why they can’t do “1”.
My car without radar behaves very poorly at adjusting to varying speeds of the lead car. And frequently gives false forward collision warnings when the speed differential is not nearly enough to cause a collision.
Humans have a 0.2 sec reaction time in normal situations where you expect something to happen.How can you assess the latency of the AP computer when you are not familiar with the code that it executes? Do you have some detailed insight into Tesla's software?
I can see the latency at work simply be watching how long it takes for the car to react to various situations. For example, when a lead car slows and turns into a parking lot, my car continues to apply brakes for at least a half second after the lead car has completely departed the lane.
BTW, human reaction time of 0.25 sec is for unexpected, or sudden changes that are not predictable. When a human is performing an action where the situation is predictable, reaction times are much better. You can steer a car smoothly around corners because you continually assess the position of the car in response to your steering and can correct without a long reaction time. Same goes for the example I gave above where a car turns out of your lane. You anticipate the other car's turn so can stop braking and start speeding up the instant the lead car is clear of your lane.
Even so, 0.25 sec latency is far better than 0.5 sec in a driving situation, right?
That's a planning problem, not a perception problem IMO. The forward collision software is set to "too safe".Radar-equipped cars, including mine, have been doing that for years.
I don't disagree, but was merely responding to the other poster, who seemed to be attributing the behavior to his car's lack of radar. Unfortunately, it can and does happen with radar-equipped cars as well. I've had my car for 4.5 years and only recently moved to Tesla Vision. I haven't noticed any increased frequency of the forward collision warnings. If anything, they might be occurring less frequently.That's a planning problem, not a perception problem IMO. The forward collision software is set to "too safe".
This is an easy problem to solve, as others have suggested. Just change the numbering so 1 is the current 2 and so on. Vast majority of people won't even notice.Why can't they just enable setting "1" under a certain speed? Like during stop-and-go situations when traffic crawls?
precisely my experience as well on our 2017 mxI don't disagree, but was merely responding to the other poster, who seemed to be attributing the behavior to his car's lack of radar. Unfortunately, it can and does happen with radar-equipped cars as well. I've had my car for 4.5 years and only recently moved to Tesla Vision. I haven't noticed any increased frequency of the forward collision warnings. If anything, they might be occurring less frequently.
That said, while I agree that the warning still happens too frequently, at least it's only providing an audible warning and is not panic braking at inappropriate times. I'd rather it warn me a bit too frequently rather than not often enough.
I stated that it is a relative measurement and not an absolute. You CAN'T change how long a minute is but a moment is variable to your situation. So Follow distance is not a "minute" in distance but instead a "moment" and can be what Tesla defines it as.This is an easy problem to solve, as others have suggested. Just change the numbering so 1 is the current 2 and so on. Vast majority of people won't even notice.