Related

BaseCamp 4.1.0 is available

Former Member
Former Member over 12 years ago
You can update to BaseCamp 4.1.0 from within BaseCamp. The download link http://www8.garmin.com/support/download_details.jsp?id=4435 should be active soon as well.

Change List
Added support for Garmin Cloud Storage.
Added support for searching and displaying Custom POIs from devices (GPI file support).
Added ability to report map errors directly from within BaseCamp.
Added support for new statistics track extension, this should allow BaseCamp and future devices to have the same track statistics.
Added better error messages for adventure publishing failures.
Implemented Part I of Find experience rework (simultaneous searches, less confusing input boxes, added Find menu, added support for user data search).
Improved behavior when editing or deleting route and track points in a list, BaseCamp now remembers the position in the list.
Improved decimal precision for low speeds.
Improved 'Send To Device' and 'Receive From Device' dialogs.
Fixed an issue where BaseCamp would erroneously prompt for Geotagged photos on Garmin-mode devices.
Fixed an issue where the folder data list size wasn't preserved.
Fixed an issue with importing KML files from Google Earth.
Fixed an issue where the original routes were not restored after cancelling during the calculation phase of a route join.
Fixed an issue where single digit entry into Arrival/Departure times may not get committed to database.
Fixed an issue with displaying waypoint comments that take more than 1 row.
Fixed an issue with missing/corrupt system services. BaseCamp now prompts the user.
Fixed an issue with sending dog icons to older Garmin devices.
Fixed an issue with resetting the activity profile.
Fixed an issue where BaseCamp sometimes would not sync with devices.
Fixed an issue with restore.
Fixed some issues with Undo and Redo.
Fixed shutdown issues.
Fixed an issue in Danish when viewing route properties.
Fixed issue where BaseCamp would not display 'TOPO Sweden V3 - Svealand'.

Cloud Storage

Every Garmin user will have 150MB of cloud storage to sync your data (waypoints, routes, tracks, etc.) between different computers. This should be fairly seemless, just log in with your MyGarmin account, drag and drop data into your cloud storage device and it will be synced on the cloud so can access it if you run BaseCamp on a different machine.

Part I of Find Rework

BaseCamp will now search for several data types concurrently (like the Mac version has been doing for a while). There is no city selector box anymore (you should just be able to search for e.g. "sea world, san diego, ca" from anywhere on the map). We added a find menu. You can search in your data as well now (useful if your collection has grown very large).

Find is still a work in progress, but any feedback would be more than welcome. There will be further find improvements in 4.2.

Custom POIs

BaseCamp can now display and search for Custom POIs (contained in GPI files) that are on the device.

Report Map Errors

