BaseCamp 3.2.2 released

There's a new wrinkle in the loading at full zoom-out bug. Today I was working to clean up some routes with shaping points in them (my zumo chokes on these) and when doing a recalc BaseCamp displayed an error message and asked if I wanted to report it. I said yes and typed a summary in the box and clicked OK. At that point the route became a straight line and no matter what I did it would not recalc.

After a lot of detective work I =think= the problem was that BC "forgot" which map was selected and assumed Topo West, even though CN NT NA 2012.20 was being displayed on the screen at the time of the error. That would explain the straight lines.

I say this because after this error, every time I relaunched BC (in the course of restoring to previous data versions, because I was beginning to panic as every single route recalc'd as a straight line), it would load zoomed way out, so I couldn't immediately tell that it had chosen Topo West.

Once I manually re-selected CN NT NA 2012.20 all the routes loaded properly and the original one I was working on recalc'd properly too.

-dan

I find both 3.2.1 and 3.2.2 to be painfully slow to launch on my MacBook. What's odd is that 3.2.1 was loading fine until about a week ago, at which time it began the crash-on-launch syndrome and I assumed it was due to corrupt track segment files. I deleted those, and prefs, even started with a fresh database, and finally got it to load, but v e r y slowly.

So when 3.2.2 came along I hoped that would be the cure. It does not crash on launch, but takes a few minutes -- not seconds -- to load. It was never a launch speed demon, but something is broken here. (EDIT: I just timed it at 2:19 to load from when the icon is clicked.)

My MacBook is a 2.4 gHz Core 2 Duo with 2GB of RAM running 10.5.8.

BC is working fine on my i3 iMac under 10.6.8.

A change was made to BaseCamp 3.2 specifically to make start up times shorter, so this is surprising. If you'd be willing to do a backup of your data and email it to me, we can see if this is an issue we can fix.

A change was made to BaseCamp 3.2 specifically to make start up times shorter, so this is surprising. If you'd be willing to do a backup of your data and email it to me, we can see if this is an issue we can fix.

Will do. It's starting up practically instantly on my i3 iMac, so I'll have to dig out my laptop where it takes 2+ minutes and grab a backup.

-dan

UPDATE: As part of some general housekeeping and sync'ing of info between my desktop & laptop, I removed several older maps from BC on my laptop and restored from a recent backup from my desktop, plus installed CN NT NA 2012.20.

The result? BC starts up very quickly now on my MacBook, so either I had too much junk in there or a file was corrupt.

-dan

Update: BaseCamp 3.2.2 was finally released on the App Store.

When I start it it's asking to select an Activity profile but there are none in the list so I'm being forced to use Task Manager to exit.

I also found this confusing ths first time I ran Basecamp. One of the items on the screen is actually a drop down menu, but this is far from obvious (I can't go back and check the detail, this only appears on the first run). Selecting an item from the list lets you go on and use Basecamp.

Martin

New try: Crash report included

Solved, something to do with Mac identification and networkdevice settings. My "Mac" PC is now running better than ever. My AppStore problems are also solved.

Picks and Pans

Just got home from a 15 day motorcycle trip covering over 5000 miles. 12 planned routes done in MapSource but administered in BaseCamp on my MacBook air.. Some observations.

BaseCamp is getting close as a planner but still (desperately) needs custom avoidances and better route duration estimation that would be gained by user scalable driving speeds on every road type in City Nav maps.

The ability to edit a single route directly on the attached GPS is a HUGE undocumented feature, discovered by accident. Well done.

The "Create Track form Route" feature is an excellent one. As I keep all of my rides as tracks this feature saved me twice on this trip.

Track editing in BaseCamp needs the tools present in MapSource to be truly useable.

Search needs work and simplification. A default search setting that would let you pick one or two POI classifications would be ideal. That way it's easy to search for Fuel and Food in a hurry. Ideally, I only need three or four POI classes 95% of the time.

And now the kicker. I've reported trouble with track files loosing time stamp data in the past and thought it had been solved. Apparently not.

"2011_09Tracks" is a file I exported from BaseCamp so I could clean up the tracks in MapSource. There are three different track types. Full data recorded tracks from my GPS, one day's tracks that were a saved file from the GPS (missing time stamps), and two days tracks that were created from that days routes.

"Spam Tracks" is the cleaned and combined track of the trip. It was then imported back into BaseCamp. At this or some earlier point all of the time and date data from the BaseCamp copies was lost, except for data on the first day or first track. As well, all user selected colors get set to 'unknown", again with the exception of the first track.

"Example.gpx and Example.gdb are the BaseCamp export. Another interesting sidebar. "Example.gpx crashes MapSource 6.13.7 but loads in 6.16.3 :confused: An exported "Example.gdb file loads fine in all flavors of MapSource.

Any insight would be appreciated.

Edit:
.gdb file attachment is not supported :confused: OK, I tried a .gpx upload and it was rejected due to a security token missing. <sigh>

Files can be found Here. in the BaseCamp folder.