Issues with BaseCamp 4.1.0

Former Member
Former Member
There are some serious device connection issues with BaseCamp 4.1.0. That is why we pulled it from the auto-update servers. You can still download it from http://www8.garmin.com/support/download_details.jsp?id=4435 if you want to.

We are working on fixing the most pressing issues. They will be addressed in BaseCamp 4.1.1.

I'll outline the 2 most common issues and how to work around them in case you already installed 4.1.0:

1. You have a device connected and start BaseCamp, or you have BaseCamp running and connect a device -> BaseCamp stops responding.
Fix: This is most likely caused by a gpi file on your GPS. Look for 006D135900.gpi in the .System or POI folder. Rename the file to something else (006D135900.bak for example). Restart BaseCamp.

2. BaseCamp 4.1 does not recognize your Nuvi, but earlier versions of BaseCamp did.
Fix: Switching the device to Mass Storage mode might fix this. Disconnect the device. Turn it on. Go to the Odometer screen (View Map, tap speed). Press your finger on the odometer for around 10 seconds. A debug screen should appear. Go to MTP settings. Select Mass Storage mode. Connect the device to BaseCamp.

I apologize for all the trouble. This is something we should have caught before releasing, but it slipped through somehow.
  • Former Member
    0 Former Member
    We seem to have a situation where Basecamp is crashing when devices are attached, the Find function isn't very functional, there is no post code search facility (most people in the UK will use post codes to find addresses) and there are various other 'niggles' with the software that affect the way the software operates. Bottom line is the basic functionality, from an automotive perspective, is not working well (I was going to leave it at 'not working' but thought I'd add the 'well' as an appeasement ;)).

    I'm sure the Basecamp aficionados will be all over me like a rash for this suggestion but why doesn't someone whisper in the ear of TPTB at Garmin and suggest they get a version of the maps out that does work properly with Mapsource? If they did that, those of us who want to go hiking, GeoCaching, Clouding and Adventuring could continue to use Basecamp. Those of us who simply want to find places to put into routes which can then be planned, calculated and downloaded to our automotive devices could continue to use Mapsource for a while. I'm sure things would then be a lot quieter here and in other places where Basecamp is being discussed, there will be less pressure on the developers to get it working RIGHT NOW (which will allow time for proper testing) and we can all come back together again when Basecamp 4.2 is released; I'm expecting great things of v4.2... I realise there are cost implications associated with doing this, but how much cost is associated with losing disillusioned customers?

    Kevin
  • You're confused I think :confused:

    Mapsource is discontinued as it doesn't support fully the newer Garmin devices, it has nothing to do with map support. Mapsource is still available and can be used with pretty much any Garmin device, though there will be limitations. I run Mapsource as well as Basecamp, although only really for postcode lookup, which as you rightly say isn't yet available in BC, although it's coming so we're told :)
  • Former Member
    0 Former Member
    Really? There's obviously a lot of it about. Try Googling 'Mapsource crash 2013.3' for a small selection of the reports then come back and tell me how confused I am.

    Do you really think I'd be struggling with Basecamp in its current form if I could get Mapsource to work reliably with the latest maps?

    Kevin
  • I was referring to your confusion over maps, and thinking that Garmin simply have to release a special map so you can use Mapsource. All my Garmin maps work with Mapsource, the issue, as I've said, is that Mapsource has its limitations with the newer Garmin GPS, but should you want to most can be made to work, possibly in a limited fashion, with Mapsource. Or you could practise a bit more with Basecamp so you know fully how it works. Up to you really.
  • Former Member
    0 Former Member
    We are definitely having some communication issues here so I'll try one more time then give up. I have no confusion. The 2013.3 maps for both EU and NA can cause Mapsource to crash; it is nothing to do with any GPS hardware and everything to do with the latest release of the maps. In identical circumstances the 2013.2 and earlier maps do not cause the crash, 2013.3 does. Using Google with the search term I suggested would have shown you others reporting the same issue.

    I think there must be hidden bits in my posts that only you can see as I haven't suggested a 'special map' for Mapsource is required. I said, and I'll quote what I said just for you "...get a version of the maps out that does work properly with Mapsource...".

    I couldn't think of anything polite to say about your last two patronising sentences so I won't say anything.
  • I think there must be hidden bits in my posts that only you can see as I haven't suggested a 'special map' for Mapsource is required. I said, and I'll quote what I said just for you "...get a version of the maps out that does work properly with Mapsource...".


    Well that would be a special map, as Garmin maps are normally issued about once every 3 months (4 a year). In the past though they have released additional/special/extra versions (call it what you like) if there has been a proven issue, but as many users seem to have no problems with 2013.30 with Mapsource (myself included) and bearing in mind Mapsource is no longer supported I suspect no one at Garmin feels this is problem they need to deal with. But if you hang on a new release is due anyway in the next few weeks if they stick to their timescale :)

    Didn't mean to be patronising but like everything in life you have a choice, and in this case it's whether you can learn how to use Basecamp so you can do what you want or stick with Mapsource.
  • When these errors occur and BaseCamp is pulled, it would be nice to have some way to rollback to the previous version. This is the second time it has happened, so it seems likely in future releases as well. I usually hold off on updates, but this one kept popping up so much that it timed itself just right to steal an enter key push in another area and update itself. :) Very frustrating.


    I agree. Worth keeping a copy of previous software just in case :)

    But it is available here should you wish:

    http://www8.garmin.com/software/BaseCamp_405.exe
  • Former Member
    0 Former Member
    I usually hold off on updates, but this one kept popping up so much that it timed itself just right to steal an enter key push in another area and update itself. :) Very frustrating.


    Same here! :mad: See my post:https://forums.garmin.com/showthread.php?33957-Don-t-want-4-1-0-how-not-to-upgrade
  • Well that would be a special map, as Garmin maps are normally issued about once every 3 months (4 a year). In the past though they have released additional/special/extra versions (call it what you like) if there has been a proven issue, but as many users seem to have no problems with 2013.30 with Mapsource (myself included) and bearing in mind Mapsource is no longer supported I suspect no one at Garmin feels this is problem they need to deal with. But if you hang on a new release is due anyway in the next few weeks if they stick to their timescale :)

    Didn't mean to be patronising but like everything in life you have a choice, and in this case it's whether you can learn how to use Basecamp so you can do what you want or stick with Mapsource.


    The problem is losing support for a product that is 3 years since it's last update and still works better than the one they are currently developing. There is a LARGE contingent that is tired of the frustration of Basecramp and were doing exactly as recommended: Using Mapsource. We also have units that are Mapsource compatible, such as my z660 and my GPSMAP276c. How they (Garmin) have betrayed us is by hooking us into buying lifetime updates, and then including maps that only the inferior Basecramp can use. So my choice is to use my reliable and intuitive Mapsource while employing ever dated 2013.2 maps, or double my blood pressure medicine and suffer through using Basecramp in order to use up-to-date maps, which I paid for.

    If you're keeping score here, some of us are technically out of luck via Garmin. We load our new mapset, which renders Mapsource inoperable, and we updated Basecramp automatically, which renders that (more) useless because I have a camera file. Sounds like progress to me.:mad:
  • Former Member
    0 Former Member
    <snip> If you're keeping score here, some of us are technically out of luck via Garmin. We load our new mapset, which renders Mapsource inoperable, and we updated Basecramp automatically, which renders that (more) useless because I have a camera file. Sounds like progress to me.:mad:


    You're confused. It's obvious to a blind baboon that there is no problem between Mapsource and any Garmin map set because a comprehensive test looking for a few post codes proved it worked perfectly. The people you see complaining of Mapsource crashes with 2013.3 in other forums you frequent or when you use Google are obviously similarly deluded; [waves hand in front of your face] everything is fine, this is not the problem you are looking for. If anything is making Mapsource crash it's one of these newer GPS units even if you don't own such a device.

    Your basic problem is you just don't understand how to use Basecamp because if you did you'd realise that not only does it do everything Mapsource does and more it does it better. Oh, and STOP PRESS: Find works as well.

    I'm sitting here looking puzzled because I don't know how I was able to type all that before SUSSAMB got here and said the same thing. Still, it saves him or her having to do it. :cool:

    Kevin