BaseCamp 4.4.0.1 BETA is now available

Former Member
Former Member
BaseCamp 4.4.0.1 BETA is now available and can be downloaded here:

http://download.garmin.com/software/BaseCampforMac_4401Beta.dmg

This release supports OS 10.8 and newer.

Below is a list of changes. This is only a BETA release.

Improved BirdsEye user experience.
Added ability to activate BirdsEye subscriptions.
Added user configurable avoidance areas that can be set for each activity.
Added waypoint category option to Smart List criteria.
Added additional information to find results for Public Land Survey data.
Added new waypoint symbols.
Added 'Show in Finder' button to the custom waypoint symbol manager dialog.
Added waypoint categories column to detailed data list.
Fixed a bug with Trip Planner itinerary distance calculations.
Fixed a crash in Trip Planner when adding/deleting days from trip.
Fixed crash when sending trip to device from subfolder.
Fixed crash with auto naming route.
Fixed crash when renaming via point in Trip Planner.
Fixed crash when recalculating routes from right click.


Post here if you have questions.

The BETA is currently only for English users.

Before using this release, back up your data.

Please post any bugs you may find here. This release is to assist us in testing with a wider user base and wider set of devices. Bugs may be present, and any feedback is welcomed.
  • Former Member
    0 Former Member over 10 years ago
    OK, guess the "outage" lost the previous conversations - although most of it had to do with the corrupted install file.

    I have something that I'd like to get some feedback on. I posted over in the Win-BC but the Mac-BC folks should be discussion this as well. Given that Garmin has this propensity to continually change Symbol Sets from Device to Device, Brand to Barnd, I think it only fair that BaseCamp should be able to read and present for selection the attached Device's Symbol set when selecting a Waypoints symbol - in addition to a users Custom Symbol Set if said device supports Custom Symbols.
  • OK, guess the "outage" lost the previous conversations - although most of it had to do with the corrupted install file.

    I have something that I'd like to get some feedback on. I posted over in the Win-BC but the Mac-BC folks should be discussion this as well. Given that Garmin has this propensity to continually change Symbol Sets from Device to Device, Brand to Barnd, I think it only fair that BaseCamp should be able to read and present for selection the attached Device's Symbol set when selecting a Waypoints symbol - in addition to a users Custom Symbol Set if said device supports Custom Symbols.


    I'm all for this. And in the hopes that someone from the device side is listening, please give us a choice over that stupid heart (Zumo 590) for imported waypoints that don't fit the device's symbol parameters. Maybe a small innocuous dot that doesn't clutter up the screen so much.
  • Former Member
    0 Former Member over 10 years ago
    Yes,yes!

    not only that but allow me to select the symbols sets most useful to me.

    I want to be a heartless b*st**d!
  • Former Member
    0 Former Member over 10 years ago
    Please send your comments to the zumo team (I expect you have already).

    At least the BaseCamp team didn't change over to the "billboard-like" symbols being used on those devices. I made the above suggestion quite some time ago when BaseCamp first supported Custom Symbols (well for old discontinued devices anyway). It just seems logical that BaseCamp would be the managing entity when it comes to Symbols Sets.
  • Former Member
    0 Former Member over 10 years ago
    OK, guess the "outage" lost the previous conversations - although most of it had to do with the corrupted install file.

    I have something that I'd like to get some feedback on. I posted over in the Win-BC but the Mac-BC folks should be discussion this as well. Given that Garmin has this propensity to continually change Symbol Sets from Device to Device, Brand to Barnd, I think it only fair that BaseCamp should be able to read and present for selection the attached Device's Symbol set when selecting a Waypoints symbol - in addition to a users Custom Symbol Set if said device supports Custom Symbols.


    I would like that also.

    I did remove this beta on a french talking MAC, a lot of crashes when switching from map to map, to br precise when leaving with EU Garmin cycle.
    Going back to previous release was not so easy, changes made on the beta were not recognized by 4.3...
  • Former Member
    0 Former Member over 10 years ago
    BaseCamp v.4.4.0.1 has the same problem that v4.3.4 has in that it will not transfer a perfectly good CustomMap to the devices internal storage using the Send To... command: the transfer window has the option grayed out. If you try and Drag/Drop the CustomMap to internal storage, BC shows an error message saying that the device does not support Garmin CustomMaps.

    The device is a BMW Navigator V and it does support Garmin CustomMaps (I have used quite a few on the device). The only way to get BaseCamp to transfer a CustomMap to this device is to have BaseCamp send it to external storage (SD Card).
  • Former Member
    0 Former Member over 10 years ago
    Now why didn't I think of that...
    I even had GarminDevice.xml open working on another issue...
    That was the problem and I will report it to Product Support.
  • Former Member
    0 Former Member over 10 years ago
    View Device Information...

    I just found this in BaseCamp and when it works it will certainly help many new users... Will v4.4.x actually show what the Help files indicates; "A check mark appears next to the functions that are compatible with your device?"

    The current version does not show this information.



    Oh! One other point of note, when my Monterra is connected and I do cmd-I on the Device, BaseCamp appears to be reading the volume of my MacBook Pro rather than the storage on the Monterra. The storage on other Garmin devices is read properly.
  • The help is out of date. It used to show that, but the information was just too vague to help users.

    Since the Monterra is MTP, we have to mirror its storage onto your hard disk to read it on the Mac.
  • Former Member
    0 Former Member over 10 years ago
    Hmmm, does that mean v4.4 will not be showing the "capabilities of the Device"? This would be a very good thing for Users. Showing, for example: Internal Storage, SD Card Storage, Allowable number of Map Segments & Segments currently installed.

    As for the Monterra Storage, maybe you could look at MapInstall and how it is reading the Monterra's available storage - it is correct.