My complaint: Autosteer will not operate faster than 5 mph over the posted limit. On Maui speed limits are idiotically slow and everybody drives 10 to 15 mph over the limit. So when there is a lot of traffic I cannot use autosteer without being a public nuisance and holding back a very long line of cars, and creating an actual safety hazard as they all try to pass me. So when the traffic is heavy I do not use autosteer. I wish this limitation did not exist.
It doesn't exist if you use it where it's intended to be used (limited access divided highways per the manual)
You're using it outside the ODD, so it has further limitations to the system (also per the manual).
City streets (in FSDBeta anyway), FWIW, has no such limitations and you can set the speed to anything you want up to the max (80) regardless of posted speed limit- same as you can regular EAP on freeways.
Does EAP on HW2.X work well enough that the majority of buyers are happy with it? Where the features, and the performance of those features match expectations?
Yup.
Longer range on smart summon would be nice I guess... but overall quite happy with it.
EAP is plagued by four things.
Pretty sure you're not using "plagued" correctly here.
It's plagued by features like Smart Summon, and Autopark being part of it. But, neither feature really has anything to do with L2 highway driving.
Yeah... "does more stuff than you'd expect" isn't really a plague.
Heck even if the "extra" stuff isn't great that's not a plague.
For these feature to work they require a lot of processing power.
<citation needed>
Pretty sure autopark uses a lot less processing power than Navigate on Autopilot for example.... (and it's not like both need to run at the same time)
It's plagued by Tesla ignoring HW2/HW2.5 while all the development work happens on HW3.
...what?
EAP has been feature complete since 2019. How are they "ignoring" something that's already done?
It's plagued by HW2.X being such a small part of the overall fleet. Why optimize for an architect that so few people have?
Again- not a "plague"
HW2s promised features have all been delivered. 2+ years ago. It's done. They'll fix bugs and occasionally clean up code, but it's not getting anything "new" anymore. Same as HW1 was years ago.
If you like what you've got- great.
If you want other, new, stuff- you'll need to buy it (that's FSD- and it comes with free hardware upgrades as needed too!)
It's plagued by Tesla using so much of HW3 for FSD that they even if they manage to get it to work it might only work at L2 because of a lack of redundancy.
...wait, what?
EAP is "plagued" by how much compute stuff that
is not part of EAP uses?
EAP, a system
never intended to be more than L2 is "plagued" by being... L2 exactly as ever promised?
Yeah- you're definitely using that word wrong.
The EAP at L2, and FSD at an autonomous level was supposed to make all the difference. It was supposed to allow EAP to work on lesser HW. But, now the lesser HW is looking to be HW3.
I'm not even sure what that sentence is trying to say.
EAP is L2. It only needs HW2.
And it's been feature complete since ~October 2019.
It doesn't "need" anything. It's finished.
For full disclosure the primary reason I paid $3K for FSD (on top of the $5K for EAP) is the feeling like old HW would be forgotten about, and that ultimately I was better off with HW3 that was promised with FSD.
Same.
My own expectation was with a computer upgrade I could probably get L3 highway, and I'd be perfectly happy with that (since at the time 95% of my driving was highway and it'd be nice to read a book or something while doing that)
I still think the sensor suite is sufficient for that task. Single stack when it comes to highways will give me a much better idea how near the software is for it though--- as from what I've seen of FSDBeta it already has code to address most if not all of what's "missing" for it to be L3 highway right now (dealing with partly-in-lane objects and handling temporarily vanishing lane lines)
My expectation was that they wouldn't be able to pull off Autonomous driving, but that NoA would be pretty sweet. It's been over 3 years and NoA still doesn't work that well.
Works awesome for me. Still use it for nearly all my driving, virtually never have to intervene for anything.
Any time I'm forced to driving anything else like my wifes vehicle I'm like "What? I have to STEER, like some sort of peasant??"
Like Auto-lane change has roughly a 50% chance of canceling if its attempted when a semi-trailer is the lane next to the one your changing into. At least that's been my experience with it.
Not remotely mine.
It could use some improvement to the logic on WHEN to change lanes based on upcoming exists, but I can't recall the last time it aborted an auto lane change (it did this fairly often when the feature first came out but not for a long time)- and it hasn't aborted an automatic-but-user-prompted one (which it does significantly quicker) in years.