Hi,
I use BaseCamp mostly to download and organize waypoints and tracks from my GPSmap 60CSx. Couple of days ago, I was prompted to update BaseCamp to a new version (4.3.3). Unfortunately, it no longer works correctly with my waypoints:
- A geocache waypoint was originally uploaded to my GPSr with the "geocache" symbol. Out there, I found the geocache and pressed the "found" button (on the display), which changed the waypoint symbol to "geocache found". However, when I download all waypoints to BaseCamp (using the green+blue button in the toolbar), the waypoint appears again with the "geocache" symbol, not "geocache found".
- During the trip, I create new waypoints: I press the "Mark" button (hardware), then edit the coordinates start navigating to the point (typical usecase: at a stage of a multicache, I know all input numbers, I compute the final coordinates and want to be navigated to the final location). When downloaded to BaseCamp, these new waypoints are there but they are at completely wrong coordinates. I suspect that they might be at the place where I stood at the time I was creating the waypoints but I am not sure.
Is it possible that the GPSr unit somehow remembers "original" waypoint data before any edits I do ... and that BaseCamp now accesses this old, outdated data, ignoring my edits?
My previous version of BaseCamp worked OK. If I knew what would happen, I would never allowed the update, even if it meant that I had to deny it every time I start BaseCamp :-( Unfortunately the old versions do not seem to be available on the web. And I do not even know how to figure out what was the number of the previous version I had (4.2.5 perhaps?)
UPDATE: Before actually submitting this post, I tried one more thing, I completely removed all points and tracks from "My Collection" (I had exported them to GPX files anyway) and downloaded the current data from the unit again. The error did not occur this time. So it seems some interaction was involved with the (lots of) data downloaded previously. Still, the coincidence with upgrading to BaseCamp 4.3.3 is striking, so I thought I'd report it anyway, even though my problem seems to be solved for the moment.
Thanks
Dan
