BaseCamp 3.3.1 (New Features)

Thank you for your feedback.

I am afraid the feature to convert a route from a track isn't supposed to do what you are trying to do. Its purpose is to create a direct route from a track. Normally tracks are very detailed (because they usually are recordings of a trip you have taken) and it wouldn't make sense to convert them to anything but direct routes.

I admit that what you describe could be a valid use-case as well. It's just not something the software is currently made to handle. I'll add this to our list of possible future features, but it might be quite a while till it makes it to BaseCamp.

The default color for tracks (and routes) is definitely doable. I'll add a case for this as well. Again, no promises when this will make it into a release.

default color for tracks (and routes) is definitely doable. I'll add a case for this as well. Again, no promises when this will make it into a release.

I hope you're just kidding about this. Those cases were said to be added months ago. Long enough ago that many of us were half expecting preference settings for default track and route colours might show up in the most recent feature release.

That's not a complaint about the latest release, which contained a ton of stuff. It's just a concern that if the cases are only being added now it means we'll be waiting for a long time to see anything. And we've already been waiting for a very long time.

...ken...

Like I always say, no guarantees when this will make it. Our list of possible features is very, very, very long. It is simply not possible to implement them all in one release.

The more critical we think a feature or bug is, and the more we hear about it on the forums, the more likely it is that we will add it.

Not sure what 'slider bar' you're referring to?

I have BC running on Win 7 and XP and see no difference between the two.

If you're talking about toolbars make sure you have the same ones selected by going to View>Toolbars

The slider bar for road preferences is gone.

You can set specific avoidances for road types now, which should be a bit more straight-forward and is also more in line in how (some of) the units do it.

The slider bar for road preferences is gone.

You can set specific avoidances for road types now, which should be a bit more straight-forward and is also more in line in how (some of) the units do it.

But isn't it still the case that as far as routing preferences, the GPS units do not "talk to" Base Camp, just as they didn't to MapSource? This has always been a complaint of Zumo users anyway, that the Zumo does not have any matching routing settings (custom road speeds, vehicle type, road type preferences, avoidances, etc.), so if a route created in MapSource is downloaded to the unit, and ultimately is recalculated for any reason, either due to an enroute change or off-route auto-recalc, the result can be completely different than what was planned. This has led many Zumo users to conclude that the customization of routing preferences is essentially useless.

In the focus on Base Camp, it seems that Garmin has a chance to do something great here, by making the unit software capable of using identical routing settings as Base Camp, and receiving those settings based on whatever was used to make a route in BC, via Activity Profiles. That is, take a more systems approach. That way, a route would be calculated identically on the unit as it is in BC, since the settings for that route would be identical. What a concept! Is Garmin moving at all toward doing this?

We are moving towards that goal. But it's still a very long way to go.

POI an BC

Why it's impossible to delete POIs in the device with BC?
Handling with tracks, routes and POI would be much easier!
Or is the problem in front of the device? ;)

POIs (unless you've loaded them yourself) are part of the map data, they can't be deleted.