BaseCamp 3.3.0.3 Beta available

Basecamp ~ Dealing With Firmware "Issues"

FYI: Besides the problem with the firmware as noted below, some units (ie:Montana series v3.7 firmware) also exhibit similar issues with the "Relocate Waypoint to Here" function. ~ I previously uncovered this other related FIRMWARE bug, and it was confirmed by FALAGAR.

On a related note: I am surprised that Basecamp does not appear to have some "simple" .GPX data validation / correction capabilities/functions. ~built in to the read/write (drag & drop for Montana series) functionality.

Seems to me, this could solve issues (at least "bridge the gap") when there are firmware issues that don't effect the hardware directly.) ;)

The attached file gives me an error in BaseCamp Beta 3.3.0.3, but opens fine in MapSource.

The problem with that file is not the elevation. It's a firmware issue where the device writes bad XML when using the 'Average Waypoint' function on a waypoint that was sent with BaseCamp.

This is a known issue, hopefully the device teams will come up with a fix.
......

Falagar,

I cleared out BaseCamp, closed it and connected the gps. Opened BaseCamp and the transfer began.

My gps is there and the folder under it called " All Data ". I clicked on the folder and my data is there.
I selected 10 waypoints and selected to send to My Collection. The waypoints were transferred into My Collection
but no list were created. The waypoints were from 8 different categories.

The gps is a GPSMap 276c Ver. 5.60
Maps are City Navigator North America NT 2012.3
Windows 7 Home, 64-bit 4GB ram
BaseCamp 3.3.0.3 Beta

Mark

I apologize, I didn't mention an important restriction: category support in BaseCamp only fully works for Mass-Storage devices (that show up as a drive on your machine).

I think the 276 is not Mass-Storage, it's Garmin mode. So I am afraid you won't get category support in BaseCamp for this device.

Don't know if anyone saw this, as it was posted under the 3.3.0.2 beta area. (Others commented and agreed)

Two minor GUI issues: "(I wish I could find more to complain about ~ although direct .IMG import sure would be a nice touch!)" :D

(The second issue is introduced as a result of the new nested folders feature.) It actually becomes more irritating as data sets grow. (Particularly the more you organize the map configuration/display with nested folders.)

1.)
When selecting a waypoint (item) from the map, the waypoint list is scrolling to display the approximate location of the waypoint. (where it is located within the list.) But the (map selected) waypoint does not get highlighted. (If you select the item from within the list, it does become highlighted.)

Maybe this is not "feasible" due to the data filters located below the list? (It does however display in the filter entry box.)

2.)
When clicking on the + and - (folders), folder behavior is a bit odd (and CPU/time consuming) for a windows application. (IMHO)

I frequently find myself viewing nested folders by clicking on the + and minus (beside the folder) expecting only to expand the folders without viewing all the underlying data (on the map). But doing this always results in not only expanding/contracting the folder, but also changing the view of what you see in the map....

This may seem like a minor thing, butif you have a lot of waypoints (within nested folders) and you're browsing the folder layout searching for a list..... A lot of CPU/time is wasted waiting for the map display to update and display the containers entire contents. (something you don't necessarily want to view.)

This behavior (moving to that folder's view) "makes sense" when double clicking on the folder, but not when clicking on the + or -.

IMHO, merely clicking on the + or - should only expand/contract the specific folder, and not change the map view. As a "seasoned windows user" I would expect the following behavior to occur:

Clicking on +/- should only expand/contract folder/subfolders. (not change map view as it does now.)
Double-clicking should expands / contracts & changes to that view displaying all sub folders & lists etc.
Expand all/Contract all options added to right click (alt menu) when focus is on folder.

I am pleased that the folder display remains persistent after closing and re-launching Basecamp!:)

I am having trouble reproducing issue #1. Whenever I select a waypoint on the map, it does get highlighted in the folder data list. (It's just a grey outline, not a blue one with a blue border that you get when the folder data list is in focus).

We'll see if we can improve the expand/contract behavior. This will have to wait for another release, though.

