Construct WebGPU status thread

I have a function that updates UI texts, and an event that triggers that function every tick during specific conditions: in WebGL it runs at 60fps, in WebGPU runs at around 10fps. If i disable the functions, runs again at 60fps.

WebGPU is hella slow at rendering text objects.

There is a known issue with WebGPU that updating textures seems significantly slower than WebGL. In Construct, changing Text objects and a few other things require updating a texture, so these cases may be slower than WebGL for the time being. I filed an issue about it back in June but it hasn't been sorted out yet. As WebGPU is still pretty new I think there may be a few early issues like this to be sorted out, but I think it's likely it will end up as fast or faster than WebGL in the long run.

There is a known issue with WebGPU that updating textures seems significantly slower than WebGL. In Construct, changing Text objects and a few other things require updating a texture, so these cases may be slower than WebGL for the time being. I filed an issue about it back in June but it hasn't been sorted out yet. As WebGPU is still pretty new I think there may be a few early issues like this to be sorted out, but I think it's likely it will end up as fast or faster than WebGL in the long run.

Gotcha. I was suspecting it depended on chromium, hopefully they'll fix that soon enough. I'll stick to WebGL for now, although i've set up everything to transition to WebGPU (updating effects).

There is also a known issue with WebGPU that rendering fails on Intel Gen12 LP GPUs. See this issue.

There is also a known issue with WebGPU that rendering fails on Intel Gen12 LP GPUs. See this issue.

Interesting. The weird thing about my situation is that it was literally rendering just fine and then suddenly stop right during the dev session. However, it appears to still work just fine in FireFox and Edge. Is there a Chrome flag i need to turn on or something? I already turned on the 2 available WebGPU flags for it but still no go.

Right now it still depends on use case. So, experiment with your project, try both renderers and see the results. Look at both CPU and GPU usage.

That looks a lot like this issue that I filed back in March (and is noted under "known issues" in the original post here). I'll add a comment noting the device you mentioned.

I wouldn't put much faith in webgpu and nwjs. Coming from Babylonjs, I noticed massive slow downs when zooming into individual polygons, it seems like each pixel drawn incurs some large overhead, zooming out was 60fps zooming into the single polygon until it hit full screen dropped to 10fps. Getting perfect performance in edge then deploying with nwjs only to find these slowdowns was a let down. Given the neglect nwjs now has I don't see it improving.