wwjd7

Followed a trail that got progressively weaker, then when it disappeared I began to walk around attempting to pick it up again. Got turned around and became "lost". Not "panicky" lost as I knew the trail was 150 metres away or so and my track log was active, let's just say "comfortably disoriented". As I looked down at my GPS to orient myself back to the trail, something on the ground caught my eye, not natural. It was a small brown squareish object, mainly obstructed by dead pine needles. I went to pick it up and it was a wallet, full of cards, ID, insurance, and two $20 bills. I saw another $20 bill laying a metre away on the ground, it's color peeking through the pine needles. (Years of geocaching has paid off having trained the eye to spot the slightest incongruities, lol!!) Everything was mouldy like it had been there a few years. Not wanting to carry out the smelly wallet and money in my pocket, I hand carried it all the way back to the car where I examined it more thoroughly the best I could. Who owned it? Where do they live? Anything with a date on it? I decided to bring it in to the nearest cop shop and let them handle it, could be a missing person, robbery, who knows. A search on my GPS directed me to the nearest cop station where I handed over the wallet and explained the circumstances on finding it. It was in such poor shape, she put on gloves before opening it and handling the money and cards. I then slid the additional $20 across the counter telling her I found this near the wallet. She looked at it and said keep it, it's yours, for your troubles. Hey, no problem, thanks! She took my name and number and said they'd be in touch if there's a follow-up but I never did hear back. Guess I'll never know how a wallet ended up in the middle of a forest. It's like reading a book only to find the last chapter was missing.

Yep, only use Activity Mode.

I'm also running v4.70. Yes, there is something strange going on with v4.70. Map updates are slow at times, my location is sometimes off the screen because the map hasn't updated itself. Also hitting the North Up icon may cause the Dashboard chevron to disappear. I'd have to swipe away from that page and come back to that page to restore the dashboard chevron icon and/or toggle the North Up icon. Very frustrating.

I only have the Ontario map downloaded and installed. This SAME map worked perfectly when I was running v4.20, but I understand you have to replicate the scenario. If you PM me, I can email you the exact IMG of the map I’m using if you’d like.

Ever since I installed v4.40 on my Oregon 700, the map drawing speed while geocaching is excruciating slow. It would take several seconds for the map (OSM) to draw, then I have to wait almost a minute for the geocache icons to display. When I pan the screen, I have to wait for another minute for the screen to redraw itself. And yep, I have the map drawing speed set to FAST and only ONE map is loaded. I gave up with the ridiculous wait time so I reinstalled v4.20 and everything speed right up, map draws are virtually instant again. Anyone else having the above problem with v4.40?

A new version of BaseCamp (4.7.0) automatically came down and updated itself yesterday. Now the VIEW menu no longer has View Selected Item in Google Earth, in fact, there are no other Google Earth selections either. Did Garmin remove the Google Earth menu options? Has anyone else experienced this? The BaseCamp changes file for version 4.7.0 makes no mention of removing Google Earth.

I visited the link that alandb suggested. And thanks for that, the info provided there fixed the issue. The 'fix' is to uninstall Google Earth Pro, then download and install the Google Earth Pro 32-bit version, NOT the 64-bit version. Seems that Basecamp doesn't like the 64-bit version of Google Earth Pro, but works great with the 32-bit version. Basecamp now opens Google Earth again! Didn't have to use the /regserver command line switch at all. Thanks again alandb.

Was working yesterday, today it doesn't. From BaseCamp, I used to be able to select View/Google Earth/Selected Items. Google Earth would open and zero in on the selected item. Today, Basecamp displays the popup "This feature requires Google Earth to be installed and running. Please launch Google Earth, then try again." It doesn't matter if Google Earth is running or not, Basecamp no longer communicates with Google Earth. I suspect it's the new Google Earth Pro that is causing the problem, the old Google Earth worked beautifully. I searched my hard drive and the old Google Earth in no longer there, but I have the new 64 bit version Google Earth Pro. Must have updated itself automatically. I tried this from the CMD line with no luck: "C:\Program Files\Google\Google Earth Pro\client\googleearth.exe" /RegServer. There were no errors or anything, it simply did not make any difference. I'm running Windows 10. Any ideas how to fix this?

