Shaping points being turned into locations on transfer from Basecamp to Edge Touring

Basecamp worked fine for me on Win10 so I suspect a call to Garmin is required so they can establish what is wrong with your system.

Win10 is creating various issues for all sorts of folks, and not just with Garmin programs. I'm sticking to Win7 :)

I've been persevering and tried again with another vanilla Windows 10 installation and Basecamp 4.5.1. Now the crashing on close has stopped, but again if I create any assets at all within Basecamp I now see the following message when I restart Basecamp....



If I click "Fix" Basecamp starts and all my assets have vanished. If I click "Cancel" then Basecamp simply doesn't start.

I have used Windows Resource Monitor to observe the files being accessed by Basecamp and there is nothing suspicious/odd about the activity.

I'm wondering whether there is a problem with .NET or something like that. I haven't tried to install anything extra. It's just a vanilla Win 10 install followed by all Win 10 updates.

Maybe the error message above is familiar to somebody, and perhaps they know the correct solution.

Contact Garmin UK for support? You'll be lucky! I've had this problem since I started using Basecamp and can't even get them to say hello!

By the way.....any idea how I can delete all the locations and clear the memory in one go? Factory reset didn't clear them and I'm having to go to each point and delete it manually - could be here for a very long time; maybe Garmin will have said hello by then though!

I've had no problem with Garmin UK, how are you trying to contact them?

What locations/memory are you trying to delete? In BaseCamp? On a device? If so which device?

On the Edge Touring Plus you can remove all saved locations at once by deleting the locations.fit file using file explorer software. It will be recreated as required by the device.

I now have Basecamp saving new assets, both in the cloud and locally. Following a hunch I uninstalled Basecamp 4.5.1 and installed Basecamp 4.5. Now it works. I would guess from my experience that there is a bug in 4.5.1 which means it works as an upgrade over a working older release, but does not work when installed onto a bare system.

Furthermore, I see no more signs of the bug which caused me to start this thread in the first place. It would appear to me that 4.5.1 is best avoided. I've wasted probably 15+ hours on this mess already and lost data it will take me many more days to recreate or which is gone for good.

And once again Basecamp is now crashing on close and unable to load the "list data file" on opening, which means all my saved assets keep disappearing. At least my cloud storage is remembering them this time. It's a bank holiday in the UK so another day to wait for support.

SOLVED - I had several waypoints/locations - maybe 8-10 - out of my library of 150 or so, which were in some way corrupt. No visible problem with them and they were happy to sit in the cloud, but every time I dragged any of these locations to local storage it caused BC to crash on exit and thus lose all new assets created within that session. Unfortunately I was copying all my old waypoints/locations, both good and bad, back to local storage so it was a never ending circle of failure. Now, through painstaking trial and error I have identified and eliminated the rogue waypoints. Touchwood it'll be plain sailing going forward.

The question remains - how the hell did they get corrupted and why didn't BC handle the bad waypoints with better grace?

Same problem

Since recently, I have the same problem on my Garmin Edge Touring. This started after an update on the GPS unit. I am curently at Software version 2.70.
I work around the problem by
1) first transfering the track to the GPS unit
2) Delete all waypoints using JaVaWa device manager
3) transfering the waypoints that I want to the GPS unit

Thanks for the reply. I don't use JaVaWa for this, but effectively I have ended up doing the same thing, over and over again using Windows explorer to delete locations.fit. It is a joke. However, I'm sure I've been on 2.70 for quite a while and I don't recall an update which directly led to this problem. I have yet to contact Garmin, but I will have to. This is stupid.

Another possibility is to convert courses/routes to tracks and send tracks instead of courses. Or rather, when downloading tracks, use them as is on the device and don't convert them to courses in Basecamp. If you convert to courses you end up with all these extra waypoints instead of shaping points. Again this seems to be a new behaviour.

JaVaWa Device Manager deletes the waypoints in the \garmin\newfiles\route.gpx or waypoint.gpx before they are imported.

Deleting the locations.fit deletes all locations in the Edge, after they are imported.


Workaround:
Don't send or transfer or drag from BaseCamp to Edge, but select only the track and waypoints you want to send (by using ctrl-mouse click for multi selecting items), and use Menu: File - Export - Export selected ... - Save as anyname.gpx directly into the \garmin\newfiles\ folder in the Edge.