`three.webgpu.min.js` to provide WebGLRenderer export

Questions
,
1

Would it be possible to add WebGLRenderer export when running under WebGL2 backend (without creating some conflict)?

It might help with current @monogrid, which does suggest some workaround but I noticed that with esm.sh mapping it is looking for WebGLRenderer export under the mapped three - this without @monogrid importing its own three.js version.

Also, current TextureUtils.js file is looking for the same.

For those who might be curious enough, currently experimental three.js WebGPU support is included in my experimental GLTF WebGPU viewer:

  • Its code can be seen here
  • Some features might not work properly (like exports that rely on TextureUtils.js)
  • Maybe keep console open so you could see any relevant errors / messages
  • Not necessarily a proper code use of WebGPU either
  • Try to ignore any customization I have been using
2

The idea of separate builds is to avoid having both renderers in one file. So I would say no, it is not possible to have WebGLRenderer included in three.webgpu.min.js.

When WebGPURenderer more matures, there will be no need for WebGLRenderer anymore so you can rely on the built-in WebGL fallback.

2 Likes