Search the Community

Thank you. Based on your advice I was able to test that my Firefox was able to run WebGL here: https://get.webgl.org Somehow in doing that test, the glitch got fixed.

Or check out previous posts in the forums about this, there were quite a few people having issues with WebGL when it first became a thing, so some of these might have the fix you need: https://forums.geocaching.com/GC/index.php?/search/&q=webgl&quick=1

See if you can get to the browse map by clicking the Play menu on the top of the screen and choose View Browse Map at the bottom. Or try going here for the browse map: https://www.geocaching.com/map But I would also do a google search for something like "enable webgl firefox windows11" and make sure you have everything enabled, something may have got turned off by a recent update.

When in the map and clicking the search geocaches button I get this new message: "The web browser you are currently using doesn’t support WebGL, which is needed to view this map. To view a map experience that supports your browser, please use our Browse map." There is a browse geocaches button but that just takes me back to my home. I am using Windows 11 with Firefox browser and both are up to date with the current versions. I have successfully used this set up for years without this problem. Any help would be appreciated. Thanks.

Yes, that did work. but this whole thing started because I use the "Map List" option in my Lists and that's NOT working. I went to the WebGL site and it showed the spinning cube and said my browser supports WebGL. My browser is up to date. Thanks for the suggestions. Marc

As I recall, those maps require WebGL to be installed and working. My old PC (12yo at the time) didn't have the hardware for it, and those maps worked quite badly as a result. You can check it here: https://get.webgl.org/

fixed it by going to about:config and setting webgl. force-enabled to true.

Dunno if it's related but I get this on the Search map with Firefox, but is ok on Chrome. TBH this could have been there for months as I never use the search map, and haven't yet looked at what I need to do to add/enable WebGL support :

Hi NiraD, Thanks, Your post led to a solution, although not the way you intended. I had seen that "Use hardware acceleration when available" setting advice days ago, and it was always in the ON position. So, I left it alone. But today, I decided to try cycling through the setting. I intended to turn it off, relaunch CHROME, then turn it on again, and relaunch again. When I turned the setting off, and relaunched, I went into Geocaching and tried the new (Non-browse) map. It worked!!! I then signed off Geocaching, went into the CHROME settings and turned the "acceleration" setting back on, and relaunched. The map didn't work. I got the "WebGL not supported" error message. Back to CHROME settings and turned the "acceleration" setting OFF, and relaunched. The map works. So, either CHROME is screwed up, or the advice to turn hardware acceleration on is wrong -- the "WebGL" map only works for me when "Use hardware acceleration when available" is set to "OFF".

I'm experiencing the same problem with WebGL not being supported. It started happening about a week ago. I updated Chrome as suggested. Still doesn't work. I'm still on Windows 7.

We’re sorry!The web browser you are currently using doesn’t support WebGL, which is needed to view this map.To view a map experience that supports your browser, please use our Browse map. Search Map is not working; see these topics for same issue I experience: Topic 365770 and Topic 365625; neither was helpful for my situation. Tuesday, Chrome update; immediately Search map stopped working and is currently broken. Wednesday, another Chrome update did not resolve this issue. Thursday (today) I rebooted Windows; still same issue. Windows 10 updates are current; no updates are pending. System does not meet minimum requirements for Win11. Chrome Version 104.0.5112.102 (Official Build) (64-bit) What do I try next?

Unable to map caches on Chrome. This is a huge inconvenience. Is there any way to get back to the previous version? We’re sorry! The web browser you are currently using doesn’t support WebGL, which is needed to view this map. To view a map experience that supports your browser, please use our Browse map.

I just clicked on "View larger map" from a cache page and received this message - did something change? I've never had issues before. Using Chrome on a Windows OS.: We’re sorry! The web browser you are currently using doesn’t support WebGL, which is needed to view this map. To view a map experience that supports your browser, please use our Browse map.

Right. The newer map ("Search" map is the name we've given it) needs a newer browser and hardware than the old ("Browse") map. System requirements were never published, but we've determined you need WebGL for sure. There's a test here: https://get.webgl.org/ Map doesn't support IE.

Has anybody seen a System Requirements page for the new map ("search map")? It's been a D5 puzzle... I know it needs WebGL (what's that?), and a modern browser (defined?)...

