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
    I was reading other threads that indicatd that when upgrading to 4.0.2 that it now will delete the maps on your computer. I can't afford this to happen as we are 2700 miles away from our home base and need my maps to plot our routes back home. We are running on air cards as we travel. If this is true it is a paramont problem.

    Is there anyone else having this problem, since Falgar has indicated the new update is good to go. Does this include the fix to the registry for the maps??

    BC
  • 0
    Yes, the update is fixed. Note that the problem was only if you updated from within Basecamp, if you downlaod directly from the Garmin website there was no problem.
  • Former Member
    0 Former Member
    Yes, the update is fixed. Note that the problem was only if you updated from within Basecamp, if you downlaod directly from the Garmin website there was no problem.


    Also note that it did not delete the maps, only the registry entries. And it's only some third-party maps and really old Garmin maps that use registry entries anyway. If you are using relatively current City Navigator maps it would not be a problem.

    ...ken...
  • 0
    I came to report two bugs with 4.0.1, saw there was a new 4.0.2, and installed that to see if it fixed the bug. In the meantime, I realized that one was not a bug, but is instead a 'bug'.

    Bug - in Print Setup > Page Setup I cannot modify the Left and Bottom margin. They appear editable but act like labels. And once you are in them, you can't exit and must use the 'X' to kill the dialog.

    'Bug' - in Activity Profile > Map Display Feature, sometimes clearing the parent's checkbox will not clear the childrens'. I was creating a map, and kept seeing Airports. I found I had to drill down to Air Transportation and clear it. Weirdly, sometimes unchecking a parent's will actually clear the children.

    If you fix this 'bug', may I suggest a related usability feature? If a child is checked, a parent show a gray box to show that some children are still active. So, if Air Transportation is checked, then Transportation should show a gray box (a check means all children are checked) and so would Points. This is a common Windows usability feature that really does provide increased usability.

    Thanks,

    Dave

    PS - I use Windows 7 solely for Basecamp. Otherwise, I use Linux. I'd prefer to not have to use Windows. ;-)
  • Former Member
    0 Former Member
    To Falagar, I have installed the 4.0.2 version of basecamp on my win 7 laptop. I am not able to perform live tracking with basestation on a birdseye image on my laptop. Is this feature possible with 4.0.2. If not available yet, then I believe I can acomplish this using a custom map with the aerial image in the map. I would then use the custom map instead of the standard global map. Any help would be appreciated. Hopefully will have this feature added to next maintenance release.
  • Former Member
    0 Former Member
    BaseCamp does read fit based activities/histories from my Edge 800, it does not read courses. Which device do you own?


    I wrote: "import fit-files (not from device)"
    It's a joke to load old Fit-files into my Edge only for importing them into BC!
    BC is able to handle fit, but why the hell only from device?
  • Former Member
    0 Former Member
    Pois are displayed at a much higher zoom level compared with v.3.3 and Mapsource.

    In Normal detail level, at 50m (200m in BC 3.3, 300m in MS).

    Is this intended, and why?

    I can imagine in some very dense populated areas, this will prevent cluttering of the map, but in sparsely populated areas this will be unwanted.

    Is it not a better idea to choose the setting of the zoomlevels yourself, just like on the GPS devices?
  • Former Member
    0 Former Member
    I encourage the BaseCamp development team to implement a hovering waypoint selection tool while rubberbanding. Motorcycle users are missing an important function to use BC for routing. Guessing where the mouse cursor is while inserting a via point and looking for an intersection is quite frustrating. The Won't Announce/Won't Flag is not effective on the Zumo unless the correct type of point is selected. This is the major reason many of us still route with MapSource.
  • 0
    I encourage the BaseCamp development team to implement a hovering waypoint selection tool while rubberbanding. Motorcycle users are missing an important function to use BC for routing. Guessing where the mouse cursor is while inserting a via point and looking for an intersection is quite frustrating. The Won't Announce/Won't Flag is not effective on the Zumo unless the correct type of point is selected. This is the major reason many of us still route with MapSource.


    Dave, could you elaborate on what type of points will avoid announcement on the Zumo when a route is prepared in BC? I believe that announcements can not be avoided on the Montana?
  • Former Member
    0 Former Member
    Dave, could you elaborate on what type of points will avoid announcement on the Zumo when a route is prepared in BC? I believe that announcements can not be avoided on the Montana?


    Intersections ("Street1 & Street2")
    addresses that are not Waypoints and not POIs.
    The Zumo models do this. I'm not sure other products do.