Father Bill
Member
Yep, 2.5.21 downloaded and installed. It includes new charging options(destination chargers) and a couple of tweaks for AP cars.
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.
Yes, it's full Autopilot
I kid.
Not very nice of Max to make a boldfaced false statement, at least without a :wink:How many people are going to scream in excitement, rush to the car, wait two hours, then scream in sadness?!?
How many people are going to scream in excitement, rush to the car, wait two hours, then scream in sadness?!?
Not very nice of Max to make a boldfaced false statement, at least without a :wink:
:smile:Hey now, I put a very small disclaimer on the bottom saying that I kid!
At first I made it white, but then realized this forum wouldn't find the humor (on another forum there is a "spoiler" tag, which hides the font, but people there know to look for it) and changed it to VERY light grey
That's not new, it was included a few builds ago. You can toggle back and forth for the map to show only superchargers or superchargers + destination chargers.Now includes destination chargers on the map /navigation
I know it's most likely just patches, but it's quite odd that it's numbered differently. Makes me think it's something bigger.
Nice first post.Perhaps there is just a 1 byte (0-255) limit for the minor version?
Nice first post.
This is a pretty good theory, so far not disproven.
My car is still installing but I'll let you know. Maybe they have the 3G "fix" in this release. Doesn't sound promising
All it takes is one tool confused by "large" numbers to motivate the entire infrastructure to respect the constraint.Yes, while not disproven, I find it a very dubious theory. I mean, nowadays, who uses one-byte integers when there's really no need for it. It's not like the build number is repeated thousands or millions of times (like in a database) where single bytes actually count, and most likely, the version and build numbers are just stored as strings. Storing the individual build numbers x.y.z as a three byte integer doesn't make sense to me for software development. I know it's the internet and people will disagree, and that's fine. But I suspect someday in the near future, we'll see a build number that does disprove this theory.