You have to turn off "off-course" alerts, which, while losing you that useful functionality, at least stops the recalculation. But it's shocking that after literally YEARS of people complaining that turning off recalculation doesn't, ahem, actually turn it off, that Garmin still hasn't either acknowledged or fixed this problem.
When you load a course & select ride the Garmin is Calculating the course not Recalculating
What this means is the Garmin is taking the course file you have loaded and is creating the TBT prompts it will use for navigation. The downside is it also changes the total height gain of the course based on its own internal DEM map.
The only way to prevent the calculation is to disable turn guidance in the navigation settings Then you have to set the course you want to use to always display in its settings
You will get the course displayed as a permanent thin line on the map, you won't get TBT and you will have to leave the map displayed so that you can manually follow your course
Thr Recalculation setting only affects what the Garmin does when you go off-course, disabling it has no effect on the initial calculation stage
There's nothing to stop you loading the course and starting the calculation well before you start your ride just don't select navigate to start. Once it's done you can put the Garmin to sleep & turn it on again when you are ready to go. Once it gets a GPS fix you should get your TBT without interruption
Thank you. I fully agree with you. The "off course" warnings are a useful feature when following a course. I am also complaining about this issue around these forums since I first bought this unit in September 2016. What makes me crazy is that my previous units (an Edge 800 and later a Touring Plus) worked flawlessly on this regard. I made more than 10,000Km with my older units following courses with manual waypoints without major issues. And even with the 820, I was able to make it work more less OK until version 3 or 4 of the firmware (in spite of several crashes). After that, the behaviour became cahotic. Unhappily, I sold both the 800 and the Touring to buy the (then expensive) 820, never imagining that such "upgrade" would make me lose my most used features :-). But, more than that, what puzzles me is that I cross these forums and I find that this bug is now spread along all Edge families (520plus/830/1030), leaving all of us without options than buy an old second hand unit (or other brand). It does not make any sense!
I'm thinking you're missing the point -- or at least my point. We all agree that if you turn on Turn Guidance, your Garmin unit is going to calculate the route with TBT directions. The complaint I (and, I think, others) have, is that IF you leave that determined route AFTER you have started riding -- your unit will begin recalculating the route to try to get you back to the previously calculated route -- EVEN IF YOU HAVE "RECALCULATION" TURNED OFF. Leaving aside that the algorithm invariably tries to get you back on course by making a u-Turn (which almost no bicyclist wants to do -- instead you want to rejoin your course at a later point), turning off Recalculation ought to have an impact on this behavior, and it doesn't. As best as I can tell, it does exactly nothing. Turning it to Prompted is worse in a way, because it will keep popping up the prompts, which you then have to manually dismiss, the whole time you're off course.
Hi. I may have missed the point then I guess sorry. The information the OP gave suggested it was maybe a misinterpretation of the calculating stage he was seeing not recalculating especially when changing courses mid ride
I have recalculation turned off on my 1030 & don't experience the 're'calculation issue you are seeing. If I start with a route or change a route mid ride it will calculate the route but no recalculation. Sometimes it will calculate the route twice for some reason but never displays recalculating
Are you using the Road Cycling Routing Mode in your Activity Profile?
My bad. I actually have the Edge Explore 1000 -- whose forum has disappeared. It was only the most recent firmware update on that device -- 9.30 -- that introduced this bug, along with actual release notes saying it was IMPROVING recalculation. So I'm guessing Garmin hasn't seen fit to introduce the bug to the 1030 yet, you lucky folks! I wonder how the 530/830 will handle recalculation?