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.2.0.10 Beta posted

Added ability to add and move track points using the selector tool.
Changed hand tool to act more like the selector tool when clicking and double clicking on user data and map points.
Fixed routing.
Fixed issue that caused BaseCamp to freeze on start up.
Fixed issue that caused a crash after picking 'Use Backup' at start up.
BirdsEye should work now.

This solves two of the more talked about issues: routing and the freezing on startup. It also adds two new features that we'd like to get comments on: selection using the hand tool and track editing using the selector tool. Also if you have BirdsEye, be sure to upgrade your unit's firmware and download imagery. You can now set the order in which the different BirdsEye images and Garmin Custom Maps are drawn.

We have not been able to recreate the Backup and Restore issue and we had a server outage last week in which we lost some of the posted crashes. If BaseCamp crashes after a restore, please post the crash and say Restore Crash in the problem description.

http://www8.garmin.com/support/download_details.jsp?id=5285

Edit: Because of a short-coming with our server, BaseCamp 3.2.0.10 cannot be distributed through autoupdate. You will need to manually download it using the above link.

0 Killtimer_ over 14 years ago

It is based on average speeds for each type of road. Being able to override the default is a MapSource feature that has never made it over because of the complexity for the user. I can't say we have plans to resurrect it, but we will keep it in mind.

Please do. The concept of "average speed" for any given road type is really a problem for may of your users. I know of many people who use MapSource for planning for this feature alone, rally participants for example.

0 Former Member over 14 years ago

I agree with KILLTIMER.

There is very little value in "average" settings. The most often remark some of us old-timers hear is that the new "stuff" (GPS's, BaseCamp) are dumbing down. Isn't it the mark of good software that hides complexity from the user? Yet, still allows the "experienced user" to access the functions that provide more detailed information.

I can understand the complexity of having so many variables introduced into the routing algorithm's but if the user can't get usable information from the tool, they won't use the tool.

I dread the moaning that will come from many Garmin customers when they realize that Mapsource is on it's way to retirement one of these days.

0 Former Member over 14 years ago

Works on Startup

The lastest beta solved the issue on startup - thank you.

0 Former Member over 14 years ago

Hide Map Features

I tried the Hide Map Features option but it isn't working as I had expected. I unchecked most of the POIs except for Campground/RV Park under Lodging. However I don't see any campgrounds on the map even though Garmin knows they are there. Am I doing something wrong?

0 Former Member over 14 years ago

Working on my installation with CNNA and Topo US 24K. When I un-check Lodging, the "Tent-symbles" and all other "Lodging types" no-show.

But, what maps are you using? Not sure what you mean by "Garmin knows they are there". Give us a specific example (lat/lon) of a Campground that should be visible under normal conditions and isn't.

0 Former Member over 14 years ago

Routing Problem

I have created a small route in Lancashire, UK, with just a start point and end point, motorcycling profile. (Small item: the info page for the route says "Transportation Method: Car". Car?)

I'm using older maps (City Navigator Europe 2009) because Garmin has ceased publishing updates for my Quest. Here's the route map:

Two issues: the silly route south turning into direct routing followed by the U-turn, and then direct-routing to the destination straight across the sea.

Here's the route:

http://www.collinacre.plus.com/Basecamp/Lancashire Route.gpx

0 Killtimer_ over 14 years ago

Have you tried re-calculation the route? I just opened your file in BaseCamp with the most recent European mapset and got the same result you show. Re-calculation provided this.

0 Former Member over 14 years ago

Re-calculated several times. No change, still a silly route.

Since it works for you I conclude therefore it's an issue with the (non-NT) 2009 maps, but for the beta version only. The route works fine in the release Basecamp using the same maps.

0 azdrmn over 14 years ago

Please do. The concept of "average speed" for any given road type is really a problem for may of your users. I know of many people who use MapSource for planning for this feature alone, rally participants for example.

I should have been more clear about why we haven't picked up this feature. The speeds that the user inputs in MapSource and PC BaseCamp only change the ETA. They do not affect the actual routing. This wasn't always true and I don't know why that change was made, but changing the time of travel didn't seem like enough to warrant the complexity.

0 Killtimer_ over 14 years ago

I should have been more clear about why we haven't picked up this feature. The speeds that the user inputs in MapSource and PC BaseCamp only change the ETA. They do not affect the actual routing. This wasn't always true and I don't know why that change was made, but changing the time of travel didn't seem like enough to warrant the complexity.

;) It's the ETA that's important to me. The routing is something I do myself as my GPS units will accept custom routes without any re-calculation. The ETA component can be important if you're comparing 2 or 3 route options.

The only time I use auto routing is when my wife wants to know where WalMart is. :D