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.

Game will not launch, stuck on "Loading..."

Resubmitting this topic, as the first time it failed with error code: 53ced15aeda2426f98d848c646eff2fc I'm not able to load the game editor. The chat and sidebar load, but the main page is stuck at the "Loading..." page. It works on Brave, but not on Firefox. Below is my info and console output, let me know if you need anything else. Firefox 75.0 (64-bit) Ubuntu 18.04.4 Extensions: Lastpass uBlock (disabled) Beyond20 (disabled) Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). onloadwff.js :71:803617 Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). editor :12:1 Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). editor :13:1 JQMIGRATE: Logging is active jquery.migrate.js :20:10 Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). 3 jquery-1.9.1.js :1444:6 Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). 3 jquery-1.9.1.js :1450:5 This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. editor CAMPAIGN ID: 5150837 startjs :15:9 RTCIceServer.url is deprecated! Use urls instead. 3 app.js :278 70 app.js :552:26453 TOUCH SUPPORTED: false app.js :554:15373 USING WEBGL ACCELERATION... app.js :554:15813 WEBGL STARTUP SUCCESS app.js :554:16286 Custom Sheet Translation app.js :556:17906 Loading Custom character sheet. app.js :574:12565 Including compendium template css. app.js :574:12682 tuts loaded tutorial_tips.js :7:10 Invalid URI. Load of media resource failed. editor Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). inspectlet.js :4:8118 Starting up WEB WORKER sheetsandboxworker.js :682:10 unreachable code after return statement ffmpeg-worker-webm.3.js :153:13433 unreachable code after return statement ffmpeg-worker-webm.3.js :164:111617 Final page load. app.js :563:18016 Auth'ed. app.js :561:18867 Go post auth! app.js :561:19064 unreachable code after return statement ffmpeg-worker-webm.3.js :183:15520 unreachable code after return statement ffmpeg-worker-webm.3.js :187:17706 unreachable code after return statement ffmpeg-worker-webm.3.js :187:19502 initial setup app.js :561:19201 unreachable code after return statement ffmpeg-worker-webm.3.js :189:21299 unreachable code after return statement ffmpeg-worker-webm.3.js :190:21237 unreachable code after return statement ffmpeg-worker-webm.3.js :194:17922 unreachable code after return statement ffmpeg-worker-webm.3.js :194:39367 unreachable code after return statement ffmpeg-worker-webm.3.js :197:71233 joining game... app.js :561:28321 Full load page! 32 app.js :558:21774 We have 50 pages app.js :561:20321 Successfully compiled asm.js code (total compilation time 5812ms) ffmpeg-worker-webm.3.js Deferred finish joining... app.js :561:28411 Firebase Online app.js :552:28237 WebGL warning: linkProgram: Must have an compiled fragment shader attached. app.js :553:1142 Error: Statuses: DELETE: false LINK: false VALIDATE: false Counts: ATTACHED SHADERS: 2 ACTIVE ATTRIBUTES: 0 ACTIVE UNIFORMS: 0 Info Log: Must have an compiled fragment shader attached. Vertex shader debug info: Fragment shader debug info: 0:2(12): warning: extension `GL_ARB_gpu_shader5' unsupported in fragment shader 0:16(36): error: sampler arrays indexed with non-constant expressions are forbidden in GLSL 1.30 and later
Bumping this issue- any fix for this?
1588530384

Edited 1588530747
I'm encountering this issue as well - it seems to only occur with Dynamic Lighting enabled. Firefox 75.0 Ubuntu 18.04.4 LTS Error: "Statuses: DELETE: false LINK: false VALIDATE: false Counts: ATTACHED SHADERS: 2 ACTIVE ATTRIBUTES: 0 ACTIVE UNIFORMS: 0 Info Log: Must have an compiled fragment shader attached. Vertex shader debug info: Fragment shader debug info: 0:2(12): warning: extension `GL_ARB_gpu_shader5' unsupported in fragment shader 0:16(36): error: sampler arrays indexed with non-constant expressions are forbidden in GLSL 1.30 and later " &nbsp;&nbsp;&nbsp;&nbsp; _createProgram <a href="https://app.roll20.net/assets/app.js?1588107306" rel="nofollow">https://app.roll20.net/assets/app.js?1588107306</a> : 555 &nbsp;&nbsp;&nbsp;&nbsp; &lt;anonymous&gt; <a href="https://app.roll20.net/assets/app.js?1588107306" rel="nofollow">https://app.roll20.net/assets/app.js?1588107306</a> : 555 &nbsp;&nbsp;&nbsp;&nbsp; &lt;anonymous&gt; <a href="https://app.roll20.net/assets/app.js?1588107306" rel="nofollow">https://app.roll20.net/assets/app.js?1588107306</a> : 555 &nbsp;&nbsp;&nbsp;&nbsp; &lt;anonymous&gt; <a href="https://app.roll20.net/assets/app.js?1588107306" rel="nofollow">https://app.roll20.net/assets/app.js?1588107306</a> : 554 &nbsp;&nbsp;&nbsp;&nbsp; a <a href="https://app.roll20.net/assets/app.js?1588107306" rel="nofollow">https://app.roll20.net/assets/app.js?1588107306</a> : 554 I've tested Chromium and Brave and was unable to get them to work either
I was able to resolve this issue a couple ways: I was able to get it to work in Chromium at least by disabling Hardware Acceleration. I installed the correct/third-party (not neoveau) Nvidia drivers for the GPU and it loads fine now!
Hello, To keep things consolidated and organized, we would ask that you please refer to the&nbsp; main thread for this issue seen here &nbsp;- it will have the most recent communications and updates from us. As such, we’re going to go ahead and close this post. Thank you!