Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Mapping errors in v12 and now v12.14(b) (RESOLVED)

der_bierpuncheur
over 3 years ago

As a few others have mentioned, the device will not calculate a map past 39%. Works fine while recording, but cannot build a route then follow it. Thew device freezes then shuts down at 39% calculated when trying to map an uploaded course. The problem was mostly continuous, but I was able to get a few routes to work on v12, but unreliably. When the beta was pushed out, I took the plunge and cannot get the device to map any routes now. I have sent beta feedback to Garmin with error logs. I'm sure I am not the only one with this issue.

I recommend we flood their beta team with reports of this error, because effectively the main appeal of the unit (large screen with good maps) is unusable to build and follow routes.

See answer below, the issue is resolved, it is NOT with the firmware, but a corrupted activity profile.

  • 0 over 3 years ago

    Hi Dachs6,

    fortunately I can't confirm  the bug you described.

    I used FW 12.0, 12.13 and now 12.14 without error.  Route calculation workes fine for me, even with thirdparty maps (OSM) on SD-card.

    Routes were planed by BaseCamp mostly as tracks.

  • 0 over 3 years ago in reply to offenbacher54

    Hmmm. Maybe I should do a factory reset of the device. Maybe some fo the code is corrupted...though I've seen a few others in another complain of a similar (or same) error. Probably wouldn't hurt to do a "clean" install.

  • 0 over 3 years ago in reply to der_bierpuncheur

    If you have the popularity layer enabled try disabling it & see if that helps. Some users have seen this issue with it enabled. I've had times when it has stalled at 39% for about 10 minutes before continuing the calculation but I haven't had the device crashing... Yet! 

  • 0 over 3 years ago in reply to hotdogpartysausage

    I tried that once, I thought....I'll give it another shot before I go "nuclear."

  • 0 over 3 years ago in reply to der_bierpuncheur

    It's worth a shot. Before going through the pain of a factory reset

    Another thing to have a play with is your avoidance settings & also check the routing mode in the activity profile is suitable for the course your are trying to calculate. These shouldn't or should I say never used to affect downloaded courses but sometimes things get changed

    Some people have also had issues where the course crosses a border into an adjacent country, if that is relevant to the courses you're having issues with

  • +1 over 3 years ago in reply to hotdogpartysausage

    I went back in and cleared all of the options on "avoidance settings" and turned off the popularity routing, and still the same result. Grown frustrated, I changed the activity profile from "ROAD" to "GRAVEL." Boom! It routed no problem. Then I turned back on the avoidance setting "Toll Road," for obvious reasons. Still no issue with routing. Then I turned the popularity routing back on, and still no problem. Of note, when I switched to gravel and ran the route calculation, it took about 5 seconds to complete the task, rather than take several minutes.

    At this point, I suspected I had a corrupted activity profile for "ROAD." So I deleted it, and rebuilt it by copying "GRAVEL," which is set up with the same screens, just a different activity profile color. With the new "ROAD" profile, it calculated the route as expected, and is now much faster, calculating 100km routes in seconds, not minutes (as previously was norm, on v11.xx and well before).

    Bottomline: issue was NOT with the firmware, it was with an apparently corrupted activity profile.