Mac/Windows Software

Basecamp Mac BaseCamp 3.3.0.2 beta posted

This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

BaseCamp 3.3.0.2 beta posted

azdrmn over 13 years ago

Just to prove that we are listening, we are releasing 3.3.0.2 which fixes several issues that have been reported from the first beta.

The beta is downloadable from: http://developer.garmin.com/apps/BC/BaseCamp_3.3.0.2_Beta.dmg. If you are already running BaseCamp 3.3.0.1, it should automatically update to 3.3.0.2.

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

Fixed + and - to correctly zoom in and out
Fixed crash that could occur when ejecting a device
Fixed issue where columns in the Detailed User Data View could get repeated
Fixed issue where Undo and holding the Alt Key would terminate the current route creation using the Route Tool
Fixed to be able to read waypoint categories from newer devices.
Added ability to edit phone numbers in the Waypoint Contact Info tab.
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
Fixed any profiles from BaseCamp 3.2 that have invalid routing preferences (ie invalid vehicle types and incorrect avoidances)

Known Issues:

Proximity waypoints sent to SD cards in outdoor devices will not have the proximity show up in the device. Sending the waypoints directly to the device does work.
Reading routes from a Zumo 660 may cause a crash. Issues is being investigated, but the circumstances seem to be rare.

Edit: Link changed to a different server that should work

0 Former Member over 13 years ago

KML/KMZ Import

Is this version suppose to import KMZ/L files? This works with the BC-Windows but not with Mac. BC-Mac sees the KMZ/L files as a "Readable" file and starts the import process but nothing happens after that.

Cheers,

0 azdrmn over 13 years ago

Is this version suppose to import KMZ/L files? This works with the BC-Windows but not with Mac. BC-Mac sees the KMZ/L files as a "Readable" file and starts the import process but nothing happens after that.

Cheers,

Mac BaseCamp does import KML/Z files. The KMZ file you sent with the 3000+ mile track in it is causing problems though. We may or may not be able to make a change to handle tracks that big in 3.3.

0 Former Member over 13 years ago

Mac BaseCamp does import KML/Z files. The KMZ file you sent with the 3000+ mile track in it is causing problems though. We may or may not be able to make a change to handle tracks that big in 3.3.

:confused: That KMZ file should have had 21 Tracks in it. The total distance covered might have been close to 10K miles but no one Track was longer than ~500 miles. :confused: Why would it work on BC-W and not BC-M - don't they use the same conversion plug-in?

Cheers,

0 danham_ over 13 years ago

Problem with micro SD card

I have been using my micro SD card in my zumo 660 throughout the beta testing, but suddenly this morning BC beta 3.3.0.2 won't read it.

The card mounts fine on my desktop (OS 10.7.2) and I can see all its folders and files. I am certain I could drag routes to it using the previous beta and am pretty sure it worked with 3.3.0.2 as well, but no go today.

It appears in the device window but the round arrow keeps turning forever and no data from the card appears in the lower window in the left pane of BC. And I'm certain I never previously saw the warning BC now displays when I try to quit that data is still transferring to/from the card.

I exported the route I wanted to use as a GPX and dragged it to the GPX folder on the card and it transferred just fine to the card and then imported to my zumo 660, other than mysteriously changing two "don't alert" shaping points back to flagged and announced vias.

-dan

0 Former Member over 13 years ago

Small issue - when I use the hot keys to switch between the any Tool and the Hand Tool, the Icon on the Tool Bar doesn't shift from previous Tool to Hand. The function on the Map does switch to Hand - just the Icon does not change on the Tool Bar.

Cheers,

0 Former Member over 13 years ago

I have been using my micro SD card in my zumo 660 throughout the beta testing, but suddenly this morning BC beta 3.3.0.2 won't read it.

The card mounts fine on my desktop (OS 10.7.2) and I can see all its folders and files. I am certain I could drag routes to it using the previous beta and am pretty sure it worked with 3.3.0.2 as well, but no go today.

It appears in the device window but the round arrow keeps turning forever and no data from the card appears in the lower window in the left pane of BC. And I'm certain I never previously saw the warning BC now displays when I try to quit that data is still transferring to/from the card.

I exported the route I wanted to use as a GPX and dragged it to the GPX folder on the card and it transferred just fine to the card and then imported to my zumo 660, other than mysteriously changing two "don't alert" shaping points back to flagged and announced vias.

-dan

Exact same condition here on my Montana. Just started two days ago for me. I had to remove BaseCamp Beta and reinstall to cure the problem. I suppose now I have to wait and see if it comes back for it to be "repeatable".

When I would exit BaseCamp (with the afore mentioned condition) I would get a popup notification that BaseCamp was in process of a Transfer and data my be lost....blah, blah. Closing BC had no effect on my µSD card or it's data.

Sounds like a . . .Time Bomb!!! :eek:

Cheers,

0 danham_ over 13 years ago

More info:

If I attempt to repair the 4GB micro SD card using Disk Utility, it does not report errors but does end up fixing what looks like some stray clusters. So I copied all my data and reformatted the card. Bingo, it shows up just fine in BC. So I transferred a medium-size list to it in BC, no problem, and that list and all its content appears in the lower pane when the SD card is selected.

But quit BC and re-launch and the SD card will no longer load. Endless spinning arrow again.

So once BC 3.3.0.2 "touches" the card, it's toast, at least for use with the beta.

Just to double-check, I then fired up BC 3.2.2 and the card loaded right up no problem.

-dan

0 Former Member over 13 years ago

More info:

If I attempt to repair the 4GB micro SD card using Disk Utility, it does not report errors but does end up fixing what looks like some stray clusters. So I copied all my data and reformatted the card. Bingo, it shows up just fine in BC. So I transferred a medium-size list to it in BC, no problem, and that list and all its content appears in the lower pane when the SD card is selected.

But quit BC and re-launch and the SD card will no longer load. Endless spinning arrow again.

So once BC 3.3.0.2 "touches" the card, it's toast, at least for use with the beta.

Just to double-check, I then fired up BC 3.2.2 and the card loaded right up no problem.

-dan

Confirmed. And, since v3.3.0.2 is in eternal "transfer" mode with the µSD card, the card can't be Ejected.

Cheers,

0 danham_ over 13 years ago

One more data point: I have a 16GB SD card which has never been used since its last FAT 32 format. Pop it into my iMac with BC 3.3.0.2 running and it shows up right away. Transfer some data to it using BC and it all shows up. Quit BC and try to read the card: eternal transfer time again.

So it's apparently not anything to do with the GPS per se; it's in BC.

-dan

0 Former Member over 13 years ago

AS in the previous beta version, I am still having trouble when zooming: there's a big blank square appearing when I zoom in and it takes a long time for the map to re-draw. Like someone else reported, Basecamp crashed when I tried to close it with the map zoomed in, but before the map had time to re-draw (it was taking far too much time and I simply decided to close the application to get out of it).

Same condition here. It's almost unusable at this point and I've re-installed on several occasions. It works fine for awhile and then back to very bad redraw performance. It is a Beta though so I expect it will be dealt with before v3.3.x release time.

Cheers,