Related

BaseCamp 3.3.0.2 Beta is available

Former Member
Former Member
BaseCamp 3.3 is here! We are starting off with an early Beta release to give everyone a chance to check out the new features and pound on it for a little bit before we release the final version.

Download it here: http://developer.garmin.com/apps/BC/BaseCamp_3.3.0.2_Beta.exe.

We have incorporated a lot of user requests from this very forum. If your desired feature/bug fix didn't make it into this release, don't hesitate to remind us.

We are very interested in your feedback, please report bugs and oddities you find, and comment on the new features.

This is the change-list from 3.2.2 to 3.3.0.2. I will add some explanations and screen-shots in later posts.

  • Added collapsible list folders and sub-lists for improved organization.
  • Added shaping point support for zumo devices like done in MapSource.
  • Added explicit support for shaping points. These will be transferred to supporting devices.
  • Added support for transfer of waypoint categories on supporting devices. These are displayed in BaseCamp as lists.
  • Added more activity profiles, with improved activity routing on supported maps.
  • Added specific avoidances for various road classes, removed the road selection slider.
  • Added custom activity profiles.
  • Added keyboard short-cuts for editing tools (divide, insert, erase).
  • Added a tools menu for easier discovery of tool keyboard shortcuts.
  • Changed to make GPX files on a memory card directly editable.
  • Changed to read all GPX files on a memory card, similar to how devices behave.
  • Improved graphing of track data.
  • Improved graphing when multiple routes or tracks are selected.
  • Improved layout of geotagged photo, waypoint, route, and track properties.
  • Added additional statistics to route and track properties.
  • Added 'Center on map' check-box on route and track dialogs.
  • Added an easier way to add waypoints to routes (Insert Waypoint button).
  • Added additional data fields to waypoints (such as address and phone number).
  • Added display and updating of date last modified for waypoints.
  • Added display of lists that contain this data item to properties.
  • Added receiving geocache visits from devices.
  • Added logging geocache visits on OpenCaching.com.
  • Added printing of geocaches.
  • Added alternate notification mechanism (less annoying pop-ups).
  • Added display settings to adjust width of routes and tracks.
  • Added support for importing waypoints and tracks from KML/KMZ files.
  • Added suggested file name when exporting (so it isn't always 'untitled').
  • Added more map details for higher detail setting.
  • Added data filters to map view.
  • Added preserving the dialog size for each data type.
  • Added option to reset track's altitude to map data.
  • Added functionality to remember display feature settings per profile.
  • Changed 'Remove List and Contents' to 'Remove list and unique contents'.
  • Added Shift-Delete short-cut for 'Remove list and unique contents'.
  • Improved printing of routes and tracks.
  • Fixed issues with sending routes to the zumo.
  • Fixed elevation profile labels for Windows XP (no longer invisible).
  • Fixed issue when duplicating a route. BaseCamp will now also duplicate the waypoints in that route.
  • Fixed issue with the data filter not being remembered between application runs.
  • Former Member
    0 Former Member
    I noticed this anomaly / BUG recently.... (last week before joining this forum)

    At one point, had a couple of waypoints that I had imported (copied) from Montana 650. I kept wondering why they were not appearing on the map.
    (They were showing up in the "List" but not on the map......)

    To get them back, I actually copied them into to another list located in a different folder. (And then back again)

    I have no idea of how or why they became invisible on the map, but they did. At first was thinking I must be doing something wrong. That clearly wasn't the case. I actually began looking for a "right click" option (on the missing item's "alt menu") for a show / hide option.

    At the time, it appeared to me that there may be an unused "hidden / show" attribute feature not yet implemented in this version of BaseCamp. (v3.3.0.2 beta)


    We have not been seeing that behavior. There is no unused (or used) hidden/show feature in BaseCamp.

    Are you sure you had a list selected that contained the data? Can you still reproduce this behavior?
  • Former Member
    0 Former Member
    I am aware of this.... But it's still too easy to hit the wrong key (delete) key unintentionally and deleting a waypoint etc.

    Being very fast on a keyboard, I speed type, and sometimes I still hit the wrong key. (Especially the weird ones when in low light.) ie: go for the arrow key and catch the delete key by mistake..... With no warning, waypoint / data could be gone forever.

    And, I know there is a backup feature, but there's no reason to restore if you don't know anything is wrong or missing in the first place!

    Besides, sometimes (as in: right click options) you get a prompt warning that a waypoint is about to be deleted. Hence, there is no consistency in program behavior in this regards.....


    The idea is to prompt when we will permanently delete data (you can check to not see that message again).

    We do not prompt if all you do is remove data from a list (that's the 'Delete' key behavior when you are in a list). The data is still in My Collection, but not in the current list. Hitting 'Shift-Delete' will remove the data from My Collection entirely. That's where we do prompt.

    There is some inconsistency as to how we do this in the Beta, we hope to address this for the final version.
  • Former Member
    0 Former Member
    Beta starts MapInstall when I connect my 60CSX

    When I connect my 60CSX and switch to Mass Storage mode MapInstall pops up and asks me if I want to install maps. Sorry if this has already been mentioned, but I can't figure out how to query the thread, and it's now waaay to long to read.
  • Former Member
    0 Former Member
    Never put an 60Csx in USB-Storage, unless you want to retrieve archived tracks or install Maps. In both cases it's better to remove the microSD kaart and do manual import of the archived tracks into BaseCamp.

    BC will recognise your 60Csx correctly if attached and not put in USB-Storage mode.
  • Former Member
    0 Former Member
    I agree, this thread has gotten pretty long.

    If you have some specific feedback, feel free to open up a new thread, so the discussion is a little easier to follow.

    I usually don't try to enforce it, because I am happy about any feedback, regardless which thread it appears in.

    I'll try to keep it a little more cleaned up for the next release.
  • Former Member
    0 Former Member
    We have not been seeing that behavior. There is no unused (or used) hidden/show feature in BaseCamp.

    Are you sure you had a list selected that contained the data? Can you still reproduce this behavior?


    YES! That's why I reported it. It's a bug somewhere, somehow..... Don't know why, or how it occurs. (Usually I can diagnose & reproduce things like this. This time, I just don't know what caused it. ) Had I not been "organizing using the new folder nesting options", I never would have come across this issue. (That's also why I had initially thought there might be an undocumented / unimplemented hide/show feature.)

    NOTE: I can't help but wonder whether this could have something to do with the "Reset Headers" issue that others have reported earlier in this thread.....

    All I know is that I ran across one of my waypoints that was in a list, within a folder. No matter what I did, it would not show up on the map when I selected the parent folder.

    Before deleting it (the waypoint), I chose to try and copy it (the "instance" of the waypoint) to another folder/list, just to see what happened. Clicking on that new folder, it appeared.

    I then deleted the original (waypoint instance / "shortcut" that was not showing on the map.) Finally, I copied it back into the original list/directory. (Upon selecting that folder, it appeared on the map.)

    I highly doubt this is an "isolated incident." It will show up elsewhere! It probably already has, but just hasn't been noticed yet.

    Can't explain why I am always the one to uncover problems like this, but I always do. For over 25 years, I've had a "nack" for finding that "needle in a haystack" when it comes to database * data related problems..... I have been buried under technology for over 30 years. I've also got a lot of beta testing experience. (I occasionally code too.) It used to be fun....... "When you see a bug, you know it!"

    Also: When I first installed this beta 3302, my old waypoints (in the most recent non beta version of Basecamp 322) did not initially appear. (Nor did the pre-existing list structure show up in the beta. Not at first anyways...) FYI: I had not installed any other interim betas such ass 3301 etc. ~So I connected the Montana GPS and copied the data over and organized waypoints & routes from scratch. The second time I launched this beta, I noticed the original lists appeared under the "My Collection" root, "almost as if by magic." THIS WAS VERY STRANGE BEHAVIOR! No idea if this had anything to do with it...... Regardless, I only found one (1) waypoint that exhibited this strange behavior. I suppose there may have been others too......

    ~Hope this helps...
  • Former Member
    0 Former Member
    Well, the thing we fixed was something on the 660, but it broke routes for older Zumos.

    Can you attach a route (as gpx) that crashes your Zumo 220? And also let us know which map product and version you used?

    I'd like to verify that our internal fix works for your route as well.

    I apologize for the inconvenience.

    Hi Falagar,
    no problem. I attached the faulty route. Map is City Navigator NT Europe 2011.4. Softwareversion of the Zumo 220 is 2.70.

    Regards
    Marcus
  • Former Member
    0 Former Member
    Thanks for reporting back to us.

    I tried for a while to reproduce this here, but I haven't been successful. But it is very possible that I am just missing the crucial piece that makes this bug appear.

    If you can still reproduce this with your current data, is there any way you could make a backup of your data available to me? Upload it somewhere and send me a link in a personal message? Then please tell me the steps you take to display the behavior you are seeing. (Which folder you select, which waypoint you expect to appear).

    We fixed the reset headers issue, that should work in the next Beta version (yes, there will be a follow-up Beta that will fix some of the reported issues). I am not 100% sure if that is related, but I am somewhat doubtful.

    Also: When I first installed this beta 3302, my old waypoints (in the most recent non beta version of Basecamp 322) did not initially appear. (Nor did the pre-existing list structure show up in the beta. Not at first anyways...) FYI: I had not installed any other interim betas such ass 3301 etc. ~So I connected the Montana GPS and copied the data over and organized waypoints & routes from scratch. The second time I launched this beta, I noticed the original lists appeared under the "My Collection" root, "almost as if by magic." THIS WAS VERY STRANGE BEHAVIOR! No idea if this had anything to do with it...... Regardless, I only found one (1) waypoint that exhibited this strange behavior. I suppose there may have been others too......


    This seems indeed very odd. If you delete the 3.3 folder in %APPDATA%\Garmin\BaseCamp\Database (after you've done a backup), does the same thing happen? The 3.3 folder is where 3.3.0.2 stores its database, so if you delete it and then start the Beta it will copy the 3.2 database to the 3.3 folder. So in theory, you should be seeing whatever behavior you were seeing when you started the Beta the first time.

    If you can reproduce the behavior, I would also be interested in a copy of your backup.
  • Former Member
    0 Former Member
    Thanks for reporting back to us.

    This seems indeed very odd. If you delete the 3.3 folder in %APPDATA%\Garmin\BaseCamp\Database (after you've done a backup), does the same thing happen? The 3.3 folder is where 3.3.0.2 stores its database, so if you delete it and then start the Beta it will copy the 3.2 database to the 3.3 folder. So in theory, you should be seeing whatever behavior you were seeing when you started the Beta the first time.

    If you can reproduce the behavior, I would also be interested in a copy of your backup.


    I'll see what I can come up with. I'm wondering whether it may have taken some time to capture the 3.2 database into the 3.3 beta data set. (More time than actually allotted before I began to work with the 3.3 beta.) ~ Upon initial launch of 3.3 beta, my waypoints were completely empty. I remember thinking: "Arrrghhh, Garmin never included automatic import in the beta"..... So I began reconstructing my data. I also should have specified this is happening on a windows 7 64bit business system. (A commercial grade Lenovo Thinkpad that has no other "known issues.") ~ Awesome top of the line system at the time......... I've had it for a few years.

    As for the waypoint not showing on the map, I'll see what I can come up with..... I just wish I knew exactly when it happened, so "I could backtrack and reproduce the anomaly."

    I do remember that when I initially found the problem, I had been reviewing all my waypoints, to make sure everything was categorized properly under the right sub folders...... I had seen a recently recorded/captured (within the past month) waypoint in a selected folder/list and noticed it was not being displayed on the map..... There were 5 or 6 waypoints in this folder list, but only 4 or 5 displayed on the map. I'm "thinking" that the specific waypoint must have been "still intact" at the root level, but not fully acknowledged when it was initially placed / "copied" into a sub-directory / list.

    I'm looking at the data now, hoping to find another waypoint like this.... And nope, there are no other waypoints presently missing from the display (that I can see). Also: None of the data seems to be missing from the old version 3.2. (So the problem must be exclusive to 3.3 beta, and likely have something to do with the nested folder support.) ~ Because the missing waypoint had bee moved into a sub-directory, which didn't/couldn't exist in 3.2. ~ I was wondering if somehow the problem was created during the import routine since I had just dragged and dropped these few points over from the GPS. (Hence, duplicate named data was being imported).... I discounted this as a possibility because only one point exhibited this problem.

    I do have many other waypoints imported from kmz files in different organized directories/lists.... These point represent cell towers, Appalachian trail data, and water bodies etc. There's no way I can tell if some of these ones are not displaying properly.... Way too many points.

    It's worth noting that the problem was noticed with waypoints that were originally dragged and dropped from the Garmin Montana. (& possibly a result of the import/upgrade to 3.3) ~ Not from importing kml/kmz files!

    Also, I just remembered (& I'm wondering if this could have been the cause of all this): I ended up installing the beta twice. Immediately upon initial install, I realized that the original 3.2 (non beta) was still running. (I had thought I had closed it out prior to installing, but apparently not.) Since I wasn't sure of the implications, I closed it out and immediately re-ran the installation. Upon running Basecamp the first time, (after that), that's when I saw an empty data set....

    I'm trying to reproduce & find what caused the problems. If and when I do, I will save the data....
  • Former Member
    0 Former Member
    Never put an 60Csx in USB-Storage, unless you want to retrieve archived tracks or install Maps. In both cases it's better to remove the microSD kaart and do manual import of the archived tracks into BaseCamp.

    BC will recognise your 60Csx correctly if attached and not put in USB-Storage mode.


    BaseCamp Beta MapInstall pops up when I connect my 60CSX. BaseCamp isn't running. It happens whether in operating mode or mass storage mode.