I think im experiencing similar problem. I trying to make a route that follows the path, but instead BaseCamp draws me 300km loop and does not follow the path.
Here are the GPX files if someone wants to give it a try.
Im trying to connect my FarWest 1/2 and FarWest 2/2 routes and it seems impossible. I can get across that section if i draw direct straight line. But if i connect my routes before and after to that, ill lose routing.
Maps im using are:
HimalayanTOPO Nepal routable
omtb_nepal_31.10.2019_UC_LOCAL
OSM Generic routable.
Well the issue will be the maps, not BaseCamp. It can only route along paths/trails/roads etc that are a) on the map and b) marked as routable in the maps database. Note you can join a routable section to a direct section then to a routable section in BaseCamp, at least you can in 4.6.2, I've not upgraded to the latest 4.7 versions as they don't work correctly with Google earth.
Thanx. I have followed that path for kilometers and its been routable. And suddenly, it's not. That's odd. Hope I can get it done. It's not an end of the world if it's 2part route.. But probably it's just a lack of skill yet. Just downloaded Basecamp, so I assume I'm 4.7 user. Fairly new to Garmin family.
If you open the route properties and then right click the point you want to navigate in a straight line from, then choose Edit Viapoint then select Direct in the drop down box at the bottom BaseCamp will use the direct profile from there on.. Do the reverse at the point you want to choose a different profile.
Its a known bug of Basecamp and has nothing to do with the map as suggested below. With the old mapsource and the same map it doesn´t happen.
I don´t know any way to avoid it from happening and given how long its exists and how depricated BC is probably considered by Garmin, I guess we will never see a fix.
Where's your evidence that it's a known bug? I've used many versions of BaseCamp over the years and never experienced it?
I can easily reproduce with every map I tried it and it was discussed in the forums by multiple users before. If it´s "known" by Garmin, though, I don´t know, if that was your question.