I have "tried now" and it still doesn't work.
thank you,
Kaarlo.
Just an observation, there have been at least 6 unique issues described in this thread. Many pertain to bots but whether or not the root cause of these distinct issues is the same is anybody's guess...
"Issue loading assets for the game" error when trying to play bots.
"oops cannot load bots..." error when trying to play bots.
Flashing 3 dots and "thinking" forever when playing a bot in analysis mode.
Invisible chess board when playing bots.
Can't access daily games.
"Can't load recent game reviews or playing online."
to complement ThoughtPaddler's thoughtful observation, this is not even the only thread on this and similar issues. there are also "Chess.com is not working," with 34 posts, "Online games, Puzzles, And game Analysis won't work," 3 posts, "Chess.com puzzles glitch," 14 posts, "Chess.com not letting me play or do puzzles," 4 posts, "Chess.com website not loading bots or explorer" 15 posts, and "Can't play online," 46 posts. and yet there appears to be only one Mod, Martin_Stahl, who clearly has too much to do and little reward for his efforts. it can't be easy recruiting mods for a website that offers much but barely delivers.
take care,
Kaarlo.
to complement ThoughtPaddler's thoughtful observation, this is not even the only thread on this and similar issues. there are also "Chess.com is not working," with 34 posts, "Online games, Puzzles, And game Analysis won't work," 3 posts, "Chess.com puzzles glitch," 14 posts, "Chess.com not letting me play or do puzzles," 4 posts, "Chess.com website not loading bots or explorer" 15 posts, and "Can't play online," 46 posts. and yet there appears to be only one Mod, Martin_Stahl, who clearly has too much to do and little reward for his efforts. it can't be easy recruiting mods for a website that offers much but barely delivers.
take care,
Kaarlo.
Most of those reports are not site issues. They are client side, caused by content filters being used by schools organizations.
Kaarlo and MartinStahl,
I am still experiencing this issue. I don't think it will be fixed anytime soon. I hope that the issue is fixed for you guys soon. The purpose of this message though is I wanted to ask if there is any mods on this forum. Last, Martin_Stahl, are you a mod for the forum?
Thank you,
Pillowxz
Kaarlo and MartinStahl,
I am still experiencing this issue. I don't think it will be fixed anytime soon. I hope that the issue is fixed for you guys soon. The purpose of this message though is I wanted to ask if there is any mods on this forum. Last, Martin_Stahl, are you a mod for the forum?
Thank you,
Pillowxz
Yes, I'm a moderator.
Oops! We could not load this Bot. Please check your connection and try again!
This issue still exists for me. I am not a school or an organization. I have flushed firefox's cache.
Would be nice if somebody resolves this.
Oops! We could not load this Bot. Please check your connection and try again!
This issue still exists for me. I am not a school or an organization. I have flushed firefox's cache.
Would be nice if somebody resolves this.
I'd bet money your computer has an old CPU (Central Processing Unit / the main chip).
I was having that problem on a computer with a 2009 era AMD Phenom II CPU. It didn't matter which browser I was using or even which operating system (the computer is set up so I can choose to boot into either Windows or Linux). I've got another practically identical computer with a slightly newer 2011ish AMD FX CPU and it wasn't having the problem with bots. So, I ordered an AMD FX CPU off ebay and put it into this computer and immediately bots started working again with all browsers in both Linux and Windows and its been perfect ever since.
Oops! We could not load this Bot. Please check your connection and try again!
This issue still exists for me. I am not a school or an organization. I have flushed firefox's cache.
Would be nice if somebody resolves this.
Try this:
Method 1: Clear Local Storage for a Specific Site (DevTools)
This method is best for developers or clearing data for one site without affecting others.
Open the website in Firefox.
Press F12 (or Fn+F12 on some laptops) to open Developer Tools.
Click the Storage tab in the top menu.
Expand the Local Storage option in the left panel.
Right-click the domain name and select Delete All
Martin_Stahl,
Are you able to contact anyone that is a higher up in the chess.com staff to possibly help us out?
Thank you,
pillowwxz
If I was Martin, beyond telling everyone to clear their caches, I'd follow up on ThoughPaddler's discovery that he had the problem under multiple browser's under both Windows and Linux and after upgrading his CPU from an AMD Phenom II to an AMD FX the problem IMMEDIATELY VANISHED FROM ALL BROWSERS IN BOTH OPERATING SYSTEMS.
It's obvious to me that chess.com now requires CPU instructions that some older CPUs can't deliver. It is the entire reason I upgraded my CPU. I had debugged it on my end to the point where there was no other reasonable explanation. Start asking what CPUs people have and work with the Development Teams to either figure out the new minimum CPU specifications or better yet make it work again with the older CPUs.
To be clear, I am talking about the specific issue where the error message is:
"Oops! We could not load this Bot. Please check your connection and try again!"
(When this thread was started the error message was "Issue loading assets for the game" but a week or two into the problem the error message morphed into the Oops!... one)
Oops! We could not load this Bot. Please check your connection and try again! Am I the only one left with this complaint? All I've seen in this forum are the attempts of users to correct this problem. Are there no people from Chess.com able to address this issue?
Oops! We could not load this Bot. Please check your connection and try again! Am I the only one left with this complaint? All I've seen in this forum are the attempts of users to correct this problem. Are there no people from Chess.com able to address this issue?
That might happen if the bot assets haven't fully loaded, which could happen on slower connections.
That might happen if the bot assets haven't fully loaded, which could happen on slower connections.
Or, the error message could be completely bogus like it is. My measured connection speeds to speedtest.net are consistently over 200 Mbps and low latency.
I've posted several recountings of my experience getting this error message on a dual boot Linux/Windows 10 system with a whole slew of browsers and getting the error in every single browser under both Operating Systems and then changing NOTHING except installing a newer CPU and the error immediately vanished in all browsers in both operating systems.
The few people that have weighed in and told what CPUs they are using with this error message also have old CPUs like I was using. OBVIOUSLY chess.com has introduced a new CPU requirement. Quit wasting people's time with an error message that blames their perfectly fine connection and support that will only tell them numerous ways to clear their browser caches.
Your speed test doesn't measure between your client and the site servers. The traffic profile is also going to be a little different, though with bots in particular, that matters less.
I asked about bot code changes. I didn't get an answer but I know the engine used hasn't been actively developed for a years. It's possible some changes were made to better work on newer browsers, but it's less likely any CPU specific code would have been changed
Your speed test doesn't measure between your client and the site servers. The traffic profile is also going to be a little different, though with bots in particular, that matters less.
I asked about bot code changes. I didn't get an answer but I know the engine used hasn't been actively developed for a years. It's possible some changes were made to better work on newer browsers, but it's less likely any CPU specific code would have been changed
But the facts are the facts Martin and the fact is I only changed from an AMD Phenom II processor to an AMD FX processor and it resolved the issue with all browsers in both Linux and Windows.
Other facts are the starter of this thread, KaarloTuomi reported his CPU is an AMD A6-3620 (also very old and similar to the one I had the issue with) and in the other thread about this issue user hypertony-italy reported "same problem, old CPU".
In other words, we are 3 for 3 with users who have reported this issue and also reported the CPU they are experiencing it with.. in all 3 cases it was an old CPU.
Unfortunately the other users who've reported the issue haven't reported on their CPU type but I'd make a big bet its an old CPU in all cases.
The explanation has to fit the facts.
Can you try now?