I can hardly believe there isn't a thread on this yet, but could not find one by search, so here goes!
Informed speculation please: with AP2 in any active mode (TACC, Autosteer) the depiction of the road has wiggling/jittery/unstable depictions of lane boundaries. Why would this continue for the past several FW versions? (currently on 17.9.3)
I mean, clearly there is software filtering to produce short term stabilization that is either lacking, detuned or inadequate. What purpose would Tesla AP team have in releasing SW with such behavior?
1.To explicitly/visually communicate NOT to trust the AP sensors?
2. Because the internal SW/filtering/hw needs serious refining and thy pushed it out too early?
3. The sensor fusion is so noisy they haven't worked out yet how to replicate AP1 performance levels like MobilEye?
Informed speculation please: with AP2 in any active mode (TACC, Autosteer) the depiction of the road has wiggling/jittery/unstable depictions of lane boundaries. Why would this continue for the past several FW versions? (currently on 17.9.3)
I mean, clearly there is software filtering to produce short term stabilization that is either lacking, detuned or inadequate. What purpose would Tesla AP team have in releasing SW with such behavior?
1.To explicitly/visually communicate NOT to trust the AP sensors?
2. Because the internal SW/filtering/hw needs serious refining and thy pushed it out too early?
3. The sensor fusion is so noisy they haven't worked out yet how to replicate AP1 performance levels like MobilEye?