BaseCamp 4.3.0.1 BETA is now available

Continues to crash when panning & zooming with BirdsEye Imagery on the map.

Categories

The following was observed with Mac BaseCamp and Mapsource 6.13.7

It appears that the new categories do not work with older units, specifically my GPSmap 478. There is however something very weird going on that I'll try and explain.

I have a very large waypoint collection that was (mostly) categorized in MapSource. In the beginning of BaseCamp I imported these waypoints but still used MapSource to maintain the master waypoint file/collection because Of BaseCamp's lack of category support. At some point in the past I connected both of my 478 and my 376C to BaseCamp and imported more waypoints that were categorized on the units, mostly from trips. These units have all been connected to BaseCamp multiple times, points, routes and tracks back and forth, the usual usage. Because BaseCamp had no category support I found other less elegant ways to sort points, and was overjoyed to see waypoint categories now supported.

In preparation I deleted all of the waypoints on the device and then deleted all of the device waypoint categories. I then categorized a sample of waypoints in BaseCamp with one, two and some with three newly created category names that had never existed on a device. I uploaded these to the device, deleted them from BaseCamp, and checked the BaseCamp connected device. The waypoints were listed with the new categories. Now it gets weird.

Checking the unit itself I found that while the waypoints had loaded to the device none of the waypoint categories had. In addition, all of the categories that had been originally deleted from the device had re-appeared. I tried this again with the same results. I then discovered that if I uploaded a waypoint that was originally categorized in MapSource or the device, even though the waypoint showed nothing in the category section of BaseCamp, not only did this category show up correctly on the device, all of the deleted categories re-appeared.

Somehow BaseCamp must be have been reading and storing the category information from these old waypoints and these devices, and has been for some time. If so, why isn't the upload to device working from the new data?

Edit:

Another data point. I completely re-named all of my categories in MapSource, re categorized a sample, deleted all waypoints and categories on the device and reloaded the sample waypoints with the new categories. This created device categories that matched those of the waypoints. I then connected the device to BaseCamp and imported these waypoints. None of the categories were visible in BaseCamp or on the device using BaseCamp. They still showed on the device itself. I then disconnected the device, deleted all waypoints and categories and powered the unit off. Powered on, reconnected to BaseCamp, and uploaded one of the sample waypoints. The device waypoint category list was completely re-created even though the sample waypoint only contained 2 categories. ????? :confused: Experimentation continues.

Edit 2

Categories created in BaseCamp and exported, or imported into BaseCamp, do not transfer in .gdb files. Only .gpx seems to be supported. And only the latest version at that. Earlier versions of MapSource do not seem to be supported.

First launch and selecting "Begin to use Basecamp" it crashed.
Second attempt it works fine. After I am done with a route I quit normally.
Today when I start it says my file is corrupt as well as the backup.
Now all my waypoints and routes are stored under "My collection/Unlisted data".
No big deal.

I use Mac OS X 10.9.3. 13D21.

I have just give it a try. I could not export the list I was working on... Got a message list too big. The gpx file of 16000 waypoints is 3.1mb. Back to 4.2.4 I just perform save/export as usual.
As Usual yes and No the size of the exported file went from 3.1 to 6.2gb ???

On OS X standard feature for selecting data is click and swipe the cursor across the data to create a multi-select condition. This still doesn't work in the List data pane on Mac-BC. Ironically enough, it does work in Win-BC. Could you please add this system feature?

Still corrupting Folder Data file upon install first start. I've installed and deleted and reinstalled four times only one of which started up without giving the "corrupted Folder Data file" message.

Bug

When deleting imported data, where a new list has been created, the list and data within are deleted but there is no option provided to delete the data from the collection. Nor does this orphaned data show up in the Unlisted Data folder. It must be tracked down in the collection and deleted.

A couple of irritating bugs

I am running on an iMac, 20 inch, mid 2007 with a 2.4 GHz Intel Core 2 Duo with 4 GB of 667 Mhz DDR2 memory using an ATI Radeon HD 2600 Pro 256 graphics all under OS X 10.9.2(13C64)

I recently upgraded to the 4.3.0.1 Beta after backing up my data. After the install I opened the beta and it seemed to be ok.

Today was the 2nd time I opened the beta and this time it came up with this error: "Your list data file is corrupted, using the back up file" I clicked on continue and everything seemed to be ok.

My purpose was to evaluate different routes from 11 Stoney Brook Drive, Waterford CT (already in as a way-point) to Table Rock State Park in Branson MO.

Using the mouse I moved the 11 SBD waypoint into an otherwise empty list named General.

Then I did a search from the upper right hand corner searchbox for "Table Rock State Park, Branson MO"

The search started and the map pane switched almost immediately to the general area of the State Park but the search continued.

I cancelled the search, scrolled the map window down to the park entrance, zoomed in using the plus key and created a waypoint at the intersection.

Next I used the mouse to drag the newly created waypoint to the General list, selected both waypoints, right clicked and created a route.

Next I moused over to the still open newly created waypoint window and changed the name to Table Rock State Park and hit enter. After a moment BaseCamp Beta crashed!

I reopened it and now got the message: "Your List data file is corrupted, and its backup file is corrupted" Not a problem I thought :) I'll just restore from my backup.

Alas, restoring from the backup did not restore my lists! All my data seems to be there but its all unlisted. I tried another restore from a different backup file and that too did not restore my lists :(

EDIT: Curiouser and curiouser! After composing the first part of this screed I went back and reopened BaseCamp Beta, again it showed none of my lists. But, I wanted to again restore the most recent backup. I did, restarted the programs and ALL MY LISTS seem to be back! :) :) Go figure?

EDIT2: Lost all the lists again when I closed the app and reopened. Can't seem to get them back by repeating the double restore

Bug:
When browsing and selection via-points in route properties, the selected via-point (one) does not show an Orange dot around it. This is broken in this beta version for both via-points and track points. Please repair.

Multi selection of via or track points change the color of the selected part of the route/track orange, this is still working fine.


Request/Bug 2:
Right mouse click on a via-point in a route on the map does not give me the possibility to delete that via-point. (with tracks the choice now exist) Please add this possibility to do that on an selected route (the "fat" one).

Bug3:
Every second time I started BaseCamp Beta it tells me the listmap database is corrupt. Continuing give me a Library without my list maps and list and all data in My Collection main list. Deleting of the 4.3 database at ~/Library/Application Support/BaseCamp/Garmin/Database/4.3 did the trick (every time).
At first start it will copy my 4.2 database and normaly starts-up with all listmaps and lists. My database consists of 6 BirdsEye's, 650 Waypoints, 2 Geocaches, 129 routes and 315 tracks.

Bug4:
Searching an street in the new address search when using a map from the GPS let's BaseCamp crash (poef and gone, no warnings). If i repeat this with a map which is installed on the computer, then the address is found and no crash of BaseCamp.