Construct WebGPU status thread

Post reply
3 favourites
From the Asset Store
Target 2.0 Slot HTML5 Construct 2 and Construct 3
$15 USD
Casino? money? who knows? but the target is the same!
bellborn's avatar
bellborn

  • 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.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • 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).

  • Been scratching my head on this for the past few days as my previews suddenly aren't displaying anymore on Chrome. I did the usual - cleared out everything, updated graphic drivers...etc. And still blank. It was only just recently that figured out that i had to turn off WebGPU rendering in the project itself (like literally set it to No, Auto doesn't doesn't do it) that the previews started loading again. Anyone else having this issue? I'm running on Chrome Version 123.0.6312.86 and Construct r385.

  • 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.

  • Just wanted to chime in, seems like I'm going with webGPU disabled for now since having it set to auto can just lead to very weird graphic corruptions on some "random" devices. I don't know if having it set to auto currently is appropriate considering it can be this unstable. I'd vouch for it to be set to "no" per default until this actually works stable on all devices that claim to support it and then do this:

    Screen recording from a friend

    Xiaomi 13 Pro, OS 1.0.9.0.UMBEUXM, Android version 14 UKQ1.230804.001

    Subscribe to Construct videos now

    EDIT: I've been told that it is set to "no" on stable releases. I had no idea because I'm always cruising on the beta branch! :D

  • 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.

Post reply
Return to board index
Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)