Great Job Garmin!!!

It's a perpetual "WIP."

Nice job on fixing the Arrive/Continue issue, but in the process you've made things worse. If you build a route in BC 4.2.4, exported to a Zumo 660 and run the route, 10 minutes from the time you start the route the 660 will spontaneously recalculate the route and in my case the new route doesn't agree with the route I setup in BC. :mad: If you stop the route and restart it again in 10 minutes (exactly) it will spontaneously recalculate again and screw up the route.

Does anyone around there do any QC before a release?

Not "going to bat" for Garmin here, but I think BaseCamp is a constant "Work-In-Progress." Because it is designed to do so many things, and work with so many different units used for different purposes it presume it must be a nightmare to deliver. The most recent version just destroyed all my track details. (It managed to remove all the times, dates and altitudes of all my tracks, not the critical navigational info, but nevertheless they are things I use to organize.) ~ Fortunately I did have backups of most, but not all.

In general, I must say that over the years they seem to perpetually deliver some very buggy software & firmware. I have the notion that we are their QC department and this forum (along with feedback on their own site) is the mechanism for "fixing broken things."

Can you please send me the route you are having trouble with in the state it is in when you calculate it in BaseCamp before it goes on the Zumo. I can then investigate.

Trakbak, I would also be interested in seeing the track you are having trouble with as well if you don't mind. Can you send me the original track before it "broke?" If not can you give me your steps to reproduce?

Thanks guys.

Can you please send me the route you are having trouble with in the state it is in when you calculate it in BaseCamp before it goes on the Zumo. I can then investigate.

I'm on the road (using another route) right now, I'll post one this afternoon. it's not just one route, it happened on both routes I used yesterday. we'll see how today's route goes.

I am grateful for your assistance. We did many tests with this and did not see this issue. But if I had specific routes that you're having trouble with that would assist me further. Also the map you are using would be helpful as well.

Thank you.

ducts

Trakbak, I would also be interested in seeing the track you are having trouble with as well if you don't mind. Can you send me the original track before it "broke?" If not can you give me your steps to reproduce?

Thanks guys.

I can, and have broken all of them. They are all current tracks captured/created with the newest firmware on a Montana 650.

Don't know exactly when they "break", but typically I capture all the data from the unit (puts it into a list under the special folder) using "Receive from Device." I then copy (duplicate) the track and move it elsewhere to rename it and change it's track color.

Note: One of the things I also have done is relocated the folders & lists via drag & drop. (Renamed them and/or even moved them within the directory tree while organizing.)

Most of the tracks seem fine unless/until you look at the detailed properties. (They frequently still will show start times after swapping map and data view, even though the details of the individual points of the "non-critical track data" are wiped out.) I noticed on some occasions that when tracks were duplicated into multiple locations, some of the "instances" of the same track still maintained start dates, and I also details (if memory serves me), while other "instances" of the same tracks (in different folders/lists) did not.

I had hoped that by copying the "good" instance back to the unit, I could preserve the data. This turns out to not be true.... :(

Here's the data (before and after).....
I had saved a good version "to the cloud." Turns out that all my tracks in basecamp are now "broken." (missing the detail info) I didn't think they were last time I was using Basecamp earlier today. (I had just fixed the ones by reverting back to the originals.) ~ Incidentally, some of the tracks still show the start dates (like this ~bad one), but are missing all the extra data in the properties pane!



(Both files show start time, but the bad one lacks all the extra property details of individual points.)

It's also worth mentioning that on my copies that show start time (but have lost the details like RUNTRAIL-POWERLINESbad.gpx), when I "right-click" on the track and attempt to "set selected track to map elevation" (under advanced to try and restore elevation detail using the topo in basecamp), elevation data is reloaded into the track, but the start time then disappears...... (try this with RUNTRAIL-POWERLINESbad.gpx) Ironically, the elevation data does restore!

One last thing: I'm wondering whether the "Archive" function on the unit (archived tracks) could have anything to do with this when importing and editing tracks in Basecamp....???? I'm thinking it does not, but the names of archived tracks are stored individually, where the names of "favorite tracks" are combined into one/several files on the unit. ~ I'm going to create a new track, archive it, and then import it and see what happens. First I'll import the track before being archived, then I'll archive it and re-import it.... I just don't see how this can be the case, because ORIGINALLY, the tracks are all good before I rename them and reorganize them in Basecamp..... (After doing this, I delete the originals on the unit and transfer the renamed ones back to the GPS to avoid duplicates.)

I have opened a case, thank you.

JM47048

I've not heard from you re the files you wanted me to send to you. Please advise. You have a PM.

JM47048

I've not heard from you re the files you wanted me to send to you. Please advise. You have a PM.

I apologize. Mondays can be a little crazy. I have opened a case on your issue as well. If you would like to just post your data here you can or you can send it to the PM and I will watch for it. Thank you for your help!