+papatom2 Posted July 2, 2006 Share Posted July 2, 2006 (edited) This has been happening for three weeks now. I get a PQ and load it into GSAK. I look at the caches with T bugs and then do a search. The bug does not exist! At lest the ref. number in the PQ does not. When I go to the cache page and click the bug name I do get a page But the ref number there is different. EXAMPLE::: Cache Name => The Narrows waypoint: GCBA2D Has Travel Bug Name => Have a little faith (ref = TB14253) I looked at the PQ and the ref number does came from GC.com and not modified by GSAK. Do a search on TB14253 and get ::: This travel bug hasn't been activated. Activate it now. Go to GCBA2D and click the T bug :::::: Have a little faith and we get the page for this bug BUT the page says to ::: Use TBGHMP to reference this travel bug. ________________________________________________________________ Looks like something wrong with the PQs. Anybody else having this problem? Edited July 2, 2006 by papatom2 Link to comment
+BlueDeuce Posted July 2, 2006 Share Posted July 2, 2006 The TB14..... doesn't seem right. I'll try the same thing. Link to comment
+Lil Devil Posted July 2, 2006 Share Posted July 2, 2006 My PQs and TBs when spun with GPX Spinner have been working fine. Maybe it's a problem with GSAK? Link to comment
+papatom2 Posted July 3, 2006 Author Share Posted July 3, 2006 (edited) Was hopeing to get some confermation by now. So I downloaded WATCHER and then got the above cache and I have the same results with WATCHER as I have with GSAK. Now this is not ALL TBs but some - and GC.com is definitly sending wrong TB ref. IDs. I can give more caches that have wrong Tb names. LIKE Quackers the Duck (ref = TB1C1BA) in 'Lil Hawk Crag The real ref is TBHMJT for TB Quackers the Duck . Edited July 3, 2006 by papatom2 Link to comment
+BlueDeuce Posted July 3, 2006 Share Posted July 3, 2006 (edited) Sorry, Got distracted and forgot to follow through. PQ - GASK Shuttle Columbia (ref = TB10718) Quackers the Duck (ref = TB1C1BA) hmmm seeing this on quite a few of them. the link does connect to the correct page. It's in the raw data. </Groundspeak:travelbug> <Groundspeak:travelbug id="115130" ref="TB1C1BA"> <Groundspeak:name>Quackers the Duck</Groundspeak:name> Edited July 3, 2006 by BlueDeuce Link to comment
+Lil Devil Posted July 3, 2006 Share Posted July 3, 2006 It's in the raw data. </Groundspeak:travelbug> <Groundspeak:travelbug id="115130" ref="TB1C1BA"> <Groundspeak:name>Quackers the Duck</Groundspeak:name> I see the problem. The PQ generator is converting 115130 using hex instead of base31, resulting in 0x1C1BA where base31 equates to HMJT as shown on the travel bug page. Where's Raine? Link to comment
+papatom2 Posted July 10, 2006 Author Share Posted July 10, 2006 A week has past and still not fixed. This makes one month that the PQ is sending bad TB information. When will it get fixed? OR just noticed by the powers that be. Link to comment
+Shilo Posted July 11, 2006 Share Posted July 11, 2006 My PQs and TBs when spun with GPX Spinner have been working fine. Maybe it's a problem with GSAK? I use GPX Spinner and have the same problem as other are having. Whats your secret? Link to comment
+Lil Devil Posted July 11, 2006 Share Posted July 11, 2006 Whats your secret? Getting lucky and never running across a travel bug with a large enough ID number to expose the software bug. Once the exact problem was pointed out, I checked for that specifically, and Spinner suffers, too Link to comment
+Raine Posted July 11, 2006 Share Posted July 11, 2006 Raine's back! I'll get on this first thing in the morning and see what's happening. -Me Link to comment
+Shilo Posted July 11, 2006 Share Posted July 11, 2006 Raine's back! I'll get on this first thing in the morning and see what's happening. -Me Welcome back Link to comment
+papatom2 Posted July 11, 2006 Author Share Posted July 11, 2006 Thank You. I knew somebody would look into this eventually. Link to comment
+Shilo Posted July 15, 2006 Share Posted July 15, 2006 Raine's back! I'll get on this first thing in the morning and see what's happening. -Me What did you find? I notice it is still doing it Link to comment
+papatom2 Posted August 4, 2006 Author Share Posted August 4, 2006 It is now 2 months or better that this problem has existed and STILL is not fixed! When will something be done? It can't be that hard, could it? Would someone lets us know what's happening with this? Link to comment
+Raine Posted August 4, 2006 Share Posted August 4, 2006 Ok.. we've found the issue and a fix will be released early next week. -Raine Link to comment
+papatom2 Posted August 5, 2006 Author Share Posted August 5, 2006 Thank you for the information raine. I am a happy camper again and shall be patient and wait. Link to comment
+Shilo Posted August 6, 2006 Share Posted August 6, 2006 Thanks for the update. I was wondering if this was going to get fixed or not. I'm all Link to comment
+papatom2 Posted August 13, 2006 Author Share Posted August 13, 2006 (edited) "Ok.. we've found the issue and a fix will be released early next week." Dont think it has been fixed. Edited August 13, 2006 by papatom2 Link to comment
+Raine Posted August 14, 2006 Share Posted August 14, 2006 We delayed the release as we were adding some other "features" together and wanted to do some proper testing before unleashing it on the public Link to comment
+Shilo Posted August 14, 2006 Share Posted August 14, 2006 We delayed the release as we were adding some other "features" together and wanted to do some proper testing before unleashing it on the public This sounds good Any timetable for the unleashing? Days, weeks or months? Link to comment
+papatom2 Posted August 16, 2006 Author Share Posted August 16, 2006 LOL. That really pins it down. Link to comment
+Shilo Posted August 16, 2006 Share Posted August 16, 2006 between 24 - 336 hours Thats only 1-14 days Now its anytime under 12 days Link to comment
+5¢ Posted August 17, 2006 Share Posted August 17, 2006 Can we add a way to see travel bugs we have already found? Meaning we could querry for caches, with travel bugs we have not found / discovered yet? Pretty please Link to comment
+Shilo Posted August 24, 2006 Share Posted August 24, 2006 (edited) We delayed the release as we were adding some other "features" together and wanted to do some proper testing before unleashing it on the public I noticed the TB/geocoin pages look slightly different. So is the original problem of this topic fixed? edit: spelling Edited August 24, 2006 by Shilo Link to comment
+Shilo Posted August 28, 2006 Share Posted August 28, 2006 between 24 - 336 hours Time is almost up Link to comment
+Shilo Posted September 7, 2006 Share Posted September 7, 2006 between 24 - 336 hours 336 hours is way past. Any update on this? I ran a PQ last night and its still giving wrong TB/coin info. Link to comment
Recommended Posts