Two Unresolved "Issues" (From Basecamp 3.3.0.2)

I somehow recently posted this on the wrong thread, so I doubt whether many viewers saw it...

Unwanted / Unexpected Data Deletion:
https://forums.garmin.com/showpost.php?p=117501&postcount=134

Folder / List Behavior:
https://forums.garmin.com/showpost.php?p=118596&postcount=163
https://forums.garmin.com/showpost.php?p=118554&postcount=162 ~ (original post, see issue #2 highlighted in red)
note: Issue #1 in post #162 is also still present, but is minor by comparison.

Also regarding:

I am having trouble reproducing issue #1. Whenever I select a waypoint on the map, it does get highlighted in the folder data list. (It's just a grey outline, not a blue one with a blue border that you get when the folder data list is in focus).

We'll see if we can improve the expand/contract behavior. This will have to wait for another release, though.

I'll adjust the brightness settings (etc.) on monitor and get back to you. As it is, I can't see any indications of an outline / highlight (or anything showing the selection) whatsoever on this win-7 pro 64 system....

UPDATE: I'm using a standard windows-7 aero theme. I've tried everything, but no indication (of the "map" selected waypoint) appears in the list..... I bet the outline only shows on certain windows resolution settings etc... FYI: I'm at 1920 x 1200 and using "Medium 125% dpi" text sizing. (Possibly a list object outline attribute could be changed, either darker or and or wider to resolve this???)

"I'm heading for the woods now with my two black labs to pull treestands, and enjoy my Garmin Montana! You could even follow me if you had access to my Garmin GTU-10!" ~ Garmin sure does makes some great stuff!

The problem with that file is not the elevation. It's a firmware issue where the device writes bad XML when using the 'Average Waypoint' function on a waypoint that was sent with BaseCamp.

This is a known issue, hopefully the device teams will come up with a fix.

Thanks, Falagar, I averaged one of the same points with my 62s. The GPX file was properly formed, but it lists this as the elevation:
16404198756600271000000000 ft. Do you have any suggestions who to report this to?

Thanks, Falagar, I averaged one of the same points with my 62s. The GPX file was properly formed, but it lists this as the elevation:
16404198756600271000000000 ft. Do you have any suggestions who to report this to?

I would shoot an email to product support, just follow the link at http://www.garmin.com/us/support/contact.

At the same time, I will try to forward this issue to someone on the device team from my end.

Thanks again, Falagar. I'd just like to add that the Etrex30 averages a waypoint it creates just fine, including reasonable elevation values. The problem was arising when it tried to update a waypoint created with software (I think it was MapSource, but it may have been Global Mapper). The original waypoints didn't have elevation data. I was able to repeat the error with a waypoint created in BaseCamp 3.3.0.3 Beta that didn't have elevation data.

I apologize, I didn't mention an important restriction: category support in BaseCamp only fully works for Mass-Storage devices (that show up as a drive on your machine).

I think the 276 is not Mass-Storage, it's Garmin mode. So I am afraid you won't get category support in BaseCamp for this device.

Falagar,

Thanks for checking into my problem. Do you think in time the support for my unit could be added to BaseCamp?

Mark

Can anyone else confirm this problem on Windows? - Select a waypoint from the map (using the pointer tool) in Basecamp, and see if the waypoint gets outlined in the lists. ~It appears in the search box at bottom, but it does not become outlined (highlighted etc.) in the list directly above.

1. Let's say you have My Collection selected. When you click on the map with the pointer tool, is My Collection still highlighted?

2. You can tweak the Windows color to see if BaseCamp is not working properly, or if the highlight color is just not noticeable on your monitor.
a) right-click on your desktop -> Personalize
b) click Save theme to save your current settings
c) click on Window Color (at the bottom)
d) Advanced appearance settings...
e) change 3D Objects -> Color 1 to yellow
f) change Window -> Color 1 to blue
g) apply the settings and BaseCamp should look like this:



If you're seeing something different, please post a screenshot.