HELP - Didn't know about "do not duplicate tracks" in 3.2.1- now Basecamp crashes

First of all, I apologize for the (huge) inconvenience.

I am afraid you probably lost track data beyond the basic data (position data), stuff like elevation, speed, heart-rate etc. might be lost for some of your tracks.

Do you still have the original tracks on your GPS? I realize this will only be of little comfort, because of the work you've done on them, but at least you could re-create your work.

If you are not in a great hurry, you could wait for the release of BaseCamp 3.2.2. Check http://www8.garmin.com/support/download_details.jsp?id=4435 periodically, or these forums, it should be out very soon. 3.2.2 should fix up your data as much as it can, but for tracks that became corrupted by duplication you would lose everything but the basic track data. Duplication will also not corrupt data anymore in 3.2.2.

If you are in a big hurry, let me know and I will try to figure out a way for you to use BC 3.1.3 with your data, or clear out the faulty files so you can start over. But that will probably be somewhat technical.

Again, big apologies. We do take great measures to secure that user data is safe, but this one just slipped through the cracks. :(

Thanks for the reply.

I ended up isolating the "bad" tracks - the ones that were created by duplicating others then paring them down - and then re-creating them all but without using the duplication function.

I did loose some data (elevation profile) for a lot of them, but the position info was the most important.

I see that 3.2.2 is available now, so I'm about to go and install that and hopefully all will be well.

I did notice something else, which might be best approached in a seperate thread but I'll chuck it in here for now.

When I sent all 80+ tracks to my Oregon 450 (I grouped them in BC then used right-click send to - Oregon 450) - they all showed up on the Oregon as cyan, which is pretty frustrating as I had spent a lot of time in BC colour-coding them for difficulty using a scheme of 5 different colours.

Am I missing something?

Thanks

You can help isolate where the problem with the transfer might be. Export some of the tracks to a GPX file. Make it so you should have a mix of difficulty colours, preferably none with cyan.

Now open the GPX file with your favorite text editor and see what the colour in the track data is. Finding the colour descriptor in each track entry should be obvious if it's there. Or equally obvious if it is absent.

If Basecamp is putting the proper colour information into the GPX file it is likely that it is also sending it to the device correctly. That would mean that the device is ignoring it and using cyan as a default. This is not absolute proof but it helps narrow down the possibilities.

If you don't want to go digging through a GPX file with your text editor, you could also test the GPX file by loading it into Mapsource and see if the colours came across properly.

...ken...

The color issue might be related to this thread: https://forums.garmin.com/showthread.php?t=19960.

Thanks for the reply.

I ended up isolating the "bad" tracks - the ones that were created by duplicating others then paring them down - and then re-creating them all but without using the duplication function.

I did loose some data (elevation profile) for a lot of them, but the position info was the most important.

I see that 3.2.2 is available now, so I'm about to go and install that and hopefully all will be well.

Yes, unless you lost some position data during a crash, position data should not have been lost. It was only stuff like elevation, heart-rate, etc. that would have been incorrectly duplicated.

3.2.2 is available, and it should duplicate tracks correctly.

Again, we apologize for the trouble.