BaseCamp 4.4.2 Is Now Available

The maps are loaded into internal memory. The 'always match route...' is checked.

Strange.. can't reproduce. In general I am NOT a fan of match a route to the maps. It's often causing unwanted effects.

Two suggestions:
- make sure you recalculate the route in the correct mpversion within BC before you send it to the device. Leave the 'match' UNchecked!
- or: try exporting the route s a track. If so: disable auto-recalculation.

@ JM:
Thats over a tear ago! Do you have any info on what changed then and/or what is the reason for this advise? As said: I am very suprised and what I am reading here is the first I hear of it.

There are some route differences between what BaseCamp and the Zumo's produce. Mapsource as of now continues to be the application with the Zumo support.

There are some route differences between what BaseCamp and the Zumo's produce. Mapsource as of now continues to be the application with the Zumo support.

I have become increasingly depressed as I have followed this thread. After all the pressure to move from Mapsource to BC despite its shorcomings (e.g. original lack of postcode search - which still doesn't work properly) and the failure to carry out any development on Mapsource for a number of years, this unqualified statement that "Mapsource as of now continues to be the application with the Zumo support" is truly startling.

Which Zumo models does the statement apply to? All of them, or (as appeared to be the original position) just the 660 and earlier? In particular (and with no lack of concern intended or implied for owners of lower spec models) does it apply to the Zumo 590?

If it does apply to the 590 (and given how recently that model was introduced) why does the advertising and sales material for the 590 not make it clear that Mapsource is the preferred software package? If it had, it would undoubtedly have affected my decision whether to upgrade from a 660.

So that I, and I imagine other owners of these devices, can understand fully the nature and extent of the issues and incompatibilities, please could Garmin issue a clear statement setting out the full (technical) details of them, whether it is intended to remedy them, and in what timescale.

And if Garmin won't, please could it explain why not.

Mapsource as of now continues to be the application with the Zumo support.

Only Mapsource doesn't support properly City Navigator maps anymore. Not a nice arrangement, remembering that you pay premium price for zumo features.

Only Mapsource doesn't support properly City Navigator maps anymore.

Mapsource 6.16.3 (the latest) is known to crash with later City Navigator maps in certain areas.

MapSource Crashes Frequently with CNNANT2013.30 maps

I experienced a few crashes, days ago, while using MS 6.15.11 with CN NA NT 2015.20. They may or may not have been map related.

Frankly I'd expect MS 6.16.3 to become unusable with City Navigator maps at some point. Garmin is including more data in the maps as time goes by so unless MS is updated it'll eventually "blow up" constantly when encountering newer data.

Personally I'd prefer to see a maintenance release of MS to deal with map related issues. However I consider that unlikely.

It would seem that Garmin is leaving Zumo owners out to dry--at least for the time being.

We are specifically talking about the 660 and the 665 currently.

We continue to look into the issue but at the moment MapSource remains the application to support these devices.

It would seem that Garmin is leaving Zumo owners out to dry--at least for the time being.

This has been going on for a while and is not just a recent thing. The spontaneous recalc issue has been around about a year. People report issues with the Zumo 66x and Basecamp, Garmin asks for example files, people send them in, Garmin sits on it for a while, then nothing...... At least they are now telling it like it is, that they know there are issues between the Zum0 66x models and Basecamp. They are just keeping the details of these issues to themselves. If nobody complains, or if the issues are not wide spread I get the feeling nothing will get fixed. Then again, I'm not sure anything will be resolved even if a lot of people complain. :) I don't get the sense there is much momentum to support any of the Zumos other than the recently released model. Garmin has developed Basecamp down a path that won't support the Zumo 66x line unless they get back to updating the 66x firmware. I get the feeling that's not going to happen, thus the "use Mapsource" declaration.....

Two suggestions:
- make sure you recalculate the route in the correct mpversion within BC before you send it to the device. Leave the 'match' UNchecked!
- or: try exporting the route s a track. If so: disable auto-recalculation.

I always recalc to the current map version. What is your understanding of what the 'match' function actually does?? I was under the impression that the gps would just accept and store the route from Basecamp without a gps recalc if the map sets matched??

Wonderful. Started BC after an absence. Forced upgrade, as usual. Then the missing dll. After several iterations of uninstall and re-install, missing dll I finally downloaded the latest (according to d/l page needs Vista, but works on Win7 anyway?), it finally runs, but my data is not there. Ah yes, that's the db inb the Dropbox folder. Point it to it and - nothing. I end up with two db's called Default, both empty and find that BC has emptied my 4.2 db. Great job!

My data is back, thanks to Dropbox versioning. It's 1:30 in the morning and I can now start doing what I started it for in the first place.

Basecamp has never deleted any of my data. I suspect yours was there somewhere :)