Related

BaseCamp 4.4.0.1 BETA is now available

Former Member
Former Member over 10 years ago
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
    Hmmm, does that mean v4.4 will not be showing the "capabilities of the Device"?


    I don't think any version of BaseCamp shows device capabilities. Most of that stuff isn't even in the GarminDevice.xml file (which BC reads) so...
  • Former Member
    0 Former Member over 10 years ago
    There didn't use to be a GarminDevice.xml file either so...my point has been, since that device description file was created, make use of it in BaseCamp to provide USERs with pertinent information about the device. Here's the chance to do just that. BaseCamp offers the Device Teams the ability to "describe the device capabilities" and BaseCamp shows the USER. This is so easy to do it make me wonder why it's taking so long to accomplish. and if BaseCamp makes it possible it won't take long for USERs to let the Device Teams know they need to provide the info.
  • Former Member
    0 Former Member over 10 years ago
    There didn't use to be a GarminDevice.xml file either so...


    True. Garmin seems to like inventing new mechanisms which are incompatible with the old just to make things "interesting".

    Additional "device capabilities" data could simply be added to the GarminDevice.xml file. Newer software that understands that data could use it while older software that does not could ignore it. No need for another file.
  • Former Member
    0 Former Member over 10 years ago
    I just discovered another file on my NAV5 that BaseCamp might be using for this "capabilities" feature. It's an HTML coded file that seems to list the Major Features of the device but it doesn't give any of the pertinent data that we've been discussing: # of Tracks, # of Track Points, # of Routes, # of Route Via Points, # of Route Shaping Points, etc.
  • Former Member
    0 Former Member over 10 years ago
    v4.4.0.1 Database...

    Back to my cryptic Database issue...

    Yes, I reinstalled the Beta. Can't resist a good problem. I have a single Database, let's call it Dan'sDB, and if I load it into v4.3.x, I see the current data that I've been working with and the current Folder/List configuration. But, if I make a copy of Dan'sDB and open it in v4.4.0.1, what I see is a back-level version of Dan'sDB. No matter what I do to the current DB if I make a copy and open it in the Beta, I only see the back-level configuration.

    I didn't know that BC was keeping "Version's" but V4.4.x.x is only reading my back-level version and I know it is not getting this from another DB on my computer other than Dan'sDB.

    Since there hasn't been any Dev Team input on this issue I can only surmise that they have a problem and are working hard to fix it.:cool:

    It would be nice to hear from them though...