Related

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://garmindeveloper.com/apps/BC/BaseCampBeta_4.4.0.1.exe

This release does not support XP.

You do not have to uninstall BaseCamp 4.3.5 and it will not overwrite that installation. The BETA and an official release of BaseCamp will live side-by-side but must be used separately.

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

• Added notification that eligible devices can install maps on the desktop using Garmin Express
• Added ability to create and manage areas to avoid while routing
• Added properties (and shading) for public land survey types
• Added progress bar in the data list for downloading BirdsEye
• Added progress bar on the BirdsEye wizard for downloading BirdsEye
• Added way to activate BirdsEye subscriptions within BaseCamp
• Added ability to go back on the BirdsEye wizard dialog and select a new area (subscription only)
• Added option to disable imagery display in the map views
• Added some additional waypoint symbols to be more consistent with newer nuvi and zumo devices
• Added Duplicate List and Contents menu option
• Added a column in the data list for waypoint category name
• Added map context menu option to search for the most recently used search category
• Improved response time when populating the list of Birdseye providers
• Changed how nearest area results are displayed on the map when hovering
• Changed to ask if the waypoint should be shared between routes when splitting a route
• Changed to preserve the settings in the print page settings dialog
• Fixed problem with marine heights being displayed incorrectly
• Fixed issues when reading GPX files that contain invalid times
• Fixed odd rendering on newer City Navigator maps
• Fixed issues with inconsistent track stats

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.

Again, thank you for all who participate.
  • Former Member
    0 Former Member
    The change was made to be in line with the devices.


    Ok. So users with older devices will see a different symbol in BC 4.4 and their unit(s). Users with new devices and older versions of BC (or MapSource) are still SOL. Users with older devices and who use pre 4.4 BC (or MapSource) are ok.

    Just so everyone understands.
  • Former Member
    0 Former Member
    Repost due to site issue.

    https://forums.garmin.com/showthread.php?122607-Announcement-Site-Outage

    Here are the 12 new symbols that I see. The waypoint names correspond to the symbol names used in GPX files.



    Note that the blue cross symbol (Hospital, Euro) was used for "Medical Facility" in previous versions of BC (and MapSource). The new blue H symbol now corresponds to "Medical Facility". That seems like a bug to me. Changing a long standing symbol (in devices and computer software) is unwise IMO.



    Seems to me that incorporating International Symbols into "older" devices in this way is a good thing. In the case of "Hospitals", if someone shares "Hospital" POI/waypoints with me for locations outside of the North America, I still get my "Cross" displayed on my "older" device. If Garmin didn't do it this way I'd get a Heart or "Favorite" symbol or some other default Symbol since my "older" device didn't have an "H" Symbol to represent Hospital.
  • Former Member
    0 Former Member
    In this case no matter what was done would be wrong for someone. Garmin chose to make it correct for owners of newer nuvi's and Zumo's (blue cross = "Hospital, Euro") rather than for everyone else. That's ok as long as everyone knows. I'm sure someone will complain at some point...
  • Former Member
    0 Former Member
    If I send a Hospital Waypoint to my Monterra, which has the "H" symbol for Hospital, and I use the "Cross" in BaseCamp what I get on the Monterra is an "H" Symbol for the waypoint - no matter what part of the world the waypoint is in. Seems like that's the way it ought to work since the Device Teams most likely aren't going to all update their Symbol sets to reflect International Symbols (to bad).

    So, as I have eluded to, I think Garmin ought to update ALL device Symbol sets to a set of International Symbols and then the rest of the Symbols fall in the "legacy" list.
  • Former Member
    0 Former Member
    I doubt Garmin is going to release new firmware for all their devices...

    In my case all my units have the "blue cross" symbol which prior to BC 4.4 was "Medical Facility". If I use the blue cross in BC 4.4 ("Hospital, Euro") and transfer that my units will show whatever default symbol (e.g. blue flag) they show for unsupported symbols. None of my units support a blue H.

    Of course if you have a newer device and use BC 4.4 everything is honky dory :)

    Personally I don't care much since I primarily use MapSource.
  • Former Member
    0 Former Member
    Neither do I expect Garmin to change the software on all current devices to have some kind of Standard Symbol Set. But, given that Garmin does have 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 in addition to ones Custom Symbol Set if said device supports Custom Symbols.
  • Former Member
    0 Former Member
    I would. Can you send them to [email][email protected][/email]


    I sent the requested files on Thursday 21 August and, although I have received an automated acknowledgment, as with the files I supplied in respect of 4.3.5, I have heard nothing further.

    Particularly as I recognize that this release is a Beta, I emphasize that I am not expecting an immediate (perhaps any) solution but, as the other reports of problems are acknowledged here, it would be nice to know: (a) if the problems I am encountering are recognised) (b) whether it is anticipated that there will be a solution, either in another Beta or the final release; and (c) optimistically, some idea of a timescale.

    TIA
  • Former Member
    0 Former Member
    I have received your files and we have been reviewing them. I apologize for not posting sooner. We are looking into your issue.
  • Former Member
    0 Former Member
    I have received your files and we have been reviewing them. I apologize for not posting sooner. We are looking into your issue.


    Thank you.

    Do let me know if you require further information.
  • 0
    Thank you.

    Do let me know if you require further information.


    I've had the install problem you described on i7 iMac basecamp 8.1 pro windows installation. Nothing else installed except ms office. I uninstalled basecamp beta, then installed the previous version which works well. I then reinstalled the beta version and it works!
    No idea what that means, maybe it can help?