eRacer
Well-Known Member
Wanted to bump this up as the current update didn't fix the issue with the navigation. The destination is still called out on the wrong side of the road.
Sponsored
This is your first post in this thread. What destination are you talking about? Did you report the issue (see above)?Wanted to bump this up as the current update didn't fix the issue with the navigation. The destination is still called out on the wrong side of the road
I don't understand why my "first post" on this thread has any relavance to me brining up an issue that another member as aslready. (Posts #3, 5 and 8 in this thread.)This is your first post in this thread. What destination are you talking about? Did you report the issue (see above)?
And why would you expect that a vehicle software update fixes a mapping data issue?
If you report issues like this, the mapping data gets fixed. I have done it twice now, and both times it got corrected within days in Mapbox. It can take a week or so after that for the changes to start showing up in the vehicle.
It's totally relevant because your post said "The destination is still called out on the wrong side of the road ". That references a problem from the past that hasn't been fixed yet, but you never posted about that past problem. You provided no context about what destination was or what you have done about the problem. And you said nothing about when and what you did to try to correct that, and whether you even read or followed the advice given by previous posters.I don't understand why my "first post" on this thread has any relavance to me brining up an issue that another member as aslready.
See, once you start adding details, it's a different story ...The issue I am pointing out is not specific to a location but as to how the desination is called out on the incorrect side of the road for EVERY location. It's not an error with the MAP. However an error in the guidance system.
Again, new information - no one else has said this is something that only started occurring on a previous update. Did you expect us all to know the details of your particular problem when you never posted those details before? You bumped this issue because the problem was "still" happening, but the OP has a different problem than you and you never explained your problem.This error only came up after the previous update. Hence why I thought that the error would have been corrected with this current update.