
#Garmin basecamp 4.4.2 Patch
I had to downgrade mY Mapsource back to 6.15.7 and patch then it will show many of the unlocked maps that won't show with the latest 6.16.3 version. What am I doing wrong? I've got several IMG files that work perfectly on the Edge 705 device but I have not been able to get any of them to disply in either basecamp nor Map Source. that page just doesn't look at all like the examples I've seen for patching the ms bit to 0 so it will display in basecamp. When I use Gmaptool and open the gmapsupp.img, it will display all the information but the write tab doesn't have the option for the ms bit. I've tried everything I can think of and cannot ever see a gmapsupp.img that is installed on my edge 705 and that works fine on the device. So far the only way I've been able to see any map in BaseCamp (or Map Source) is if I have the actual DVD or the MapSource version. I have BaseCamp 3.2.2 and i've tried this with and without the patched. but I have read dozens of posts and have searched quite a bit before asking this. It also seems like selecting only "Fastest" or "Shortest" doesn't affect much on the accepted length of the route, while adding "Avoidance" seems to allow for slightly longer routes.I'm pretty new. But when selecting other destinations I notice that it gladly passes a toll road instead of a 20 minute longer drive toll free.Īnother issue I have noticed is that it seems not to accept long routing with Touring (car) or Motorcycle option, I have to select RV or Truck options for long routings, I have a few examples where I have test routes of 4000km (south of Brazil to north of Brazil) in order to check routing integrity. I can understand from my home town to nearest airport, a 64km run have two toll road options, a non-toll-road option turns out 3 times longer. Some due to lack of data (when I identify the spot creating the problem I go on JOSM to make an edit effort on the local), and some appear more strange to me.įor example, the routing option "Avoid Toll Roads" doesn't seem to be respected. I am noting several different issues on routing.
#Garmin basecamp 4.4.2 for mac
I am using latest BaseCamp stable release for Mac (4.4.3 I think), with different maps, mainly (I load Norway, Portugal and Brazil for my own interest, several different options for Brazil). If you need anything else to help fix it (assuming it can be fixed), let me know I hope I've described the problem clearly.

Use to the tool to calculate the estimated distance and features/landmarks to look out for/avoid.
#Garmin basecamp 4.4.2 how to
If thats not the case I'd love some more troubleshooting tips, suggestions on how to fix this issue. (I can't imagine garmin map format is opensource) My guess at this point it's a compatibility issue between garmin / openstreetmap. and finally, I've re-installed the maps and garmin basecamp.


%appdata%\garmin to see if I fudged the settings. I've read on the forum it might be, among other things, my route avoidance, or profile (hiking/biking,etc.) would route my hike onto public highways/roads / route in straight line rather than following path / looping around/double back on path. I've been using basecamp to route my hiking trips in basecamp and transfering to my dakota 10.Įver since 1st oct, the maps have been acting oddly, giving me bad/incorrect routing.Įg. I think I already know the answer but if this is something I've done I'm stumped.
