Forum Replies Created
-
AuthorPosts
-
@Cachelovskys wrote:
Is that radius thing correct?? any Garmin owners??
Right-they won’t show if the unit is set to “find nearest” On ours, (Legend CX) you can select “find by name” to make sure the Texas ones got loaded. That’s the button on the lower left.
Once the waypoints are in a GSAK database, click on the “GPS” pulldown at the top of the screen. Then, click on “Setup” and select “Garmin”. A list of Garmin units will appear and then select the one you have. Once that’s done, you select “Send Waypoints” under GPS and connect the unit and turn it on. We used to always export the waypoints to Mapsource and then send them from there to the GPSr, but we switched to this method since it’s easier. Hope that helps.
@sandlanders wrote:
Maybe it’s all due to a shift in the space-time continuum. 😯
Perhaps some time traveling first-to-find hound was going back to nab a few and somehow warped it (the space-time continuum, that is).
53105 is Burlington and 53147 is Lake Geneva.
OK-tried 53191 (Williams Bay) and it worked fine. This is messing with our
minds!Just tried again-53105 and 53147 were not working at all.
Check out Bong State Recreation Area-it has lots of trails and a bunch of caches.
@Mister Greenthumb wrote:
@Captain and Mate wrote:
The last couple of times we were browsing the Recent Logs, we noticed a cache or two that had several (anywhere from 6 to over 20) found logs by a single cacher (different one each time). Surely this wasn’t intentional, but what causes that? Is it logging from a phone or what? Just wondering.
Was it the Navarino Event? That one had multiple “attended” logs from logging temporary caches.
.
No, these just appeared to be traditional caches, not events or multis. The logs were all identically worded.
We can just see the log now:”Took Chirp/left McDonald’s happy meal toy. TFTC!”
This is why you’re the WGA Webmaster. 🙂 You can figure all that stuff out. We just use the “our finds” database as a backup to keep track of our finds. The things you mention…wow, we have a lot to learn. Thanks for your help!
@Todd300 wrote:
That happened to me once, Barry. I once posted a log saying the cache terrain rating should be a 1.5, not a 1 since it was a drive up, but not wheelchair accessible. I then downloaded the “My Finds” PQ.
The CO got pissed and deleted my log. I re-posted my log with a cut and paste “TFTC”. Then downloaded another “My Finds” PQ. The result was 2 finds for that one cache in my database. I ended up deleting that database and making a whole new one so my stats would be accurate.
We tried this method and it did the trick. We just deleted everything in the database, reloaded the “finds” PQ, and it’s now correct. Thanks to all who offered ideas. We learned a couple of things in the process. 😀
@CodeJunkie wrote:
There’s an easy way via the filtering option.
Search -> Filter -> Log Tab
Logs to search = All + Found (uncheck Unfound + Others)
Required Count = Greater than or equal 2
Logged By = Check the box to enable, select Exact Match, and then enter your caching ID in the Details box.This should filter the results to caches where you have 2 (or more) “Found” logs.
If that doesn’t work, let me know and I’ll have you send me your PQ from GC.com and load it into GSAK and find it for you.
Once we got the filter to go, we had 13 caches with more than one “found” log, but all of them were caches that had bonuses attached, events with temps, or multis where you could log each stage as a find. All seemed to be logged correctly. The confusing part is that cachestats uses the same PQ, but shows the correct number of finds according to GC.com.
Okay, here’s another GSAK question: This is a minor issue, but it’s made us very curious as to why it happened. When we run the findstatgen macro, the results show 1 more find than we actually have. It’s no big deal, since we use cachestats for our profile page, but does anyone have a thought about how to correct this error? Going through each cache one by one would be far more effort than it’s worth, but maybe there’s an easier way.
We’ve gotten ours here:
http://www.cacheboxstore.com/microcache/microcacheindex.html
Great coin! Thanks to all who helped make them happen. We’ll be holding on to ours-having one of these go missing would REALLY make us mad!
-
AuthorPosts
