New basecamp 3.2.1 doesn't show tracks by default

Unfortunately there is no ETA for a fix. Garmin seems to be able to fix other bugs that are just now being reported for the next maintenance release but won't do a thing about this one.

They could have given us back the old thicker lines until they could come up with a user selectable system. But no, they'd rather listen to a few beta testers that wanted hairline thickness and ignore the majority that are wondering what happened to their tracks. It's knee-jerk changes like these that stop me from having a Garmin gps in my airplane.

For now the only fix is to uninstall 3.2.1 and find 3.1.4 on the net somewhere, since Garmin can't even be bothered to post a link to the old version.

One could always change the track colors to something other than transparent and use the control key to select multiple tracks to display; this gives nice thick lines on my machine.

But no, they'd rather listen to a few beta testers that wanted hairline thickness and ignore the majority that are wondering what happened to their tracks. It's knee-jerk changes like these ...

I apologize that we apparently caused a lot of dismay for our users with that change.

But I assure you that was not a knee-jerk change. If I were to find the number of posts where people complained about the THICK track lines I would be busy for quite a while... And it wasn't just in this Beta. We've had complaints for MapSource and earlier BaseCamp releases. And I don't recall anyone speaking up in favor of the thick track lines then.

So this was honestly a change trying to give users what we felt they wanted.

We will try to make this customizable in a future feature release (that means in 3.3 or later, not 3.2.x). Hopefully 3.3, but no promises, as usual.

I was not posting before that change happened, but I can tell you that I was also very annoyed by these thick track lines and I´m quite happy, that they are thin now. I´d rather see an option where you can select what you really want to see within your "collection". While you can create Collections on your PC and Drag / Drop the Items you want to see at the same time on your map, you can´t create them on your Device. So when I switch in Basecamp to my device, the map is probably full of things I don´t want to see. But I don´t want to hijack that thread now :o

I was one of those that asked for thinner / adjustable track thickness. What has been implemented works extremely well for me. The tracks do however appear to be invisible in their current default colour (light grey), especially when viewed on top of Birdseye imagery.

Perhaps as an interim "fix" the default could be set at say red ? That appears to be the colour that stands out the best for me with the mapsets I have installed.

And yes, as PBUEDI states, another call for turning on or off individual lists in My Collection.

Perhaps as an interim "fix" the default could be set at say red ? That appears to be the colour that stands out the best for me with the mapsets I have installed.

As I've pointed out before, changing the track color is not any kind of a temporary fix or workaround. The Basecamp track color = the gps track color.

Say you have 100 tracks in Basecamp and a gps that you can only load 20. You change all the tracks in Basecamp to red so you can see them. When you want to upload some of the tracks to the gps, they will be uploaded as red, which is very hard to see while moving in bright sunlight.

In fact, the best color on the gps for visibility is blue. Unfortunately with topo maps in Basecamp, the thin blue tracks blend in with rivers and streams.

So the workaround requires changing the color to red when importing and then having to temporarily change it to blue for uploading, then changing it back to red. Not a workable solution.

Even for printing, selecting the tracks first might give thicker lines, but it also activates the track direction arrows. For the maps I print I don't want to insinuate that the trails are one-way.

The thick lines may have "annoyed" some people, but the thin lines have made the program useless for others.

The thick lines may have "annoyed" some people, but the thin lines have made the program useless for others.

This shouldn't turn into a p1$$1ng contest among users. The thick lines made the program as useless for many of us as the thin lines seem to for others.

The solution is for Garmin devs to stop making assumptions for users and where something could easily be user-selectable just make it so. I realize that a fundamental decision has been made to cater to the least common denominator user .. the one who refuses to spend any time learning the features of a program. But that's what the defaults are for. That doesn't mean you take away the ability to control things.

...ken...