Home
9:53 am
December 3, 2010
Offline
Sockeye wrote:
... but who cares for caching anyway?
BR
Sockeye
I do :woohoo:
10:28 pm
July 18, 2010
Offline
pprass wrote:
I would have thought that is what the beta testers were for :huh:
Well these "Betatesters" seem to have only a very limited idea of geocaching. (About the amount the guy has, stopping his car near a tree, walks the 10feet towards it and finds the cache. (As in the promotion video))
Things like multi-stage caches do not really exist for them, and they absolutely do not see any sense in doing a waypoint projection on anything else than their current position. (WTF ist that anyway and WTF needs that...)
...ok, that's still the main reason Geocachers buy Garmins here in Europe, but who cares for caching anyway?
BR
Sockeye
10:25 pm
April 6, 2010
Offline
Nope, the beta testers get a product to test that is apparently designed by people that know next to nothing about maps, compasses, GPS, geocaching, hiking, trekking, surveying, cartography, or being outdoors.
If anyone in the decision making process had thought to consult an expert in any of those subjects we would have a much better product to start with and may not have some of the design flaws that are aggravating in the field. Like the SD card falling out when you change batteries outdoors in the cold while it's raining or no declination settings for the compass or the cable being nearly impossible to plug in/out when the unit is on the Magellan mount.
Well, that's my rant for the new year! (I'm trying to cut back) 👿
When in trouble or in doubt, run in circles, scream and shout
9:01 pm
November 11, 2010
Offline
phild31 wrote:
...I do wish they would talk to an experienced geocacher/GPSr user/hiker before they implement these stupid, redundant ideas! :blink:
I would have thought that is what the beta testers were for :huh:
1:36 am
April 6, 2010
Offline
Yeah, you have to delete the MagellanGeocacheExtension.gpx file to stop it from reloading all your finds.
Magellan must of thought it would be nice to keep a record of every geocache found with the unit.
That's what the 'Geocache Summary' is about.
I guess they don't know that GC.com keeps a running record of your finds.
I do wish they would talk to an experienced geocacher/GPSr user/hiker before they implement these stupid, redundant ideas! :blink:
But, on the fun side; :laugh:
I've got 2000+ cache finds now so a few weeks ago I loaded all my finds with the regular cache files for my area (50 miles around Boston) onto the 710.
It really slowed things down. :dry:
The list, set for nearest caches, was full of found caches and the map was full of smiley faces! :woohoo:
It looked kinda' cool but I dumped everything and went back to loading only caches I have not found.
When in trouble or in doubt, run in circles, scream and shout
11:59 pm
March 17, 2010
Offline
I have the same thing happen. There's a file in the unit that keeps a memory of all the caches you've logged. I believe this file gets recalled each time and reloads the previous list, plus all the new logs. I like having the file there because it shows a smiley on all the caches I've found, and a frown on the Not Found caches. However if you have 3000 caches found it ends up slowing down the unit, and it causes the issue above.
You can delete this file, it's called MagellanGeocacheExtension.gpx, and will create a new one for the caches you've found since the last delete. Another thing VP does is use that file, along with your log entry file to show all the caches you've found with smiles in VP, when you fetch the logs.txt file with VP, after a caching run. Kind of neat, but again, with thousands of finds it will take a toll on speed. I've only got 220-something found, so it isn't an issue yet.
Denis Gionet, OGA Executive Member - Northern Ontario.
10:31 pm
March 26, 2011
Offline
How about just going into the correct drive (your gpsr unit) and under the geocache folder just DELETE the log file?
Mine never does what you're saying...as a matter of fact, I use VantagePoint when I get home from caching and it automatically pulls up a window and guides you thru uploading the field notes. Then after closing that window another window awaits in VantagePoint asking if you want to delete the log file and you click on yes and it's done...no navigating or otherwise....might try that way.
Only thing I can think of is that if you're going in there and MANUALLY clearing all the contents of the log file you need to make sure to save changes when you close the file and it should be just fine. Just to be safe tho I'd just delete it entirely and you won't have to do all that editing crap. Why bother with the extra steps?
6:19 pm
January 2, 2012
Offline
After caching, I come home and use the gc.com Field Notes to log the caches. I hook up the unit to the computer, find the right drive (E:), go to the geocaching folder, and choose the "logs" file. I upload it and then use Field Notes just fine. Everything works great....and only the caches I have found show up to be logged. When done logging on-line, I go to the "logs" file and delete everything in it and then save it.....so that next time it will be blank. It shows as totally blank when I'm done, and this must be mostly true since Field Notes only has the next group of caches I find upon doing the same thing the next time. The weird thing is that when I go to delete/resave the "logs" file, the file always shows ALL the caches I've found since starting to use the unit from day one.....even though I just deleted it the last time to be blank. As I said, the Field Notes don't show all of this...just the new ones.....so I can't understand why the file shows everything to date, especially after I delete it and clear it out every time. This is strange. Any thoughts about this?! It's not so bad now but a few months down the road will be obnoxious!
1 Guest(s)
