Related

BaseCamp 3.3.0.3 Beta available

Former Member
Former Member
We decided to release another Beta before 3.3.1. This release fixes some of the shaping point issues for Zumo 4x0 and 5x0, so we are especially interested in feedback on that (please use https://forums.garmin.com/showthread.php?t=24732 to provide feedback regarding that topic). We also fixed some other issues, and added a few more features that weren't done at the time of the first Beta.

Download the Beta here: http://developer.garmin.com/apps/BC/BaseCamp_3.3.0.3_Beta.exe. If you used 3.3.0.2, you should also be able to update from within BaseCamp.

If you haven't tried 3.3.0.2, make sure to check out https://forums.garmin.com/showthread.php?t=24413, there have been a lot of changes!

Change list from BaseCamp 3.3.0.2 to 3.3.0.3
  • Fixed zumo 5x0 and 4x0 route transfer issues. Note that this may cause route transfer issues on the zumo 660. A future firmware update on the 660 will address this issue
  • Update waypoint references to map data when recalculating routes. Advice for the first beta that said that shaping points only worked for brand new routes can now be ignored
  • Added hiding of Activity profiles
  • Added creating OpenCaches from waypoints
  • Added calculating ascent and descent for direct routes
  • Added indication of data filter visibility state on the data list
  • Change to prevent property dialogs becoming lost off screen after screen resolution changes
  • Fixed any profiles from BaseCamp 3.2 that have invalid routing preferences (ie invalid vehicle types and incorrect avoidances)
  • Fixed list in-place rename requiring pressing enter to complete the edit
  • Fixed the "Reset Headers" context menu being displayed after renaming an item
  • Fixed issue writing out altitude when exporting to the GDB file format
  • Fixed track filtering "automatic mode" for tracks with no time information


Known issues
  • Doing a “Send to” from the root device folder to “My Collection” crashes. This is when selecting the entire contents of the device in the folder list, and only when selecting the root My Collection in the folder/list picker dialog.
  • Sending geocaches to some of our older devices (first generation Oregons and older) fails when there aren’t already geocaches on that device (a geocaches.gpx file).


These will be fixed in the final release.
  • Former Member
    0 Former Member
    Thanks for the screen-shot and the Backup. See if that gets me anywhere.

    Your help is much appreciated.
  • Former Member
    0 Former Member
    I could reproduce the issue.

    Using the Beta to export routes with custom route settings (activity profile set to None for that route) will create invalid gdb files.

    This will be fixed in the final 3.3 release.

    Thanks again for your help in tracking down this issue.
  • Former Member
    0 Former Member
    I don't understand what None means.

    Good call. I wouldn't have thought about activity profile conflicts. Thanks.

    My impression is that the Activity Profile named on the Tool Bar is the default used for routes and the individual route properties of None says no override of the default activity profile.

    MapSource gdb imported into BaseCamp sets the individual route properties activity profile to None. A new route made in BaseCamp sets the individual route properties activity profile to the tool bar default.

    I don't understand what None means.
  • Former Member
    0 Former Member
    MapSource gdb imported into BaseCamp sets the individual route properties activity profile to None. A new route made in BaseCamp sets the individual route properties activity profile to the tool bar default.


    I haven't seen this to be the case in my installation of BC beta, importing MS created routes kept my Motorcycle Profile for the imported route.
  • Former Member
    0 Former Member
    Why would you put a waypoint in a route1, route2 or test list unless it belonged there for some reason? I would assume you put it there because there was a good reason for this waypoint to be in that list, and so it makes perfect sense to me that it would show up as that category on the device.

    I thought it would be obvious from the list names I used (intentionally) to illustrate.

    Just in case you didn't figure it out, the TEST list that I created in the CATEGORIES folder is a category and was correctly added.

    The ROUTE1 and ROUTE2 lists that I created in the My Collection root are for route planning so I do not want them to appear as categories on the device.

    Basecamp already forces us to use the kludge of adding waypoints to lists if we want to do route planning. There are a couple of lengthy threads on the subject in here already so I won't repeat all the details.

    The point is that there are multiple reasons for lists. Only one of them is for categories.

    So if I have a list that is holding a route or two and their associated waypoints the very last thing I want is for that list name to be added as a category to all the waypoints it contains. That list is for route planning in Basecamp, not for categorization of the waypoints for search purposes on the device.

    It's just plain wrong in this use case.

    Lists are used for organizing many things for many reasons. They are used for too many things to make the simple assumption that we want them all to be added as categories on the device..

    ...ken..
  • Former Member
    0 Former Member
    FALAGAR,

    I have not been able to find a feature in BC that is in MS. The feature is the advanced avoidances. With this feature you could select sections of road or areas to avoid. If you knew there is roadwork and wanted MS to route around this you could use the advanced avoidances. I have not been able to find this in BC. Does this feature exist?

    Also, a comment on the activity profile. Not sure this is an issue but it was a little confusing until I figured it out. I made a route with the motorcycling activity profile and then changed to the automotive activity profile, right clicked on the route, picked advanced>recalculate route; BC recalculated the route but it did this using the activity profile that the route was originally created (in this example motorcycling). However, if I go to the route properties and change the activity profile to automotive, BC automatically recalculates the route using the automotive activity profile. I am not sure what the "advanced>recalculate route" would be used for. If BC retains the activity profile with the route recalculating won't change anything if it does the recalculate with the same activity profile the route was originally generated with. Hope this makes sense.
  • Former Member
    0 Former Member
    I haven't seen this to be the case in my installation of BC beta, importing MS created routes kept my Motorcycle Profile for the imported route.

    MapSource does not have activity profiles. How would a MS route have an activity profile to keep?
  • Former Member
    0 Former Member
    MapSource does not have activity profiles. How would a MS route have an activity profile to keep?


    BaseCamp tries to be smart in picking a profile if it can.

    Setting the activity profile for a route to NONE, means that you get custom route settings for that route (the Route Options tab will be visible and allow you to adjust the settings).
  • Former Member
    0 Former Member
    FALAGAR,

    I have not been able to find a feature in BC that is in MS. The feature is the advanced avoidances. With this feature you could select sections of road or areas to avoid. If you knew there is roadwork and wanted MS to route around this you could use the advanced avoidances. I have not been able to find this in BC. Does this feature exist?

    Also, a comment on the activity profile. Not sure this is an issue but it was a little confusing until I figured it out. I made a route with the motorcycling activity profile and then changed to the automotive activity profile, right clicked on the route, picked advanced>recalculate route; BC recalculated the route but it did this using the activity profile that the route was originally created (in this example motorcycling). However, if I go to the route properties and change the activity profile to automotive, BC automatically recalculates the route using the automotive activity profile. I am not sure what the "advanced>recalculate route" would be used for. If BC retains the activity profile with the route recalculating won't change anything if it does the recalculate with the same activity profile the route was originally generated with. Hope this makes sense.


    Advanced avoidances haven't made it into BaseCamp yet.

    If you change the activity profile in the toolbar, that changes the default profile BaseCamp is currently running in. It doesn't change the profile of the routes (you might want to have routes with different profiles, one for bicycling, one for automotive, e.g.). Changing the profile in the route properties dialog will change the profile for that particular route.

    Recalculating a route will also yield different results if you switched the map, for example (like when you update from CN NT 2012.3 to CN NT 2012.4, and want to recalculate a route so it still works on the Zumo that now also has 2012.4).
  • Former Member
    0 Former Member
    MapSource does not have activity profiles. How would a MS route have an activity profile to keep?


    I guess another way to say this is, an import from Mapsource into BC beta appears to assign the toolbar Activity Profile to the imported route's properties. I don't use and have not seen Activity Profile 'None' appear as a default or associated with any route.
Copyright © 1996-2025 Garmin Ltd. or its subsidiaries