BaseCamp 3.2.2 is available

Former Member
Former Member
BaseCamp 3.2.2 has been released, it is available for download at http://www8.garmin.com/support/download_details.jsp?id=4435.

Currently there is a problem with the Auto-Update, so please use the download link for now.

3.2.2 is a Maintenance Release, that means it is mostly bug-fixes, not new features.

This is a list of changes:

  • Fixed an issue with migrating waypoints with thumbnails from previous versions of BaseCamp to 3.2.1. This issue could have corrupted the database.
  • Fixed an issue with tracks that had been duplicated becoming corrupted.
  • Added a prompt to notify the user when data loss might have occurred.
  • Added a 'restore from previous version' menu item.
  • Added support for exporting of fitness data (heart rate and cadence) in tracks.
  • Changed to attempt to fix the paths in Garmin Custom Maps (KML ground overlay) files at start-up without notifying the user that there were problems with the file.
  • Changed the message displayed at start-up when the current video mode/card doesn't support 3D.
  • Improved initial download size estimates for some BirdsEye products.
  • Fixed some issues with undo/redo.
  • Fixed several issues related to application shutdown.
  • Fixed an issue with not recognizing Garmin mode USB device (such as the GPSMap 60) arrival and removal.
  • Fixed several issues related to aborting transfers to Garmin mode USB devices.
  • Fixed some issues related to ejecting mass storage devices.
  • Fixed some issues with changing folder selection while using the BirdsEye wizard.
  • Fixed an issue with reading geotagged photos from many smartphones.
  • Former Member
    0 Former Member over 13 years ago
    Please, please, please do! This would be fantastic!
    ...
    At present, in order to declutter the screen and view only the elements I am presently interested in, I must create several lists in My Collection as follows:

    ...


    We will see if there is something we can do about filters in the map view.

    Just as a current work-around: have you considered using the data view (Ctrl-Tab) and then making the map larger? That would allow using the filters.
  • Former Member
    0 Former Member over 13 years ago
    Just as a current work-around: have you considered using the data view (Ctrl-Tab) and then making the map larger? That would allow using the filters.


    Yes, but that doesn't seem to work.

    I just tried, but when I clicked on "show waypoints", the data list changes but the map does not - it still shows everything in the currently selected list.
  • Former Member
    0 Former Member over 13 years ago
    You are correct, we don't hide that data. I don't believe this is how it should be.

    I'll file it as a bug and see if we can get that working.
  • Former Member
    0 Former Member over 13 years ago
    Elevation Data

    If I create a route in BaseCamp using a topo map it shows elevation data in BaseCamp but if I send the route to the Edge 800 from BaseCamp and load it up in Courses... nothing on the Edge. If I've ridden the route and create a course from it then there's full elevation data.

    However - if I load a route onto the Edge from a 3rd Party Website then I get the full elevation profile.

    I therefore surmise the way that BaseCamp sends routes to the Edge isn't the same as other websites??

    What I'd like to do is draw a route in BaseCamp, send it to the Edge and when I'm riding have the upcoming hills display on the course I'm riding...
  • Former Member
    0 Former Member over 13 years ago
    We'll look into this.
  • One fix was:

    Improved initial download size estimates for some BirdsEye products.

    Using 3.2.2, I selected BirdsEye imagery that estimated near the 230MB maximum but the actual downloaded imagery was 89MB.

    Dave
  • Former Member
    0 Former Member over 13 years ago
    I exported my entire collection to a GDB file. Then I immediately imported the GDB file so there were no changes in Basecamp's collection in the meantime.

    1. As I expected, the imported file showed up as a new list (list name == "My Collection copy" was assigned automatically from the GDB filename).

    2. As I expected, the new list was identical to the original collection.

    3. Unexpected: there were no duplicates listed in My Collection. There was only one of everything showing


    After thinking about this a bit more, I have to flip-flop here.

    This is working as intended, and within BaseCamp's data paradigm. We will not duplicate things unless you ask us to, or we determine that an item with the same name is indeed a different item.

    I was stuck in the MapSource mind set when I first answered, probably because I read too much of your feedback. ;)

    Importing data is not like opening a file in MapSource that you get a blank slate, it's more like receiving data from a device in MapSource, where you will ignore stuff that you already have, create data you didn't have and rename data that has the same name, but appears to be different.

    So the behavior when you import a gpx (or gdb) file in MapSource is similar to what you would see in MapSource if you would receive from a device that has a current.gpx file with the same data that you already have in MapSource.
  • Former Member
    0 Former Member over 13 years ago
    Hi Falagar,

    Can you confirm that you are actually comparing the contents of each named object in the imported file against the one with a matching name in the collection to be certain they are identical?

    What do you do if you have objects with the same name where the object being imported is actually different in content to the one in the collection? E.g. do you rename the imported object; pop an error dialog and ask the user to select an appropriate action; etc.??

    ...ken...
  • Former Member
    0 Former Member over 13 years ago
    We do check the content. If the content is different, but the name is the same (let's say the name is 'My cool POI'), they will be imported as 'My cool POI 001' or something very close to that.

    Currently there is no message box warning the user about this.
  • Former Member
    0 Former Member over 13 years ago
    No worries about a warning. I just want to be confident that none of the content of the import is going to be ignored simply because it has an identical name to something that's already in the collection. A notification is a nice-to-have if you ever get a round toit. ;)

    ...ken...