...and had pretty much the same results as yesterday.
Very interesting. I assume you've done the bug report thing. It's pretty crazy how vastly different versions behave, and how serious regressions creep in. But, this is pretty much what you'd expect of a ML system approaching its maximums.
Also, the car... both cars, actually, behave perfectly fine with NavOnAP disabled and normal AP working. No phantom braking, and obviously no changing lanes into other vehicles.
I think it's pretty clear at this point that EAP is a simple line follow robot with some radar input. NoAP appears to be the actual semi-autonomous system, and these "corner" cases aren't nearly rare enough and the system doesn't handle then nearly smart enough. I'm interested to see what the event on the 22nd is all about, and whether they give demonstration rides of a fully autonomous system or not.
I don't feel like a calibration issue could be the cause...
The fact that two different vehicles did the same thing pretty much guarantees it's not a calibration issue.
Definitely seems like a YMMV situation, since other's are reporting glorious results... so, who knows. I'm definitely not losing my mind, since I had passengers today and yesterday who witnessed the same shenanigans.
I've had good results, but nothing I'd ever consider glorious. Then again, I disable NoAP/EAP when more than one lane is merging, when vehicles around me are driving extra crazy, and in situations I think are probably too complex. It's not a 100% solution. It's probably a 75-80% solution in simple cases and heavily traveled areas. But it's got a long way to go before the thing can actually drive itself.