BaseCamp 4.3.5 is Now Available

Many thanks

Have tried that, and it's still just crashing

Wow! Really? That's the answer? You stop all support for Mapsource, tell us to start using Basecamp. So I bite the bullet and learn Bascamp. Then you introduce issues that didn't exist a year and a half ago with earlier version of Basecamp and my 660, then tell us to go back to Mapsource? Amazing support!

What version of Basecamp was this issue introduced? I'd like to know so I don't have to learn by trial and error on a multi-thousand mile trip....

I am not using the 660, I have the 350LM. My issue isn't with Base Camp nor MapSource. It's when the zumo recalculates the route I painstakingly created in either desktop tool. When the zumo does recalculate, it doesn't have the same granularity basecamp or mapsource does and either prevents ALL highways or allows ALL highways. I just want to avoid interstates, which can't be done on the zumo.

I do the same thing. I create my routes, upload them to the gps and just want the unit to follow it. Even with the 660 set with 'recalculate' = no it spontaneously recalcs multiple times during the execution of a route. Come on Garmin, the 660 isn't that old and it worked fine in the past. Are you telling me Basecamp can't simply create a route and send it to my unit without screwing it up? What are my options? Pay $800+ for a 590 to replace a 660 which works fine when the firmware and software provided doesn't screw things up?? You're still selling the 660 on your site.....

Can you guys reload your original route? I know it's sub-optimal but I remember doing that on an Alps trip. If we got off course and the unit recalc'd even though it was told not to, we'd just pull over and reload the original route. If we were a little off the route we'd just zoom out till we saw where we were supposed to be and head that way. There's no way you should have to do that but may be a temporary (or permanent) work around.

Many users happily use their zumo with BaseCamp and it works just fine.
MapSource Download

So <some> users don't experience these issues, or some users are happy with spontaneous recalculations even thought they have disabled the 'auto-recalc' option?

I'm still waiting to hear why Garmin refuses to fix this issue, which wasn't a problem with earlier versions of BaseCamp, even though "We take compatibility between BaseCamp and all Garmin devices very seriously"?

Any pointers on where to look next? Are there processor restrictions with this version?

Thanks for the feedback and the debug data. We are looking into it. I have not seen this specifically before but will try to recreate. Thanks for the feedback.

Can you guys reload your original route? I know it's sub-optimal but I remember doing that on an Alps trip. If we got off course and the unit recalc'd even though it was told not to, we'd just pull over and reload the original route. If we were a little off the route we'd just zoom out till we saw where we were supposed to be and head that way. There's no way you should have to do that but may be a temporary (or permanent) work around.

I've been doing that for over a year now. On one of my day routes a couple of weeks ago I did it about 15 times. :) What is the response from Garmin after being strung along for a year+. "Your 660 isn't really support by BaseCamp. Please use MapSource, (the program we no longer support)."

I've been doing that for over a year now. On one of my day routes a couple of weeks ago I did it about 15 times. :) What is the response from Garmin after being strung along for a year+. "Your 660 isn't really support by BaseCamp. Please use MapSource, (the program we no longer support)."

Garmin, any update on this issue? Is it Basecamp or the firmware in the unit? Will there ever be a fix? As requested I convert all of my Mapsource files to Basecamp. Every trip since 2001. Is moving everything back into Mapsource really my only option?

Garmin, any update on this issue? Is it Basecamp or the firmware in the unit? Will there ever be a fix? As requested I convert all of my Mapsource files to Basecamp. Every trip since 2001. Is moving everything back into Mapsource really my only option?

You will get much better answers on http://www.zumoforums.com/.

You will get much better answers on http://www.zumoforums.com/.

Thanks for the tip! I'll go have a look there.

Still, it would be nice to hear from Garmin why they told me to switch from Mapsource to Basecamp and are now telling me to switch back to Mapsource. It took me quite a while to convert 15 years worth of route data to Basecamp and to get up to speed on using Basecamp. The Zumo 660 was working fine until about a year ago. That's when it would randomly and spontaneously recalculate routes mid-trip even if the auto-recalculate option was turned off. You'd think they would be able to update Basecamp or the 660 firmware to a point it would remain compatible with Basecamp. I'd even be happy if they could tell me when the incompatibilty was introduced so I could revert back to a version of Basecamp which works with my unit.

I suppose I could figure it out myself by loading previous version of Basecamp, load up the 660, then go on a 300 mile ride and see if it happens. The problem is it happens hundreds of miles into a route, and not on every route!? Even a little assistance from Garmin would be helpful. The frustrating thing is I report an issue, get the standard "thanks we'll look into it', then nothing for months, then a year later, "you need to use Mapsource". In the mean time Garmin is releasing newer versions of Basecamp which typically break more things than they fix or add.

I don't think I've ever dealt with a company with a software development team that has had this many issues. I get the impression the current development team doesn't has a very strong sense of planning in their development process. Reminds me of the old Windows 95/Windows NT days at Microsoft. They had two separate development teams. The NT team was slower and methodical, but what they produced was pretty stable. The Windows 95 "cowboy coders" would pump out the consumer versions of Windows right and left, but man was it a rough ride!