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
This post has been closed. You can still view previous posts, but you can't post any new replies.

Stuck on black loading screen is *not* resolved

The previous thread marks this as resolved, but I'm still having the problem. I'm running Firefox 39.0 on Ubuntu 14.04.  Everything in Roll20 worked peachy through last night. Now, when I try to launch a campaign, I get the black screen "Loading..." and it just stops there. I tried clearing my cache and restarting Firefox; it made no difference. I have tried disabling all extensions and restarting Firefox; it makes no difference.
I think I saw this in the other thread.  Looking at the web console, I see the following error which looks ominous: 15:28:15.678 SyntaxError: missing } after function body1 app.js:4:15434 15:28:15.695 Use of getUserData() or setUserData() is deprecated. Use WeakMap or element.dataset instead.1 cacheobj.js:870:0 15:28:15.707 ReferenceError: soundManager is not defined1 startjs:28:0 (Everything else is a warning about use of a SHA-1 certificate.)
Hmmm... mayhaps is this the result of current roll20 site update and that they did not polished the bugs yet concerning i.e Firefox/Ubuntu combo? I'm using Chrome/Windows 7 myself and I didn't had loading screen problem once. Also this "soundManager" thing... hm, generally roll20 tries to use your microphone when you first get into game so maybe there's something going on with sound card/settings? I'm really not an expert in technical things, but I just hope me throwing different possible angles on the problem will help :) Cheers :)
So it's some sort of poisoned cache issue. Can you try now (I pushed out a new file version to try and force a cache update)?
Yes, it's working now.