Description
Description
Hi,
I’ve been experimenting with WebGPU and tried enabling it in my project, but encountered the following error (in console):
luma.gl: WebGPU command submission failed: [Invalid CommandBuffer] is invalid.
While calling [Queue].Submit([[Invalid CommandBuffer]])
Command encoding already finished.
While finishing [CommandEncoder (unlabeled)].
At first, I assumed it was an issue with my own project setup. However, I see the same error even when running the test app from the Deck.gl repo:
https://github.com/visgl/deck.gl/blob/master/test/apps/webgpu-scatterplot/
I understand WebGPU support is still in development, but I’m really excited about the performance improvements it can bring to my project and would appreciate any insights or updates. I also wanted to check if there's any documentation available for properly enabling WebGPU. From my testing, it seems that WebGL is still the default renderer, and WebGPU only activates when explicitly passing an adapter via device props. If that’s the intended behavior, some clarification in the documentation would be super helpful.
Also, if possible, I’d love to know if there’s a rough timeline for when a more stable integration is expected. Thank you!
Flavors
- Script tag
- React
- Python/Jupyter notebook
- MapboxOverlay
- GoogleMapsOverlay
- CARTO
- ArcGIS
Expected Behavior
DeckGL loads smoothly and utilizes WebGPU when available
Steps to Reproduce
Load https://github.com/visgl/deck.gl/blob/master/test/apps/webgpu-scatterplot/ as per the instructions
Check console logs
Environment
- Framework version: Latest
- Browser: Google chrome
- OS: Windows
Logs
luma.gl: WebGPU command submission failed: [Invalid CommandBuffer] is invalid.
While calling [Queue].Submit([[Invalid CommandBuffer]])
Command encoding already finished.
While finishing [CommandEncoder (unlabeled)].