...and all we've got is Purple Rain instead, and only if Spotify/Apple Music doesn't lock up the MCU. My silly wipers are in the off position until I see rain.
On a different but related note, just drove Brisbane to Sydney yesterday on a roundabout detour route with 2023.26.8 and noticed a few interesting things:
Range prediction has been surprisingly spot on. That's definitely been getting better for the last several releases. Predicted arrival for a 350km away SC was at 1%. I wanted a little more buffer so I planted myself behind a B-double for about 100km and gained 5% for an arrival estimate of 6%. Arrived with 5% at the SC. This is all the more surprising as the last 250km of that drive were on the Grafton - Glen Innes - Tamworth route, a route I've never driven before and that has some massive ascents and descents (by Aussie standards). So Tesla would have no data of mine on that route. In fact on this entire ~2,700 km to Brisbane and surrounds the car overall has provided really accurate SOC predictions. As long as I let AP drive of course. This all goes (ludicrously) rapidly out the window as soon as I drive with play factor.
Speed limit sign recognition worked really well*, except for where it didn't: Had another two random instances of the car reading non-existent 50 signs in a 110. Even saved the video to go back and try and find which sign it misinterpreted. Turns out there weren't any signs visible at all. I can only assume that comes out of an overly imaginative database. Also encountered several really effing annoying repeat instances of the car imposing a speed limit of 80 when it was a sign "80 for trucks and buses". They still don't have compound signs sorted apparently.
Autosteer performed nearly flawlessly. Still swerves on country roads that widen for a turn-off, but really did well at all other times, even in situations where I was borderline confused myself on where to go it managed just fine. Brisbane has a few "interesting" locations with complex road layouts and turning options. AP and I saw those for the first time, and I can honestly say AP drove those better than me seeing them for the first time.
I don't often pay attention to the trip meter data, but on this trip I noticed a discrepancy between what Teslafi and the car report. According to the car, I drove 1,107 km yesterday and used an average of 163 Wh/km. Teslafi arrives at 178 Wh/km over the same distance. I wonder where this difference comes from. 10% would make sense if AC/Heat was counted in, so Tesla under-report consumption by reducing it to drive consumption only? Wouldn't make sense to count charging losses either (and would be smaller than that as I've been supercharging only on this trip).
* yeah, it still is a far cry from where it should/could be. One thing I don't get is why Tesla don't harness the power of the masses to improve on this speed sign recognition clusterduck by letting users do simple actions. On an opt-in basis, I think there should be an option popping up on the screen every time the car determines a change to the speed limit should be made, allowing the user to either do nothing (and accept the change), or have the option to undo to last limit (wrong speed detected). Perhaps an additional option "reset to speed from database".