BaseCamp 4.3.3 is Now Available

Is "Unlisted Data" a List? If one selects the objects in the Unlisted Data view and selects Delete....



The resulting Warning would suggest that it is.

Nice catch. if it is indeed 'unlisted' data, then what 'lists' can it be deleted from?

My understanding is that 'unlisted' data is present in the BC database, but not referenced in any named list.

Of course it's not a List. But, OK, it could be considered nit-picking. But consider the person struggling to figure out BaseCamp. They've been told that this is a "database" and that Unlisted Data is just a reference to data that is not referenced in any List. Now you tell them that this is a List (by inference). I get questions about this stuff every day and it pains me to explain that the developer that wrote that "Warning" was lazy and used the warning message one would get when deleting data from a real List rather than create a warning specifically for the "Unlisted Data" delete-action: which might have read, "Warning! This action will delete this data from your Library." Notice I used the word delete and not Remove! I hate the use of the term Remove when the action is to DELETE!

Apology for the short rant...

Basecamp 4.3.3 has a bug when using the Travel planner

When a travel is made and corrections are necessary because different locations are wanted, the deletion of the former location ends in a shutdown of the software. The deletion of the total travel plan is having the same result : total shutdown of Basecamp.

BaseCamp is 4.3.3 now available and can be downloaded here:

http://www.garmin.com/support/download_details.jsp?id=4435

This release does not support XP.

Installation of this version will overwrite your previous BaseCamp installation.

Here are the changes made in this version:

• Fixed issue when importing a file and errors or warnings are encountered in the file
  
• Fixed issue with adding or editing an activity profile
  
• Fixed issue with changing the cover photo of an Adventure
  
• Fixed issue when joining tracks
  

Post here if you have questions.

The non-English language version of the software will be available through the in-application software update check shortly.

Please post any bugs you may find here.

Thank you all in advance for any feedback you may have.

Issue: BaseCamp 4.3.3 recalculating an existing route, using the same map, is creating a longer route, having duplicate route segments and sometimes loops.

To reproduce:
- Create a Route
- Map = OpenStreetMap
- Route Preference = Faster Time
- Feature Type Avoidances = U-Turns

Test (1):
Recalculate Route using BaseCamp 4.2.5:
Distance = 80 km (for instance)

Test (2):
Recalculate Route using BaseCamp 4.3.3:
Distance = 100 km (for instance)

Map is identical, Route is identical, only BaseCamp version is different.

Symptoms:

1. Route is reverting back to its own trail to a via-point.
See direction arrows. To find these duplicate route segments you will have to follow the route completely and watch arrows directions: a backwards directing arrow indicates a duplicate route segment.

2. Route is – sometimes, not always, only if possible - creating a loop.

To demonstrate:



To resolve: remove the viapoint that is causing the error.



In MapSource this "error" will not occur.

To reproduce:

- Map = OpenStreetMap
http://www.openfietsmap.nl/downloads/bnl_full
OpenFietsMap.zip

- Route attached:

Are you willing to attach a GPX file of your route data here? If not we have an e-mail address you can send it to. This way I can look at the data itself and see what's happening. Let me know. Thanks for the feedback.

To reproduce BaseCamp_Routing_Error:

- Map = OpenStreetMap
http://www.openfietsmap.nl/downloads/bnl_full
OpenFietsMap.zip

- Route attached as gpx:



Route is most simple route to reproduce and (almost) identical to:

... (duplicate post) ...

Basecamp downloaded 4.3.3 and I stupidly decided to upgrade. And surprise it failed with the missing dcll message. So have uninstalled Basecamp and removed the x86 Basecamp folder and downloaded 4.3.3 again. And now it starts to initialise, and then nothing. Checking task manager it spends a while doing something, before disappearing from the processes list.

Any ideas on what to do?

Which OS are you using?