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

Bug on climb pro

Hi

when using climb pro, very often the "remaining ascend" freezes. This happens mostly (probably always) on imported gpx tracks.

If I stop/restart the navigation, maybe to a slightly different route, what happens is that the new route shows on the map, but the "climb pro" window retains the old route climbs (still frozen)

I have to switch off the device (and loose the activity)

Any suggestion?

I have version 4.10: I will update the device, but only if this is a known bug that has been fixed.

Thank you

EDIT: I'm attaching images showing the issue. It was a video but my language was not very polite so I'm attaching just two frames.

Here the display correctly says "26 km to destination" (I just loaded a new destination)

But here the climb pro is still stucked on the previous climb (and says "next climb 34 km", that is beyond the end of the current navigation, which is impossible).

  • OK, so when

    I have a ticket open on this.

    it does not mean that Garmin is following this 3D, is it?

    Is any of the users here a Garmin employee?

    Thanks!

  • aweatheral isn't a Garmin employee (but he does appear to have some sort of special association). If a Garmin employee is following it, it's because he created a ticket for it. The Garmin employees that post here (see the firmware notification at the top) appear to have "Garmin-" as the first part of their user name.

    Maybe, there's a bug as part of this. Maybe, if it's reproducible and determined to be a bug, it will be fixed. It's very likely you won't see a resolution of that anytime soon.

    What will you do until then?

    (Your only option now is to try a better file.)

  • At about 3 km/h (moderate climbing speed),

    Mmmmm... 3 kmh ??? So what is low?

  • Doh. I meant 8 km/h.

    That isn't the important number.

    I was using that to get the approximate resolution the device recorded. It's on the order of 2 meters (on the low side). Not 50 m.

  • your bad file

    I really really really appreciate all the time you have spent on my issue, regardless the fact that I may sounded harsh at some point, and I would like to pay you a beer if you only stop calling it "bad". It's a common gpx as billions you can download from the internet, optimized to a  resolution that was more or less the standard when I started recording my tracks on mountain bike, 20 years ago. I'm sure nobody  wants me to trash the result of all that work, :)

  • I'm calling it "bad" to make it very clear that it can't be used on the Edges for navigation. The routing might work (but not always) and you'll regularly get "off course" warnings with them.

    It's a response to you being insistent that it should work after I repeatedly showed (with a picture, even!) why it would have problems.

    That there are "billions" of them won't magically make them work on the Edges.

  • Yes, but this is the other thread.

    you'll regularly get "off course" warnings with them.

    The point here is not the off course for a certain file, is the Garmin freezing after loading a certain file.

  • Yes. But it might be related (as I pointed out). Aweatherall's post said that too.

    If you don't care about navigation (or off course warnings), then the navigation problems aren't relevant.

    If you do care about navigation, you need both problems solved.

    An appropriate file will fix your navigation complaints and it might fix the climbpro issue.

    Using an acceptable file is something to try.

    It appears the only available alternative is hoping that it's a bug and that it's fixed someday (it won't be very soon).

  • Ok I may have found a temporary fix for the Rider Icon freezing on ClimbPro when you select your course go into settings and turn off Course Points.

    I tried it this morning on a steep hill climb and it worked ok. However a data pool of one is not proof I would be interested if anyone else can try this and see if it works.

  • Interesting you have the same problem (not many people appear to).

    I’d be very surprised if this worked.