BaseCamp version 4.1

Frankly, I was too tired to post last night before going home. To turn on cloud syncing, go to the transfer menu and enable it.

I will post the full list of changes later, unless someone beats me to it. Note that the random location/map start up issue has not been fixed yet. Sorry for the inconvenience.

I pasted the changes below, Cloud syncing seems too easy. How does it know which computer to sync. I did not sign into the cloud unless signing into the forum is being used. Maybe I understand. I am currently using DropBox and I signed into Garmin on one computer. Because DropBox is syncing, I must be signed in on all computers as the other computers show me signed in. Hope double syncing is not a problem.


Thanks

Changes made from version 4.0.4 to 4.1.0:

Added support for Garmin Cloud Storage
Added support for searching and displaying Custom POIs from devices (GPI file support)
Added ability to user coordinates in search field
Added ability to copy/paste data from tables (User Data Table, Tracks, etc.) into other applications
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 Garmin Adventure publishing failures
Combined the two search boxes into one
Moved the search box to toolbar
Fixed issues related to retina display
Fixed various stability issues

Frankly, I was too tired to post last night before going home. To turn on cloud syncing, go to the transfer menu and enable it.

I will post the full list of changes later, unless someone beats me to it. Note that the random location/map start up issue has not been fixed yet. Sorry for the inconvenience.

Just FYI, the random map startup issue appears to be fixed, at least on my system (iMac i3, OS 10.8.2). If I move the map to a new location, then quit BC, the next time it starts up with that new location displayed, regardless of whether I made any changes.

-dan

Initial Impressions

Any update is welcomed, thank you.

The cloud sync has the potential to be a very useful tool, it's good now but with the addition of the ability to backup to the cloud it would be great. My average backup file size is ~50 megs so (in my application) the space provided would be adequate. This would allow preservation of the list and folder structure of projects.

I see that there is a windows registry hack (addition) to fix the map distortion issue found when displaying any map view north or south of the American mid west. Is there any way a similar fix could be instituted in the Mac version? The distortion is also alarmingly apparent in European maps with views anywhere north of Malta.

I'm going to assume that the implementation of waypoint category support, not lists, but true integral waypoint category support is dead. Please confirm or deny.

Again, thanks.

This new build of BC is crashing every time I connect my zumo 660. It does not crash when I connect my nuvi 760. Here's the crash log (attached)...



Based on the following portion of the report, I tried deleting the 3D map img file from my zumo. The program then tried to read the gmapprom.img file and crashed again.

Application Specific Information:
Time: 11:03:43 AM
Web app
Resident Memory: 1808MB, Virtual Memory: 848MB
Current Map: City Navigator North America NT 2013.3
Locale: en
Activity: Loading preinstalled map at path: /VOLUMES/GARMIN/GARMIN/GMAP3D.IMG

EDIT: Fixed with a workaround; see below.

-dan

FIXED! I should credit two other folks in other forums, but I've stared at so many today I can't recall who/where. They mentioned removing some stray POI files. In my case there was a file called 006D135900.gpi which contains a lot of airport location data that was causing the crash. Removed that file from my zumo and now BC launches without a hitch and the zumo shows up in the device pane very quickly.

I don't recall adding that file and sure enough, checking an old backup of my 660, it's always been there. I have some other gpi files in addition to poi.gpi but they don't seem to cause problems.

EDIT: alandb in the nuvi forum at gpspassion pointed me in the right direction. Thanks!

-dan

Just FYI, the random map startup issue appears to be fixed, at least on my system (iMac i3, OS 10.8.2). If I move the map to a new location, then quit BC, the next time it starts up with that new location displayed, regardless of whether I made any changes.

-dan

Yes, for me also, but it seemed to take a couple of cycles of closing and reopening BC. At first, I rolled my eyes at this still being ignored, but now all is well.

Still holding out hope for future ability to have multiple identically named waypoints in BC, so that they are truly the same name as listed on my 62st.

Not sure you'll get your last wish, which if I read you right you want identical waypoint names in My Collection, but you can already have the same names on your GPS and in Basecamp now :confused:

FIXED! I should credit two other folks in other forums, but I've stared at so many today I can't recall who/where. They mentioned removing some stray POI files. In my case there was a file called 006D135900.gpi which contains a lot of airport location data that was causing the crash. Removed that file from my zumo and now BC launches without a hitch and the zumo shows up in the device pane very quickly.

I don't recall adding that file and sure enough, checking an old backup of my 660, it's always been there. I have some other gpi files in addition to poi.gpi but they don't seem to cause problems.

EDIT: alandb in the nuvi forum at gpspassion pointed me in the right direction. Thanks!

-dan

You beat me to it. The file 006D135900.gpi which contains airport custom POIs is indeed the culprit. If you change .gpi in the filename to something else, BaseCamp won't crash. We are planning on releasing a fix to this and a couple of other issues in the next few weeks, but the exact day is up in the air. Sorry for the inconvenience.