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

Crash sending route to Edge 800

Beta is unusable for me as it crashes when transferring to an Edge 800. No probs with standard version.

Using OSX Lion and an up to date Edge :confused:

0 Former Member over 13 years ago

Bad performance as in slow, or a lot of holes in the scene? A temporary fix for the holes would be blasting your tile cache, which can be done in the app either by switching your detail setting on the main map controls or by fiddling with your display feature settings.

. . . .

Clearing your tile cache is a good way to let you keep using/testing the beta, but please don't stop reporting these kinds of issues. We definitely want to know if BaseCamp is rendering out of date/incorrect map data. Our users shouldn't need to use tricks like this :P.

Just a little feedback, I've tried "cache clearing" and it doesn't seem to do much at all once this redraw condition starts.

Cheers,

0 Former Member over 13 years ago

I have not worked with this much.

Redrawing, I get missing squares when I zoom.

Only thing I have done so far is round up the Favorites I keep permanently stored in my Zumo.

Phone numbers... I can't change them either. I can delete them and replace with corrected information. I have not tried to send them back to the Zumo yet.

I am still trying to wrap my head around a way to make MyCollection work for me instead of against me by creating one big mess with no organization. Importing stuff just did not work for me in pre versionn 3 BaseCamp. Afraid to start trying at this point.

0 Former Member over 13 years ago

I have not worked with this much.

Redrawing, I get missing squares when I zoom.

Only thing I have done so far is round up the Favorites I keep permanently stored in my Zumo.

Phone numbers... I can't change them either. I can delete them and replace with corrected information. I have not tried to send them back to the Zumo yet.

I am still trying to wrap my head around a way to make MyCollection work for me instead of against me by creating one big mess with no organization. Importing stuff just did not work for me in pre versionn 3 BaseCamp. Afraid to start trying at this point.

Denny,

The current release v3.2.2 and the Beta v3.3.0.2 both support organizing your data in the database (My Collection). You just need to take advantage of the List Folder's and List's.

Please do check out if your "Favorites" (waypoints) will return to the zumo with Contact Info intact. I don't have my zumo any longer so I can't check that one and my Montana doesn't yet support the extended waypoint attributes.

Cheers,

0 Former Member over 13 years ago

Who is going to change?

BaseCamp supports Custom Waypoint Symbols and various Garmin GPS's support Custom Waypoint Symbols. Aside from the image format (GPS's require BMP no larger than 24x24pix) the only difference is:

BaseCamp writes the GPX as:

<sym> Custom 2 </sym>

and my Montana writes the GPX as:

<sym> 2 </sys>

So, my question is - who's going to change so that Custom Symbols work between BaseCamp and Garmin GPS's?

Cheers,

0 Killtimer_ over 13 years ago

So, my question is - who's going to change so that Custom Symbols work between BaseCamp and Garmin GPS's?

Cheers,

As it stands it works fine with my 478 and 376. I really hope fixing one does not break the other.

0 Former Member over 13 years ago

As it stands it works fine with my 478 and 376. I really hope fixing one does not break the other.

I knew that "Custom #" syntax look familiar. :o

So, it's back to when is BaseCamp going to be "smart enough" to recognize which Garmin XSD should be used on any attached device?

Cheers,

0 Killtimer_ over 13 years ago

Feature Request: Context Menu Items.

Would it be possible to include the <File_Export> command in the context (right click) menu when lists or folders are selected?

0 Former Member over 13 years ago

Would it be possible to include the <File_Export> command in the context (right click) menu when lists or folders are selected?

The File menu has that option for the current list/folder selection already and has a hotkey (cmd + S). Our context menus are a bit on the crowded side already; is there some functionality that adding this option to the context menu will add for you?

0 Former Member over 13 years ago

I knew that "Custom #" syntax look familiar. :o

So, it's back to when is BaseCamp going to be "smart enough" to recognize which Garmin XSD should be used on any attached device?

Cheers,

We do that already. That's why proximity waypoints work when sent to a Montana (but not its SD card, at least in the current beta build). Thanks for reporting this custom wpt issue. I'll see what we can do.