BaseCamp 4.4.2 Is Now Available

The straight lines is still an open issue. We fixed crashes as the priority. We are working to resolve this issue as well. Thank you for all the patience.

Three weeks have passed. Any news on the straight line issue?

It's extra relevant since we now have a City Navigator update that will automatically install the latest basecamp-version.

When is the straight line problem expected to be solved?

We have a release coming out soon. I do not know the exact date but we are aware of this issue and we are working to resolve. Thank you all for your continued patience.

I have a two small functionality requests. Can you add the ability to sort the list generated by the search function? The list as it is now is only sorted by distance from map center.
If I'm looking for a Holiday Inn, for example, I need to manually scan the entire list containing maybe several Holiday Inns to find the one I'm looking for.
I'd also like the ability to copy the search result string to the clipboard. I can then paste the restaurant or whatever name into Google to search for additional info.

Thanks.

See post 2 above yours.

However I don't believe this is going to change your devices behaviour, routes created on Basecamp transfer just fine on my GPS. You don't say which device you have but unless it knows you're in a big rig it can't possibly anticipate your problems.

Read my post. I'm not blaming the device ... just saying I don't *believe* this will change your problem. Course you can wait and see ... entirely up to you :)

I've had U-turn avoidance checked in BC and on my 550 for years, but it is common for either to require a U-turn anyway. In BC I set shaping points to correct, but while following a route and deviating for some reason, it commonly says to make a U-turn anyway. I don't think the U-turn avoidance has ever worked properly in either BC or devices. YMMV.

Agreed, I think the fact is it's 'avoid' rather than 'prohibit' so if it has to be a U-turn then you get one ...

I don't have u-Turn avoidance on because in the US (especially in cities) they're are often required (when exiting interstates, turning left off divided roads etc). Of course it depends upon Garmin's definition of "U-Turn".

...Should have quoted Sussamb, that's who this response is intended for, Stuart got in there while I was typing...) Well, I would agree in the case of, for example, going to a waypoint that's on a dead-end road, not any choice there. But in my experience, BC will suggest a U-turn even if going around a block would add only 2 seconds to the time and would be perfectly reasonable and in fact what you would do in real driving. Who makes a U-turn on a downtown street? So I think that "avoidance" just flat doesn't work. But it's easy to deal with it, so no biggie.

As I said it depends on Garmin's definition of "u-turn". From my experience it seems very broad. My Garmin units tell me to take a "u-turn", on one of my often used routes, when it's actually a 90deg left turn at a stop light. Kinda funny :) I've also seen "make a u-turn" to mean exit right off an interstate, turn left underneath it, and turn left on the access road on the other side.