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

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 Killtimer_ over 13 years ago

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,

I've seen it as well. In addition I occasionally get the following anomoly when switching between activities that have very different display feature settings. The area affected appears to be same square segment that is not redrawn once in a while. In the grabs below, notice how the paved road is not rendered properly between the two activities.

The difference in display properties is "Paved Roads", and yes, Hwy 27 is paved through this area. I drive it once a week. The anomoly is not specific to any one location that I've found.

CNNT 2012.3
.7 and .3 mile scale.

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

Thanks for the info, Dans :). We've discovered a bug that keeps us from receiving categories from Removable Media. I believe this would have happened in 3.3.0.1 as well, if you managed to get categories onto an SD card. That was harder to do in 3.3.0.1 though. This will be fixed in the next release.

0 danham_ over 13 years ago

Good news ... I think [g].

I did not have any categories on the micro SD card, just routes -- some from earlier versions of BC and a few from the betas.

-dan

0 Former Member over 13 years ago

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,

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.

@KILLTIMER:
I think your problem is pretty similar: tiles getting cached when they shouldn't be. This probably happens when you're clicking through the checkboxes in your display feature settings, toggling things off and on again to see what they affect. Each time you do this it clears the tile cache, and each time you do it the tile renderer gets busier and busier with its pile of tiles until it gets behind and returns a tile for the wrong display feature settings late enough that our code assumes it's for the new ones.

If that's right, a temporary fix for your issue would be to wait for the scene to finish drawing before you change your display settings next time, or just change the detail level since that tends to clear the tile cache entirely.

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.

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.

@KILLTIMER:
I think your problem is pretty similar: tiles getting cached when they shouldn't be. This probably happens when you're clicking through the checkboxes in your display feature settings, toggling things off and on again to see what they affect. Each time you do this it clears the tile cache, and each time you do it the tile renderer gets busier and busier with its pile of tiles until it gets behind and returns a tile for the wrong display feature settings late enough that our code assumes it's for the new ones.

If that's right, a temporary fix for your issue would be to wait for the scene to finish drawing before you change your display settings next time, or just change the detail level since that tends to clear the tile cache entirely.

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.

I'm will to work with Beta code in hopes of getting the Track Edit Tools from MapSource. Not being able to easily select, copy/paste Track points is killing me - especially when BC-win is heading that direction.

Cheers,

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.

@KILLTIMER:
I think your problem is pretty similar: tiles getting cached when they shouldn't be. This probably happens when you're clicking through the checkboxes in your display feature settings, toggling things off and on again to see what they affect. Each time you do this it clears the tile cache, and each time you do it the tile renderer gets busier and busier with its pile of tiles until it gets behind and returns a tile for the wrong display feature settings late enough that our code assumes it's for the new ones.

If that's right, a temporary fix for your issue would be to wait for the scene to finish drawing before you change your display settings next time, or just change the detail level since that tends to clear the tile cache entirely.

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.

I'm willing to work with Beta code in hopes of getting the Track Edit Tools from MapSource. ;)

Not being able to easily select, copy/paste Track points is killing me - especially when BC-win is heading that direction. :o

Cheers,

0 Former Member over 13 years ago

Added ability to edit phone numbers in the Waypoint Contact Info tab.

Still not working for me. Click to Edit highlights and allows change but change does not stick.

Cheers,

0 Killtimer_ over 13 years ago

Still not working for me. Click to Edit highlights and allows change but change does not stick.

Cheers,

I'm seeing the same thing.

0 PSEABOLT over 13 years ago

Waypoint comment, you guys are into Mac Development

Looks like the comments field under waypoints dialog is a mini word processor. I pasted a comment from the web and it turned all my comments into large red font. Finally figured you can select the text in comment you want to change, right click and select font to totally customize fonts down to each letter. By default it changes all waypoints to the style set but looks like you can just change a single comment field of each waypoints but I did not test this feature.

0 Former Member over 13 years ago

Looks like the comments field under waypoints dialog is a mini word processor. I pasted a comment from the web and it turned all my comments into large red font. Finally figured you can select the text in comment you want to change, right click and select font to totally customize fonts down to each letter. By default it changes all waypoints to the style set but looks like you can just change a single comment field of each waypoints but I did not test this feature.

Whatever text style you apply to one Comment field applies to all.

The zumo's supported HTML in the Comments field.

Cheers,