Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

Microsoft Edge & Google Chrome Issues

Hi, Over the last couple of weeks or so, everytime I use the mouse I get the message that Microsoft Edge isn't responding. Then, after a few seconds, it does respond. Very frustrating as you can imagine. So, I tried using Google Chrome the last couple of days and great, it responds! However, when I try to open up a character sheet it won't do it...argh!! Is it just my PC or is anyone else experiencing the same issues? Thanks.
I don't use Edge (it works for some people but it's not supported by Roll20), but in both Chrome and Firefox the characters sheets ( D&D 5E by Roll20 ) can be slow loading at times, especially ones with lots of spells, but it's usually just the first time that they're called up. As for the mouse issue, try updating your mouse drivers; even if their currently up to date, drivers can get corrupted over time.
There are A TON of issues with FIREFOX lately! Regarding Jukebox, Character Sheets and others...
1719153899
B Simon Smith
Marketplace Creator
Microsoft Edge isn't supported by Roll20.  That means if you can get it to work, that's great. If not, then you'll get recommended to use Chrome or Firefox, the two supported browsers.
1719155277
keithcurtis
Forum Champion
Marketplace Creator
API Scripter
Hi Graham! In Google Chrome, try running Roll20 in an incognito/private browsing window. That might help diagnose if it is a browser extension that is causing your woes. Bad cache or cookie data is unlikely given that you apparently have not used Chrome for Roll20 before, but clearing it is worth the test, anyway. Speaking to Rick's point, if you have an alternate pointing device to your regular mouse, that also might be worth testing. This is not a common or widespread problem (at least there are no similar reports right now that I can see), so this might require some detective work.
Thanks everyone for their feedback, much appreciated!