Old hardware? The video card in my 12yo ex-PC didn't have the modern-ness to run something called WebGL. There's a test button on the WebGL site. (A never-stated requirement...) If you can see the Browse button, that map should work.

Browser here is Firefox 71.0, Ubuntu Linux build, with the Ublock Origin and Decentreyes addons. WebGL is disabled and it is set to delete cookies on exit. I had no problem with the privacy prompt and it has not reappeared. After accepting the prompt, I have used the latest version of Waterfox on Windows 7 and managed to view and submit logs. I suspect any problems with the privacy panel are due to the non-availability, or incorrect performance, of a javascript function which is meant to intercept clicks on the accept button. If that is happening on a "vanilla" instance of a currently supported browser (installed "out of the box" with no subsequent configuration) then I venture to suggest that that is a problem GS needs to address with some despatch. If people with addons are noticing it I would suggest trying the browser with addons disabled.

Definitely not an XP/Firefox problem. Due to XP, still on Firefox 52.9.0. gc.com map working, and test page working fine here https://get.webgl.org/ WebGL came with Firefox 51, which is still supported on XP systems. See here > https://hacks.mozilla.org/2017/01/webgl-2-lands-in-firefox/ So if you've updated Firefox to at least that level, you should be functional.

I didn't mean, try going to those sites. I meant, if those sites are blocked by a script blocker, allow them. But that's not the issue for you, it seems. Check your browser settings, and make sure WebGl is enabled. What's your browser and version number?

It's an old-hardware issue, so don't waste your time/money on Windows 10. Groundspeak ticked a "vector tiles" checkbox when they built that map, which we've since figured out means, you need something called WebGL, which in turn needs a modern video card and a modern browser. (OS? Dunno.) Try this test here: https://get.webgl.org/ My 12yo hardware with current Firefox on current Linux failed that test, and thus the map failed too. (I no longer care; upgraded hardware.)

Are you able to see a spinning cube at https://get.webgl.org/ ? Groundspeak tried something bleeding edge, and the release notes thread is full of calamity. More info there. Even people who do see something on the screen don't seem happy about it. Psst, for better technical support in general, more info is needed. System specs in particular...

Hi Brendan. Sorry, I'm not seeing that; I still get the "snow" background with caches laid overtop. I'm using Firefox 66.0.2 (64-bit), Linux 4.15, about:config webgl all at defaults, and either "Use recommended performance settings" checked or "Use hardware acceleration when available" unchecked; doesn't matter. The key thing is I have old video hardware that flunks the test at get.webgl.org. And it's so old Nvidia no longer provides Linux drivers, meaning the open-source nouveau driver that I'm stuck with may be the culprit. I mention all this only in case it helps your devs, and indrectly, someone else. I'm upgrading my hardware shortly, mostly for other reasons, so it doesn't matter for me. EDIT: If I change webgl:disabled to true (non-default), then I do see the new modal window you mentioned. But that's obscure; I couldn't even find "webgl" in the preferences UI using their search feature. Anyway, moot for me; let's see if this fixes things for other people. EDIT: But that modal window redirects to the Browse Map (good) at my home coordinates (hardly useful).

Hi everyone, Thanks for sharing all your feedback on the new map, it is much appreciated. Once again, I should note that all of the feedback is read, considered, and serves as a valuable input when we decide what to work on next. Today’s deployment consists of the following: We have a fix for users that are running browsers that do not support WebGL. For those that are affected by this issue, they’ll now get a modal window with a link to access the older Browse map. As a reminder here’s the URL to the older Browse map https://www.geocaching.com/map/ The map will now only use the corrected coordinates to plot cache markers if the user has not found the cache. Fixed some placed-date issues with caches on the Search map. Please stay tuned to this forum thread for further updates. Best, Brendan

I doubt it's the operating system in this case (though it should be updated anyway). If you have old hardware, it probably fails this test: https://get.webgl.org/ Our esteemed hosts haven't said anything about this, but apparently you need working WebGL for the new default map to work. Note that the existing map still works, if you can get to it.

As it is, just moving the map is laggy for me. Laggy to respond, laggy to draw. It's a lot less laggy when I switch the map to Google Street, but it's still slower than the browse map. I suspect it's a webGL issue with my ancient machine (we did decide that the new map is built upon WebGL, right?).