Jump to content

De Bosmannetjes

+Premium Members
  • Posts

    3
  • Joined

  • Last visited

Everything posted by De Bosmannetjes

  1. I have this issue too. Logs are not loaded, cannot make private notes on the page and correct coords. This is probably due to a wrong cookie implementation on the website. When I choose only 'Necessary' cookies I have the problems. Choosing the 'Preferences' cookies as extra solves the problem for me. I use Win10and Chrome.
  2. You've found all of those caches. Are you sure you aren't filtering out found caches? The Garmin devices track your finds internally (not by the status in the GPX file). By changing the GC code, it no longer matches the internal list of caches you've found and wouldn't get filtered out, so it would show up again. Yes, i'm sure my filter is ok. It's set to show alle caches including found caches. They were not on the map when I was searching for them for the first time. Used these in my tests because I knew they failed to show up.
  3. I have the same problems with my 35T. Most caches are shown but not all. It seems it is not a filter or a 'long distance' problem. My filters are set to show everything, I live in the Netherlands and the caches used in my test are all Dutch caches. It looks like there are GC-code <> cache-ID combinations the 35T cannot handle. For instance GC5DP7M with ID 4615147 is not visible on the map and in the search screen. The cache is shown on the map in the search screen after changing the GC-code and ID to GC5DP7N, 4615148 manually in the gpx file. Other non working combinations are <name>GC5DP7M</name> <Groundspeak:cache id="4615147"> <name>GC56KR9</name> <Groundspeak:cache id="4404243"> <name>GC6RBAP</name> <Groundspeak:cache id="5855893"> <name>GC4PZXA</name> <Groundspeak:cache id="3968074"> After changing the GC-code and recalculating the ID they are back on the map. Looks like a bug in the Etrex 35T.....
×
×
  • Create New...