Now you can just right-click on the map and report a mapping error directly to Garmin. The form will be prefilled with the map product and the location. Reporting map errors does make a difference and our cartography team is very eager to receive them. So report away!
  • 0 over 12 years ago
    Interesting bug ... works like that for me too, but workaround is untick map tools then retick them and map tools toolbar is back :)

    Shouldn't be like that though.
  • 0 over 12 years ago
    It is worth noting that now BaseCamp starts fast and there is no computing of index for new maps.

    Address search moves map position before selecting a result and there is no option to return back. This is wrong, map should be moved only when I select new position from results list.

    I'm not sure, what is the meaning of distances shown next to results. Sometimes they are computed from my selected position and sometimes from BaseCamp moved position. Or maybe I get some cached results with cached distances, which have nothing to do with current search?

    Address search lasts very long, it is like 2-3 minutes on City Navigator Europe. If at this time I start POI search using cogwheel icon at results list, I get weird results or no results. I have to close search window to restore search functionality.

    Next search for POI works correctly if I wait till the end of address search or stop it manually.
  • 0 over 12 years ago
    Could we have more info on cloud data and how it's supposed to work as it's not yet in the BC help files?

    When I click sync what is it syncing with? Is it My Collection? If so it doesn't appear to work.

    When I open Cloud Data on a second PC what happens? Is it the cloud data from the original PC (I assume so)? What now happens if I choose sync?

    If I click Open I see a green line above an indication of how much space I've used from within the 150Mb, it's moving but never stops moving as though something is still happening. Is this correct?
  • Former Member
    0 Former Member over 12 years ago
    Interesting bug ... works like that for me too, but workaround is untick map tools then retick them and map tools toolbar is back :)

    Shouldn't be like that though.


    That does indeed work, thank you (why didn't I think of doing that?!).

    Kevin
  • 0 over 12 years ago
    FALAGAR -

    A few of us are having issues with BaseCamp crashing as soon as a Zumo 660/665 is hooked up.

    BaseCamp 4.1 starts normally and is perfectly stable. Then, when the Zumo is hooked up, BC starts to read the internal memory of the Zumo and immediately crashes.

    This is being reported on both the Windows platform and the Mac platform.

    edit: This issue seems to be related to extraneous .gpi files. Deleted the .gpi files and everything is good.Thanks to Danham for the fix.

    Tom
  • 0 over 12 years ago
    The statistic "total time" also shown as "elapsed time" ignores layover times at waypoints. Don't know whether this is a new feature, I just noticed it in 4.1 on Win7x64

    Eg. Depart @ 00:00, arrive 05:09 next day. Total time shows 26h 59m, should be 29h 09m. That's with 13 x 10 minute stops
  • 0 over 12 years ago
    The problem seems related to user POI's.

    BC crashes for me also when my Zumo 660 is connected. After deleting a file named 006D135900.gpi from the POI folder on the Zumo BC works OK. After disconnecting the Zumo I could still see all standard POI's. However, I could no longer see any user POI's even though I did not delete the user POI file (poi.gpi). It seems that the file I deleted is generated by the poi loader and somehow a prereqisite for seeing user POI's on the Zumo.

    The crash occurs whether the user POI's are loaded on the uinit itself or on the uSD card.

    Edit: Reloaded user poi's. I can now see my user poi's on the Zumo and BC works fine. Seems that the file 006D135900.gpi was the only problem, whereever it came from.
  • Former Member
    0 Former Member over 12 years ago
    Could we have more info on cloud data and how it's supposed to work as it's not yet in the BC help files?

    When I click sync what is it syncing with? Is it My Collection? If so it doesn't appear to work.

    When I open Cloud Data on a second PC what happens? Is it the cloud data from the original PC (I assume so)? What now happens if I choose sync?

    If I click Open I see a green line above an indication of how much space I've used from within the 150Mb, it's moving but never stops moving as though something is still happening. Is this correct?


    Syncing means syncing with the cloud. Cloud storage is disconnected from My Collection. It's its own database.

    When you open Cloud Data on a second PC, it should sync the data from the cloud to your second PC.

    The Green Bar only indicates how much space you still have, it doesn't indicate progress (although it sure looks like it does). We want to change that, because I agree it's confusing.
  • Former Member
    0 Former Member over 12 years ago
    FALAGAR -

    A few of us are having issues with BaseCamp crashing as soon as a Zumo 660/665 is hooked up.

    BaseCamp 4.1 starts normally and is perfectly stable. Then, when the Zumo is hooked up, BC starts to read the internal memory of the Zumo and immediately crashes.

    This is being reported on both the Windows platform and the Mac platform.

    edit: This issue seems to be related to extraneous .gpi files. Deleted the .gpi files and everything is good.Thanks to Danham for the fix.

    Tom


    I apologize for the trouble, we are working on a fix that doesn't involve deleting gpi files.
  • Former Member
    0 Former Member over 12 years ago
    The statistic "total time" also shown as "elapsed time" ignores layover times at waypoints. Don't know whether this is a new feature, I just noticed it in 4.1 on Win7x64

    Eg. Depart @ 00:00, arrive 05:09 next day. Total time shows 26h 59m, should be 29h 09m. That's with 13 x 10 minute stops


    Thanks for reporting. That seems wrong to me as well. I'll see if we can change that.