BaseCamp 3.2.2 is available

When displaying a custom map the world map shine through in 3.2.2.

How to turn off the bagground map completely?

Have you tried adjusting the draw order?

Both of these display fine on my test Oregon 450 when I put them in my device's Garmin\gpx folder. The files look good.

So I am not sure what might be causing this. Maybe try deleting all user data on the Oregon? Or even master-reset (http://garminoregon.wikispaces.com/Miscellaneous#FAQ-M1.%29%20How%20do%20I%20master%20reset%20my%20Garmin%20Oregon?)?

Master reset didn't do it, but I re-deleted my GPX folder AND deleted the CustomMap I had created in the 62s's internal memory. Then the transfer worked fine. Thanks, Falagar.

Troublesome GPX output

In this thread there's some information about a change to the GPX output of BaseCamp that seems to be causing interoperability issues.

Is this something that just accidentally got left switched on in the release build?

community poi search

Don't know if this is already mentioned, but in the community poi search, places of worship (churches) are missing as subcategory.

On which map?

The Places of Worship subcategory works fine in 3.2.2 with the Garmin maps I tested (CN NT NA & Europe 2011, German Topo map).

waypoints on eTrex30

I've used an eTrexH for years with DNRGarmin but got my first mapping eTrex30 last week. There has been discussion about the style of waypoints and it would seem that the eTrex30 simply ignores any BaseCamp <sym> data sent to it in a route and uses a big blue flag for everything. Am I right or in need of a little coaching?:confused:

On which map?

The Places of Worship subcategory works fine in 3.2.2 with the Garmin maps I tested (CN NT NA & Europe 2011, German Topo map).

I was searching for this on my custom Openstreetmap but didnt realize the search index was map dependent. Now I noticed the subcategory works on other (OSM) maps. I added this place of worship subcategory later to my map, but couldnt find it.

After resetting Basecamp to the default settings, it came back. So somehow Basecamp remembers and stores the search index. Thanks, this issue is solved.