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

Beta 4.18 - very slow turn by turn calculation (on my device)

mcinner1
over 4 years ago

Strange thing:
with beta software 4.18: no turn by turn calculation, no routing to POI, no rerouting on track deviation, no roundtrip calculation anymore - at least on my device.

Turn by turn calculation stops at 10% - on every chosen course.
Roundtrip calculation rotates for ever at „0“.
Navigation to POI or adress will not calculate.
I have tried it with different maps. Made sure, all needed img files are activated.

I did a factory reset - to no avail.

This is strange, because it seems it is only me (my device) - no one has reported this issue until now.

Just went back to v4.10 and now all is working as usual.

Edit:
it turned out that the calculation does work - but very very slowly. See later postings!

  • 0 over 4 years ago

    Just checked mine. It is acting strange!

    Calculating takes much much longer. On some of my courses it works, but not all. Some (one I have ridden last week) now gives an error (Route calculation error).

    When selecting ‘Ride’, then the ‘X’ for not navigating to the start, I notice that it DOES navigate to the start (and the starts are not near my current position, so that is probably taking up so much time?

    So, there is something wrong. I will revert to 4.10.

  • 0 over 4 years ago

    Hi , I went on two trips (road bike) with the new 4.18 beta and have not noticed any issues with the turn by turn navigation so far. I almost try to follow the routes created in Komoot and have not really concentrated on the recalculation. I will try to have a further look at it. I am not using any functions like POI or roundtrip navigation.

  • 0 over 4 years ago

    What maps are you using? I'm using OpenMTB and have the same behavior. The next time I will test it with the Garmin map.

  • 0 over 4 years ago in reply to Cerina

    I‘ve tried both: Garmin Cycle map and OpenMTBmap (of course the other one disabled in each case).
    To no avail.

    With v4.10 t-b-t navigation, POI-navigation and roundtrip creation work with both maps.

  • 0 over 4 years ago in reply to MacStar

    Former MemberI am using the original Garmin maps (MTB switch disabled).

  • 0 over 4 years ago in reply to Cerina
    Cerina said:
    I'm using OpenMTB and have the same behavior.

    Maybe you try „Roadbiking“ instead of MTB. It‘s too late for me to test it.

  • 0 over 4 years ago in reply to sirfive

    Same here. I rode a 85km route yesterday, of which the GPX was correct. The 1030p could not calculate the route (calculation error). The route was visible on the map as a purple line, so I was able to follow the route manually. But no turn-by-turn instructions.  Even when I was on the route, the 1030p would not notice this. Also, some strange directional arrows were all over the map.

  • 0 over 4 years ago in reply to Microkid


    Please report it to [email protected]

    (I did already - the more reports the better!)

  • 0 over 4 years ago in reply to mcinner1

    I've done some more tests and found out:

    It is as @sirfive mentioned: Calculating takes much much longer.

    I loaded a 45 km mtb course for tbt navigation.
    Calculation started and after some seconds stopped at 11%. On my tests before I gave up after about 5 minutes and stopped the course.
    Yesterday I just let the device do and waited. And - lo and behold - after 18(!) minutes it continued to count the calculation percents.
    To make a long story short: it took 35 minutes to complete the turn by turn calculation successfully.

    I then loaded the same course file to my "normal" Edge 1030 and have controlled the calculation time: 7 minutes!

    35 minutes calculation time on Edge 1030 PLUS vs.
    7 minutes calculation time on "normal" Edge 1030.

    Something's wrong with that software!

    PS: I did the calculation for some other stored courses as well - all ended up with successful calculation, but with incredible long calculation time.