NASA-AMMOS / NASA-AMMOS/3DTilesRendererJS
Plugins & Custom Materials: Support for WebGPURenderer
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2.5k
- Forks
- 416
- Avg merge
- 17h 52m
- Merged PRs (30d)
- 37
Description
Question
You indicated in https://github.com/NASA-AMMOS/3DTilesRendererJS/issues/1069 that the library is WebGPU-ready. However migrating my codebase from WebGL to WebGPU renderer, I have the following error coming from ImageOverlayPlugin:
TiledTextureComposer.js:46 THREE.NodeMaterial: Material "ShaderMaterial" is not compatible.
It looks like ImageOverlayPlugin is not WebGPU-ready. Any chance this can be supported soon? What would be the required effort? It looks like it would be quite significant (essentially a complete rewrite) and not fixable on the user side, right?
Supplemental Data
No response
Library Version
v0.4.18
Three.js Version
r181
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with ImageOverlayPlugin and the reported TiledTextureComposer.js error while reproducing the issue using three.js r181 and WebGPURenderer. Review issue #1069 for the library's WebGPU expectations. Done means ImageOverlayPlugin works with WebGPURenderer without the ShaderMaterial compatibility error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, three.js
- Domain
- computer-graphics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100