BaseCamp for Mac software version 3.0.2

The dropdown menu for maps now in Basecamp includes both the device map and the hard disk map for the same area using the same name.

That is a bug and will be fixed in the next version. Thanks for the feedback.

I'm not seeing much improvement in this latest version. With about 10 birdseye maps installed, and with CNNA 2011, with or without the gps connected, I'm still seeing startup times that are the same as previously - one minute and 45 seconds or more. This is probably the longest start up time of any of the programs I have installed, including some much more hardware and memory intensive ones. Not to mention the sluggish delays that accompany trying to do anything, even basic things, once the program has started.

So is there anything I (we?) can do to streamline the startup and operation? Short of uninstalling all the maps and such that are what this program is about?

No replies? Please - there must be some kind of remedy to this.

Edit - After some experimentation, I've found that deleting the birdseye maps from the computer after transferring them to the gps helps basecamp load a LOT faster. Of course, if the gps is hooked up to the computer, it still takes forever to read it, but then you have access to the birdseye images you've already downloaded.

This is an inelegant solution, garmin people, and I still expect the memory problems to be fixed, hopefully soon. In the meantime, you should seriously consider rebates or partial credit for your birdseye customers, or at least consider these first few months as freebies and extend our subscription period. Charging us for a product we can't use properly is the sort of thing class action lawsuits are made of, and we don't want that to happen. Perhaps the situation is a lot better in the PC side of things, I don't know - but here in mac land, basecamp and birdseye images do NOT work well adequately.

I can say that a huge amount of work went into reducing the memory footprint of BirdsEye images in 3.0.2 so it wouldn't crash. While speed enhancement did take a back seat to robustness, less use of virtual memory should cause a significant improvement in performance. It did in our testing. We have been able to load 4X more images without issues in BaseCamp 3.0.2 than 3.0.1. Obviously your results may vary.

However, most of the changes in 3.0.2 were tweaks to attack measured inefficiencies. In the next feature release, we are planning a fundamental change to the way BirdsEye imagery is stored which should improve both memory and speed.

In the meantime, I would suggest you do what you did. If BirdsEye imagery is causing your system to be too slow, move some of your BirdsEye images to your device or an SD card and don't plug them in unless you need them. I agree that this is inelegant, but should be effective until the next release.

Thanks for the reply! Looking forward to a new version! :)

@SDUCK

Have you tried increasing the 'Disk Cache Size' setting in the preferences for BaseCamp. I don't use BirdsEye images so I don't know if it would make a difference with them but I did notice a increase in map performance when I increased the Disk Cache Size.