Related

BaseCamp 4.0.2 is available

Former Member
Former Member
BaseCamp 4.0.2 is a maintenance release. It addresses the most common issues with the 4.0.1 release.

BaseCamp should now properly remember its state from the last run and not resize every time. Maps should be read properly from devices again. Changing the detail level should not cause a crash anymore.

You can download it directly at http://www8.garmin.com/software/BaseCamp_402.exe or use the internal update within BaseCamp.

The full list of changes:

Added smoothing of speed and heart rate graphs.
Improved Track Join inside of an Adventure
Change to not show the "Filter Results" option in the find results if there are no results to filter.
Fixed layout not being remembered properly between application runs.
Fixed layout being different after exiting from Adventure playback.
Fixed an issue with the "References" tab page not being properly updated when changing selection.
Fixed an issue with route shaping point info being lost when erasing points from a route.
Fixed an issue with track color being changed when tracks are filtered.
Fixed an issue with not updating the summary in the route dialog when points are unselected.
Fixed some issues with login and re-login for MyGarmin services
Fixed doing an undo while drawing a route ending the route. Now only the last via point is removed.
Fixed an issue when importing photos with invalid time EXIF data.
Fixed text messages from Basestation devices being repeatedly notified
Fixed an issue with route join
Fixed an issue with the route divide tool
Fixed an issue with duplicating routes
Fixed an issue with adding waypoints into routes in an Adventure
Fixed an issue with line breaks being repeatedly added to GPX files
Fixed an issue with click & drag on the map hiding properties dialog
Fixed an issue with importing KML or KMZ files that had downloadable content.
Fixed an issue with creating a waypoint via the map context menu when a list folder is selected
Fixed an issue where the waypoint ordering was not updated when changing the main track in an Adventure
Fixed an issue when clicking on the 'X' to remove a tag from the References tab page.
Fixed an issue when changing map detail level before putting focus into the map views.
Fixed an issue where the creation date of a photo waypoint didn't match the creation date of the photo's EXIF data
Fixed an issue with waypoints sometimes not being shown on the map
Fixed an issue with some card products not being recognized. Unfortunately this requires re-indexing all card products.
Fixed various other customer reported issues
  • 0
    The Won't Announce/Won't Flag is not effective on the Zumo unless the correct type of point is selected.

    The Won't Announce/Won't Flag is supported by the zumo 340/350; other devices (including the older zumo's) don't.
  • Former Member
    0 Former Member
    I have been trying to download BaseCamp 4.0.2 for the first time from the Garmin site and it got half way through the downlaod when I got the message "file corrupt". I have tried looking to see if there is anything to uninstall before trying again but have found no intalled files. When I try and re-download, I immediately get the corrupt message again. Any ideas? I am getting desperate...
  • 0
    When sending a (or multiple) route(s) to the Zumo660, all routes on the internal memory of the Zumo + the newly sent are stored in the temp.gpx file. When you have 8+ files on the Zumo, the newly added routes never get loaded when the Zumo reboots...
  • Former Member
    0 Former Member
    When sending a (or multiple) route(s) to the Zumo660, all routes on the internal memory of the Zumo + the newly sent are stored in the temp.gpx file. When you have 8+ files on the Zumo, the newly added routes never get loaded when the Zumo reboots...


    The zumo 660 can only import 5 to 7 routes in one time, depending on the complexity of the routes.

    But there is always the manual import. Extra - My Data (or something like that) - Import - Routes .... and there you can select the routes which you want to import additionally.
  • Former Member
    0 Former Member
    DAVEHATHAWAY "I came to report two bugs... "

    - I sent you a private message to your earlier post. Want to make sure I understand the issues you're seeing. When you get a chance if you could respond to it I'd appreciate it.
    Thanks!
    MQ
  • Former Member
    0 Former Member
    The Won't Announce/Won't Flag is supported by the zumo 340/350; other devices (including the older zumo's) don't.


    On both my Zumo 550 and Zumo 665, when I put a shaping point (a via point on an intersection that gets the label of "Street1 and Street2") on a route it shows on the route map of both Zumos as not flagged.
  • 0
    Placing via points on intersections is the usual trick to avoid flags on the (older) zumo's; it works with MapSource too. I was referring to the new option in BaseCamp, where you can explicitly set other via points (that normally would cause a flag in de zumo) not to be announced. That option works only with the zumo 350.
  • Former Member
    0 Former Member
    On both my Zumo 550 and Zumo 665, when I put a shaping point (a via point on an intersection that gets the label of "Street1 and Street2") on a route it shows on the route map of both Zumos as not flagged.


    Yes, we added that support as best as we could for the 550 and 665. But outside of intersections and addresses, 'do not announce' flag only work on the 340/350. I've actually only tested on a 350, but I assume the 340 works as well.

    Edit: Javawa pretty much said that already, didn't see his response.
  • 0
    ... But outside of intersections and addresses ...

    That's not correct; addresses (and POIs) are the cause of the flags on a zumo 550/660. When you put a via point on a stretch of road without an address, the via point won't be announced on the older zumo's.
  • Former Member
    0 Former Member
    That's not correct; addresses (and POIs) are the cause of the flags on a zumo 550/660. When you put a via point on a stretch of road without an address, the via point won't be announced on the older zumo's.


    Just to make sure we are not talking about different things:

    I am talking about the 'Do not announce' flag you can set in BaseCamp. That flag is honored regardless where you set in the Zumo 340/350. In the Zumo 550/660 it is only honored if the waypoint is on an intersection or address. At least that is my understanding based on our testing back when we implemented the feature.

    I am not sure about the behavior when you set a waypoint on a stretch of road without an address.