So, it would appear the bug is in the routing algorithm and not the OSM maps being at fault. Thanks for verifying that MartyBartfast. (Learned something new... wasn't aware you could draw routes on the OSM site, good to know. Thanks.)

Did more tests. Below is the worst case example I saw, to take the 7th exit on a 4 exit roundabout. Other entry and exit points sometimes showed no exit counts at all, just simply to turn L or R at such-and-such a street as if the roundabout didn't exist. Basecamp does the same thing. However, since Garmin is the source of the routing software in both the GPS and Basecamp, this is inconclusive where the problem actually resides, the maps or the routing algorithm? I have no other maps to try. Wanted to hear if others have noticed this.

When I transverse a roundabout, it'll frequently indicate the wrong exit count (eg. Take the 3rd exit when in reality it should be the 1st exit). The images below show the problem. By the way, it's not this particular roundabout, it occurs at other roundabouts as well. Doesn't always happen, just depends on my entry and exit points, but I see no pattern why it miscounts the exits sometimes. Is this a problem with the maps or, dare I say, a bug in the routing engine? Anyone else notice this?

Interesting. I just noticed the POI list discrepancy with the 3.9 download, thought it was a new bug. As I’ve said, it still calculates routes correctly to the POI, so it's live-able for now. Thanks.

Finally had time to do a print screen of the bug.

Installed the latest 3.9 version and the routing issue introduced in 3.7 has been corrected in my limited testing. Unrelated to routing, I've noticed my first two POIs listed (under the Extras menu) always show the same distance and direction. At first I thought my CSV import contained duplicate coordinates, but CSV file contents are correct. It appears to be a bug in the way POIs are displayed in the list. The good news is that navigation to either POI still result in correct route calculations, so it's not a showstopper, it's just a small annoyance. Can someone else verify that custom POIs display the first two POIs correctly in distance and direction, rather than showing the same info?

Ah, good to know I'm not the only one who's noted this routing bug in 3.7.

Thanks alandb for the suggestion, unfortunately I had limited success. I created a /Garmin folder on the USB Drive, copied the IMG and GarminDevice.xml to it and fired up BaseCamp. BaseCamp now thinks my Oregon 700 is connected, a good sign. Unfortunately the Maps menu still does not have a selection for the map. Time to move on, I've spent way too much time on this. If it wasn't for me seeing and actually using my old computer with that map installed in BaseCamp for the last 4 years, I'd say it's not possible yet I've seen it. Thanks to all who offered suggestions.

I haven't tried that but I did as soon as I saw your post. I put the IMG file on a USB Drive. But how do I get BaseCamp to actually look there for the IMG file to load the map? From BaseCamp, when I select Install Maps, I have the same issue as before, BaseCamp wants to install maps from itself to the USB Drive, not from the USB Drive to BaseCamp. I can't believe I'm having this much trouble. It's just an IMG file, there's got to be a way to have BaseCamp load it. On my old computer, BaseCamp was happily using the CN 2013 maps. This is frustrating. :/ Maybe it's a Registry thing. I'll delve in there later and see what I can find. Thanks for all the input from eveyone, it's very much appreciated.

I tried that but BaseCamp wants to install maps from BaseCamp to the GPS. Apparently there is no option to install maps from the GPS to BaseCamp. Thanks for the suggestion anyway. It was worth a try.

I purchased CN North America NT 2013 years ago (on an SD card only) and used it in my GPS and I installed it into BaseCamp, used it for years. Well, that computer died so I'm setting up my new laptop and I can't figure out how I got the maps installed from the SD Card into BaseCamp. It's basically just two files on the SD card. I've tried dropping the files into various folders, but BaseCamp just isn't seeing the maps. Can someone tell me how to get the maps from the SD Card installed into BaseCamp? It's probably just some simple step I'm missing. I know I've done it before. Thanks

I may be jumping on this possible bug too early but when I installed 3.70, the automobile routing wouldn't display its usual "250m turn right at xxxx Street" or "800m turn left at yyyy Avenue". Instead it would display "Continue to xxxx Street" or "Continue to yyyy Avenue". I need it to work properly ASAP and couldn't afford misbehaving behaviour at this present time, and I knew it worked properly with 3.60. After reinstalling 3.60, the automobile routing once again displayed proper turn directions so I'm suspecting the automobile routing is broken in 3.70. Again, I may be jumping on something prematurely, and I could be wrong, so take this as a heads-up just in case 3.70 has broken automobile routing. I'm sorry I can't provide more information than this as I only had 3.70 running for a very short time before reverting back to 3.60 so no print screens or anything.

An updated v3.6 has been released that's fixed the auto-routing bug mentioned above. Auto-routing now calculates turn-by-turn directions when Calculation Method is set to Prompted. Thanks for everyone's contribution and assistance. Have to give Garmin credit as well... it was less than a week from them being made aware of the bug to a released fix. That's good service.

Thank you Atlas Cached. It was challenging to find the specific sequence of steps that recreated the issue, particularly to be in the, apparently unrelated, Geocaching activity first. Glad you were able to duplicate it. Garmin should be able to do as well then.

Of course, the maps I'm using are routable. They are openstreetmap by the way. If the Calculation Method is set to Minimize Time or Minimize Distance, it does give turn-by-turn directions. Problem only shows up when Calculation Method is set to Prompted then it draws a straight line to my destination.

The problem appears related to switching activities. Screen shots attached. First, the preparation: You have two Activities, a Geocaching activity and another activity (we'll call it Driving). The Geocaching Activity has Map/Dashboard set to Geocache, and Routing/Activity set to Direct Routing. The Driving Activity has Map/Dashboard set to Automotive, Routing/Activity set to Automobile Driving, and Calculation Method set to Prompted. This shows the problem... 1) On the Geocaching activity, search for any Geocache and pick Go. The point is to get the GPS to do a Direct Routing calculation. It draws a direct line to the cache. Perfect. Hit Stop Navigation. 2) Now return to the Activity selection page and swipe to select the Driving activity. 3) Now search for any destination to drive to. 4) You'll be prompted for Minimize Time, Minimize Distance, or Minimize Ascent. Select either Minimize Time or Minimize Distance. 5) It will draw a direct line to the destination, no turn-by-turn directions!

Installed v3.5. Same scenario as my previous comment, performed a battery swap in the field and my track was preserved! One more bug to go and I'd be super happy. If the Dashboard is set to AUTOMOTIVE and Routing/Calculation Method set to PROMPTED, it'll draw a straight line to the destination rather than give turn-by-turn directions. I can live with that one for the time being.