MoreTrout
Well-Known Member
Got it a few days ago and noticed one thing that I wouldn't actually consider an issue other than making something already bad worse.
I think most of us realize the range remaining estimate on the nav is pretty useless and the range remaining on the driver screen display based on EPA estimates is far more accurate and easier to mentally adjust for conditions with even basic math. But at least the nav estimate that routinely grossly underestimated range remaining on arrival would gradually increase during the trip when it figured out you weren't really driving 80 mph uphill in the rain in subfreezing temps the whole way that it apparently uses to calculate range remaining at trip end.
Yesterday I did my usual ~200 mile trip I have done dozens of times. Knowing the distance and subtracting from the driver screen range indicator resulted in me arriving with ~85 miles left. Knowing temps were in the high 20s to high 30s with some wet roads let me estimate I would probably arrive with around 65-70 miles. In typical fashion, the nav guessed I would arrive with 30 miles remaining. At least it didn't try to force a useless charging stop or refuse that route if I didn't.
Early in the trip it did slowly adjust up to 35 miles remaining, but then stubbornly remained there the entire trip. Even when I was a mile from my destination with 68 miles remaining on the driver display, the nav still was delusional enough to display that I would arrive with 35 miles remaining.
Just one trip since the update, but based on previous behavior this update appears to actually be a step backward in an already dysfunctional nav range remaining calculation.
I think most of us realize the range remaining estimate on the nav is pretty useless and the range remaining on the driver screen display based on EPA estimates is far more accurate and easier to mentally adjust for conditions with even basic math. But at least the nav estimate that routinely grossly underestimated range remaining on arrival would gradually increase during the trip when it figured out you weren't really driving 80 mph uphill in the rain in subfreezing temps the whole way that it apparently uses to calculate range remaining at trip end.
Yesterday I did my usual ~200 mile trip I have done dozens of times. Knowing the distance and subtracting from the driver screen range indicator resulted in me arriving with ~85 miles left. Knowing temps were in the high 20s to high 30s with some wet roads let me estimate I would probably arrive with around 65-70 miles. In typical fashion, the nav guessed I would arrive with 30 miles remaining. At least it didn't try to force a useless charging stop or refuse that route if I didn't.
Early in the trip it did slowly adjust up to 35 miles remaining, but then stubbornly remained there the entire trip. Even when I was a mile from my destination with 68 miles remaining on the driver display, the nav still was delusional enough to display that I would arrive with 35 miles remaining.
Just one trip since the update, but based on previous behavior this update appears to actually be a step backward in an already dysfunctional nav range remaining calculation.
Sponsored
