Related

BaseCamp 4.0.0.5 is released

Former Member
Former Member over 12 years ago
We are releasing another public Beta of 4.0. This release contains a bunch of bug fixes and a few added features.

You should be able to update from within 4.0.0.4. Or download it directly at http://developer.garmin.com/apps/BC/BaseCamp_4.0.0.0_Beta.exe.

If you had trouble updating from 4.0.0.4 to 4.0.0.5 please use the download link, don't update from within BaseCamp.

Please give it a spin, report any errors and leave feedback here or via feedback option within BaseCamp. Thanks!

The What is new in BaseCamp 4.0? Thread still applies. Adventures are still the focus of this release.

We disabled the 'Unlisted Data' list for now till we get it working correctly.

A long-standing issue with shopping card POIs showing up on the map even if users turned of the display of points has been fixed.

You can now import into folders and lists (before we would always create a new list in My Collection).


Full change list:

Added ability to import into folders and lists (and not always import into My Collection).
Added ability to archive/un-archive adventures.
Added header for the folder data list.
Added easy way to display elevation profile from adventure.
Added ability to duplicate geotagged photos.
Added link the BaseCamp license agreement in help menu.
Added info icon for adventures in folder list.
Added ability to undo/redo on supported devices.
Added ability to drag and drop folders with BaseCamp data from the file system.
Added ability to accept Google Maps coordinate format when centering map at position.
Added new dog icons.
Added more information to adventure find results.
Added ability to permanently hide the adventure group.
Changed the simple route dialog to transition into the route properties so the route can edited further.
Don't let scroll-wheel change detail setting after changing setting.
Made sure waypoint creation date is visible by default in the waypoint properties dialog.
Fixed an issue where turning off the display of points would leave a lot of "shopping cart" POIs on the map for certain map products.
Fixed an issue where the selection was lost when left-clicking on the map with the hand tool.
Fixed issues where BaseCamp erroneously allowed you to create waypoints and would crash.
Fixed issues with route/track creation and joining.
Fixed issues with deleting data on devices.
Fixed issues with creating routes from tracks.
Fixed transfer of waypoint categories to device.
Fixed issue when BirdsEye selection box was dragged too far North.
Fixed issue with displaying custom maps on devices.
Fixed various adventure issues.
Removed Unlisted Data list (it will be back).
  • 0 over 12 years ago
    Have you tried MapInstall 4.0? These features are already implemented. But if you send maps to removable drive, only gmapsupp.img is used. You need to connect GPS to get more functionality.
  • Former Member
    0 Former Member over 12 years ago
    a)\GeotaggedPhotos are not in the BC backup, so restoring on another computer does not restore \GeotaggedPhotos.

    d) Deleting a photo waypoint in BC does not delete the copy in \GeotaggedPhotos.


    a) The backup does contain that folder. When we backup, we back up the entire %APPDATA%\Garmin\BaseCamp folder, not just %APPDATA%\Garmin\BaseCamp\3.3, e.g.

    d) That would be a bug, that should work. Please note that the photo will not be deleted till you close BaseCamp. (So you can easily Undo the deletion if you change your mind.)
  • Former Member
    0 Former Member over 12 years ago
    I made this suggestion log time ago, but still is not implemented.

    When you send a map to a Garmin unit or a removable memory using MapInstall, the map is being sent using a unique name (gmapsupp.img)

    This causes two potential problems or annoyiances:
    1. The possibility of removing a previous map you already have saved..
    2. Or the need (in the newest Garmin units) to previously change the img's name kept already in the unit to avoid the annoying substitution of the map

    Since BaseCamp can recognize the GPS model you connect to you computer I am wondering why you don't let to choose the name of the map at the time of sending it to your GPS if that unit is compatible with names different to gmapsupp.img


    MapInstall 4.0 creates unique image names for devices that support nMaps (img files of any name). http://www8.garmin.com/support/download_details.jsp?id=3291
  • Former Member
    0 Former Member over 12 years ago
    When "rubber banding" a route there is no way to snap to an intersection or other possible selections like in Mapsource. The route tool will do this for the beginning and end points but not any other points.
  • 0 over 12 years ago
    A related issue: If you move a via point in BC it keeps its original name. If you move a via point in MS it takes a new name from the location to which it is moved. The behaviour in MS is much more helpful when adjusting a route to hit intersections and thus avoid flags and announcements on the Zumo.

    Unfortunately, the trick to place via points on intersections in order to avoid announcements does not work for the Montana.
  • Former Member
    0 Former Member over 12 years ago
    Don't know if this already mentioned*):

    Why are toll roads and carpool lanes avoidance greyed out (and carpool lanes activated) by default in the cycling actvities?

    In Europe there are toll bridges where cyclists have access to but you dont want to cycle there.

    About carpool lanes I can't give a good example but I think they are good to cycle on (very wide shoulder) if is allowed to cycle on motorways and there are no other alternatives (USA?).

    I have to admit that the actual reason I mention this is that those options messes up all custom (cycling) OSM maps. Carpool lane avoidance blocks all roads with access=no and motorcar=no. In my custom map I "misuse" the toll road avoidance option to navigate on cycle routes.

    I can understand that Garmin doesn't have to care about 3rd party maps but at least make those options available in the cycling activities. This might help us and of course also Garmin, because a lot of Garmin users use OSM maps as well (and many users have bought a Garmin unit because of the availability of free OSM maps).

    *) Edit: see also https://forums.garmin.com/showpost.php?p=117905&postcount=10
  • Former Member
    0 Former Member over 12 years ago
    Don't know if this already mentioned*):

    Why are toll roads and carpool lanes avoidance greyed out (and carpool lanes activated) by default in the cycling actvities?

    In Europe there are toll bridges where cyclists have access to but you dont want to cycle there.

    About carpool lanes I can't give a good example but I think they are good to cycle on (very wide shoulder) if is allowed to cycle on motorways and there are no other alternatives (USA?).

    I have to admit that the actual reason I mention this is that those options messes up all custom (cycling) OSM maps. Carpool lane avoidance blocks all roads with access=no and motorcar=no. In my custom map I "misuse" the toll road avoidance option to navigate on cycle routes.

    I can understand that Garmin doesn't have to care about 3rd party maps but at least make those options available in the cycling activities. This might help us and of course also Garmin, because a lot of Garmin users use OSM maps as well (and many users have bought a Garmin unit because of the availability of free OSM maps).

    *) Edit: see also https://forums.garmin.com/showpost.php?p=117905&postcount=10


    I'll see what I can do, but no promises. The problem might be that the routing code (that we share with the device) sets these automatically regardless of what you set in the UI. If that is not the case (which is what I hope) then exposing these options would make sense.
  • Former Member
    0 Former Member over 12 years ago
    I'll see what I can do, but no promises. The problem might be that the routing code (that we share with the device) sets these automatically regardless of what you set in the UI. If that is not the case (which is what I hope) then exposing these options would make sense.


    Thanks Falagar,

    Is there a chance that the Dakota will be released with the new firmware that is compatible with Basecamp (and the activity routing) soon?
  • Former Member
    0 Former Member over 12 years ago
    Car pool lanes in NZ (known as transit lanes) are open to bicycles & motorbikes. Of course, bicycles are still not allowed on motorways. So, it makes no sense to force routing avoidance of these, unless your definition of these is that they are always on motorways.

    Regards,
    Peter.
  • Former Member
    0 Former Member over 12 years ago
    Car pool lanes in NZ (known as transit lanes) are open to bicycles & motorbikes. Of course, bicycles are still not allowed on motorways. So, it makes no sense to force routing avoidance of these, unless your definition of these is that they are always on motorways.

    Regards,
    Peter.


    As a point of reference (and general trivia), in Texas (and probably most of USA), "carpool lanes" (aka HOV - High Occupancy Vehicle lanes) are usually only present on highways.... where bicycles are prohibited. And motorcycles (125ccs or more) are allowed on highways AND in HOV lanes even if there is only one rider. Highways range in speedlimit from 55mph to 75mph, and always have a minimum speed (even if it is not posted), usually 45MPH at the least. Bicycles and small displacement motorcycles/scooters/mopeds usually cannot do these minimums and that is why they are prohibited on highways.

    Most of the toll roads are high speed highways as well, usually 65MPH or more.

    In some very urban & suburban areas (Dallas, Austin), there are bicycle ONLY lanes... sort of a half-width lane next to the curb. Motor vehicles may not enter the bicycle lane (except city buses, for passenger boarding) .


    P.S. had to login, fail, hit BACK button, and repeat several times to post this reply.