You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently using headless-gl (https://github.com/stackgl/headless-gl) for rendering in node.js to do tests and create images. While headless-gl is wonderful, it has no WebGL2 support and there is no indication that it ever will. Three.js has now removed WebGL1 support (mrdoob/three.js#27836). For the next Mol* version I would like to do the same and clean-up/simplify the code base.
I asked in the WebGL community group (https://groups.google.com/g/webgl-dev-list/c/cZJ6-uwaprU) what is used as a replacement for headless-gl and the suggestion is to use Puppeteer. Using the full Browser stack with Puppeteer will also make support for WebGPU in the future easier.
The text was updated successfully, but these errors were encountered:
Hey @JonStargaryen and @midlik I would very much appreciate it if you could raise this issue in your teams and see if you can contribute a solution. Thank you 🙏!
We are currently using
headless-gl
(https://github.com/stackgl/headless-gl) for rendering in node.js to do tests and create images. Whileheadless-gl
is wonderful, it has no WebGL2 support and there is no indication that it ever will. Three.js has now removed WebGL1 support (mrdoob/three.js#27836). For the next Mol* version I would like to do the same and clean-up/simplify the code base.I asked in the WebGL community group (https://groups.google.com/g/webgl-dev-list/c/cZJ6-uwaprU) what is used as a replacement for
headless-gl
and the suggestion is to use Puppeteer. Using the full Browser stack with Puppeteer will also make support for WebGPU in the future easier.The text was updated successfully, but these errors were encountered: