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
    Waypoint Categories

    I am using a GPSMap 276c and have 16 categories set up in the unit and in MapSource.
    MapSource and the 276c work well together with the categories.
    From what I see the categories are not transferred into BaseCamp. Should the categories
    that are setup in the gps been sent to BaseCamp?

    Mark
  • Former Member
    0 Former Member
    We don't transfer the categories per se, what BaseCamp does is to create lists (or put waypoints in an already existing list of that name) for all the categories the waypoints are in that you transfer from the device.

    So connect your device, select the waypoints you want to transfer, right-click, 'Send to', pick My Collection.

    If you have categories on the device, but don't transfer waypoints from that category, BaseCamp will not create lists for these categories.

    I hope this makes sense, let me know if it doesn't.
  • Former Member
    0 Former Member
    I haven't had a chance to check out the betas yet. Is there some indication that a list is actually a "category" rather than just another list?

    Or to ask it another way, if I have, say, 20 lists in my collection and 9 of them are "categories" and the rest are not, is this obvious at a glance?

    ...ken...
  • Former Member
    0 Former Member
    I have a nuvi 2550 and the trasnfer route doesnt work. The 2550 does not recognize it at all.
    The waypoints get transfered fine and show up on the favorites but not the route.
    It works fine with Mapsource.
  • Former Member
    0 Former Member
    I haven't had a chance to check out the betas yet. Is there some indication that a list is actually a "category" rather than just another list?

    Or to ask it another way, if I have, say, 20 lists in my collection and 9 of them are "categories" and the rest are not, is this obvious at a glance?

    ...ken...


    There is no distinction.
  • Former Member
    0 Former Member
    I have a nuvi 2550 and the trasnfer route doesnt work. The 2550 does not recognize it at all.
    The waypoints get transfered fine and show up on the favorites but not the route.
    It works fine with Mapsource.


    I'll have to check that. Anyone else has seen routes not working when sent with BaseCamp 3.3 but it works in MapSource?
  • Former Member
    0 Former Member
    I haven't had a chance to check out the betas yet. Is there some indication that a list is actually a "category" rather than just another list?

    Or to ask it another way, if I have, say, 20 lists in my collection and 9 of them are "categories" and the rest are not, is this obvious at a glance?

    ...ken...


    I just created a List Folder called ... you guessed it: CATEGORIES. ;)

    Now when I create waypoints I just drag/drop from my originating List to the appropriate category-List.

    Cheers,
  • Former Member
    0 Former Member
    Okay, I've been using 3.3.0.3Beta for, like, all of 27 seconds and I discovered this. In the following post regarding the .0.2Beta ...

    https://forums.garmin.com/showpost.php?p=117501&postcount=134

    ... you said that you prompt for delete confirmation if it's a destructive/permanent delete, e.g. if you hit Shift/Delete on/in a list.

    Not!!

    Immediately after installing the 3.3.0.3Beta I decided to clean out some junk to start my "category" testing cleanly. So I clicked on a list name in My Collection, hit Shift/Delete and ... it was gone!! :eek: No confirmation prompt.

    I clicked on My Collection just to be sure that the original items were indeed gone and they were. Shift/Delete worked exactly as expected -- deleted the list and its contents from My Collection -- but no confirmation prompt.

    I did it with three more lists just to be sure. It's absolutely consistent. Clicking on a list name in My Collection and hitting Shift/Delete does NOT result in a confirmation prompt and it DOES result in a permanent destructive delete of the list AND its contents from My Collection.

    Looks like it needs a little work. ;)

    For what it's worth, Edit > Undo multiple times was able to restore the whole works. That was impressive because the very first of the four or five deletes took out a list containing over 300 waypoints and a few tracks.

    ...ken...
  • Former Member
    0 Former Member
    I apologize if this has already been mentioned somewhere/sometime...

    "Sort by..." ... Any time you right-click and select "Sort by" it sorts everything. EVERYTHING.

    That is, if I right-click/Sort by in a list, it immediately sorts all the other lists AND My Collection by the same sort criteria.

    That's not especially useful.

    Please consider restricting the sorting to only the display of the element I've selected, e.g. only My Collection but not the contained lists; only the selected list; etc. and leave everything else alone. It's only a display deal anyway. No need to actually sort the underlying database if that's what you're doing.

    ...ken...
  • Former Member
    0 Former Member
    I apologize if this has already been mentioned somewhere/sometime...

    "Sort by..." ... Any time you right-click and select "Sort by" it sorts everything. EVERYTHING.

    That is, if I right-click/Sort by in a list, it immediately sorts all the other lists AND My Collection by the same sort criteria.

    That's not especially useful.

    Please consider restricting the sorting to only the display of the element I've selected, e.g. only My Collection but not the contained lists; only the selected list; etc. and leave everything else alone. It's only a display deal anyway. No need to actually sort the underlying database if that's what you're doing.

    ...ken...


    We are sorting just the displayed data. But the sort column and order aren't remembered on a per list basis. That's why you see the same sort order and column for all lists.

    I can see that remembering this on a per list basis could be useful. I'll add a case. That seems more like a nice-to-have feature, so no promises when we'll get to work on it.