-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Live demos don't work on multiple browsers #1
Comments
I think this should be resolved in the new version with sdf support. Closing for now. |
Sorry if it's obnoxious to follow up so quickly, but I don't think the live demo build has been updated to reflect this fix (I still get this error). retrace seems really cool and I'm excited to try it out! I've written a lot of SDFs in the past, never with tooling 1/10 as nice as this :) |
@MaxBittker No, not at all, and thanks :) It's a bit hard for me to debug this though, as all scenes work perfectly for me on both my home & work mac os setups running the latest/almost latest versions of chrome & firefox. Do you experience the same issue with all scenes? Could you provide some info on your environment? (os, browser, screen resolution, gpu & gpu driver details would be fantastic). I recognise this error string, though. For me it usually has appeared after the webgl context has been lost at one point (i.e. webgl has crashed), in which case a browser restart fixes it for me. That'd be the first thing I'd try :) Or, you're running Windows and are experiencing loooong shader compilation times (and probably other issues) due to ANGLE, which can cause context loss/a webgl crash. In which case there isn't much to do I think (you should still be able to run most demos with the sdf render mode, though). |
Tested with Firefox 67.0.2 and Chrome 76.0.3809.12.
Firefox console prints out:
es6.promise.js:110 Unhandled promise rejection TypeError: "this.uniforms[e] is undefined"
And Chrome prints:
picogl.js:3928 Uncaught (in promise) TypeError: Cannot read property 'set' of undefined
Despite the different error messages both browsers deliver an identical page. It's completely black but the menu as well as the code editor are visible.
The text was updated successfully, but these errors were encountered: