Jump to content

RonFisk

+Premium Members
  • Posts

    496
  • Joined

  • Last visited

Everything posted by RonFisk

  1. The problem has been resolved. I trashed the Adventure Labs app on my iphone and reinstalled it. The geofencing is now working correctly. Thanks for the help...
  2. Correct, The builder website. I do believe that it has been modified since my first use, which was over a year ago. I'm not sure of the version number if any. Since my original complaint I have redone my Adventure lab and reinstalled the applicataion to my iPhone 11. I do believe that it's operating correctly now. I'll be better able to determine if in fact it's operating correctly after a few more people have tried it. Thanks for your input...
  3. My information is that this has happened even before visiting the location for the first time. I have tried to change the geofencing, turning off the lab and then making the lab public again. It doesn't seem to have any effect. I didn't have this problem with another of my Adventures. I also noticed that this submission was using a newer version of the lab creator application...
  4. My geofencing doesn't appear to be working. I'm having geocachers report to me that the geofencing on my adventure lab "Exploring the Santa Barbara Cemetery" isn't working. They are able to get the questions to my stations while not even remotely close. I have my geofencing set to bellow 100 meters on all statiions. In some cases 20 or 30 meters. Anyone else having this problem? The status is "Public".
  5. Thank you very much. iOS 12 will be out of beta soon and we certainly don’t want any problems. I’d be happy to join your beta team if you have openings...
  6. I’d also like to add that it’s only happening on my iPhone X. It’s fine on my iPhone 6+. I’ve also placed a bug report on my developer account...
  7. Same problem here. Using an iPhone X, ios 12b11 (16A5365b). Application worked fine up until your latest update 6.10.0. Now it crashes upon opening... Thanks, Ron
  8. All of a sudden my Garmin Communicator won't download cache information to any of my Garmin devices through Geocaching.com. It seems to work correctly in Windows, but will not work on the Mac with Firefox or Safari. I constantly get the following error when trying to connect. (SyntaxError: unterminated character class) Any ideas why this is happening? It just started this week and only seems to effect geocaching.com when using OS10.10.2. Other applications using Garmin Communicator seem to work OK. It's just Geocaching.com where I'm having the problem. I can't download any cache information to any of my Garmin devices. Any help will be appreciated. Any others having this problem? Ron...
  9. Reply to Konza Coyote: It's not at all uncommon for some cachers to log beta finds. This occurs when a cacher is with the cache owner when the cache is placed and verifies the placement and coordinates. This is generally in off the beaten path locations where the beta finder is not likely to return to the area, such as out of state or in another country etc. The beta find shouldn't be logged as a find until such time as the cache has been activated and actually found. Sometimes this takes weeks, months and even years. The log sheet is signed by the beta finder at the bottom or back of the log sheet including the notation, beta & the date. Some approve of this practice and other don't. A beta finder cannot log a first to find unless he/she actually returns to the area after publication and signs a clean log sheet. (This opens another can of worms -- what constitutes a FTF? and who really cares?) I know of no rules covering either practice...
  10. I'm glad to see you are able to edit my account. That gives me something to go by. The problem is recent as I've never had this problem in the past. I don't really know where to start but I'll give it a go. I haven't really changed anything that I can think of but it does seem that the problem is at my end. Thanks again, Ron... Problem solved. I found that I have to use the calandar to change the date. I can't just type in the date in the date box. I don't know if this is new but I don't remember having to do that in the past. In any event that solved my problem and I'm a happy camper again...
  11. I'm glad to see you are able to edit my account. That gives me something to go by. The problem is recent as I've never had this problem in the past. I don't really know where to start but I'll give it a go. I haven't really changed anything that I can think of but it does seem that the problem is at my end. Thanks again, Ron...
  12. Moun10Bike, The log entry you changed was OK to begin with. it's all the caches on that date that show the beta find date of 5/17/14 by others in our group. An example is GC5556T (4 Logs). The found by me date on that one should be 5/17/14 and not 7/16/14. Funny thing is the dates are correct in GSAK but when I downloaded my "My Finds" PQ they all show the 7/16/14 date. I can't figure out where the problem is. I've used two different computers and I'm unable to edit these files. As for "NOINO ON" I left your edit and added a new one with the correct date. I can delete it later to get rid of the duplicate find. Thanks, Ron...
  13. I am attempting to log quite a few finds that I neglected to log when found on 5/17/14 everything looks OK, but when I check my found caches they all have todays date 7/16/14. I edit them back to the correct date 5/17/14 and I get the log edited date of 7/16/14 but the find date has reverted back to todays date as well. How do I get the correct date to show on my found caches. For some reason I can't edit them. Obviously this creates a serious problem... I've even received a few emails telling me that the date is incorrect but I can't change it. I've never had this problem before. Anyone else seen this?
  14. Actually they should pay attention to it or delete it altogether. The gps device database is sadly out of date. They don't even have any of the new Garmin devices listed. Maybe someone at Groundspeak should be assigned this task. Jeremy, are you listening?
  15. Sure! I'd suggest that you first back it up to your computer. If it's a Garmin Map MicroSD then you have gained a map set as well. Preprogrammed MicroSD's can be used in any unit that takes them. They don't have to be unlocked...
  16. How do I get a travel bug that I no longer have? It's still in my inventory? TB4J4BH shows up as being in my hands, but I don't have it and can't get it off my inventory. I've tried contacting the owner and haven't gotten a reply. I've tried to delete the entry and it still shows as being in my hands. The problem is that I took it out of a travel bug hotel and logged it out when I got home, I gave it to someone else to move along and they logged it as removing it from the TB hotel before I got a chance to log it. They then placed it into another cache but it doesn't show up in that cache, but still in my possession. Apparently the TB owner is no longer active and I'm stuck with the TB in my inventory and can't get rid of it. I no longer have the identification number so I can't log any details. Any help will be appreciated. I don't know if a reviewer can help out, but decided to post here before asking a reviewer for help...
  17. Sanyo Eneloops for sure. The only way to go and the MAHA charger pairs up well with them. I haven't tried the 2500 mAH, but the 2000's work great for me...
  18. Try holding the upper left hand corner of the screen when you power up. If that doesn't work call Garmin. You may have to return it. That's what happened to me...
  19. I'm a Mac guy and not a PC person, but I'd assume that they would automatically transfer over when you do a migration to your new machine. Windows can do a migration to the new machine can't it?
  20. The "H" stands for Hi sensitivity.
  21. The "H" stands for Hi sensitivity.
  22. My vote would be for the Garmin GPSMAP 60CSx if you don't need paperless. If you want paperless caching go for one of the Oregon units. I have both a GPSMAP 60CSx and an Oregon 550t. They both have their place and are both relatively reliable units...
×
×
  • Create New...