Construct WebGPU status thread

Post reply
Not favoritedFavorited Favorited 5 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

  • ForsakenBA - with buggy graphics drivers anything can happen. Even using an entirely different app could crash Construct.

  • Good news!

    Subscribe to Construct videos now

  • Seems like with iOS 26.2 / safari 26 there are loading issues on iOS apps made with Construct 3 and I guess it's a WebGPU issue, since with those new versions WebGPU became available to iOS users. Does anybody have similiar issues? Would you recommend to switch to WebGL for iOS exports?

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • What issues are you talking about exactly? Has an issue been filed either with Safari or us? That is the best way forward.

  • I didn't create an issue on github yet, since we can't replicate the issue and we are not sure what the issue exactly is. The only information I have: We have a game with around 500k users and everything was working fine. Since iOS 26.2 we get some reports on our discord from players, that they've updated to iOS 26.2 and since then the game restarts after loading. Loading means: We preload all main layout images in our loader layout. Once it's done, we go to the main layout. Some users provided videos. Once all images are loaded and the game goes to the main layout, the whole game restarts over and over again. I don't think it's a memory usage issue, since the game only uses ~70 MB memory usage (construct 3 debugger).

    After some research I found out that WebGPU got introduced with iOS 26.2 and there could be some issues / new limits or whatever. That's why I asked if there is any risk to use WebGL instead for the iOS builds.

  • WebGPU was actually introduced with iOS 26.0, so the update to iOS 26.2 should not have changed whether or not WebGPU was used. If you think WebGPU is causing an issue then you can disable WebGPU in your project properties and publish an update to the app. If an iOS update causes a problem then generally that's good evidence that the problem is with iOS or Safari, so you might want to file an issue with Apple directly about that.

  • Sorry my bad, the issue actually occured when updating to iOS 26.

    I will try WebGL within my next game-update and let you know if it's working then.

  • I had some issues on my iPhone 16 pro max when webgpu was enabled. The screen would flicker. After updating my device from iOS 26.2 to 26.4.2 I don't have this issue anymore. So webgpu is definately getting better on iOS!

  • That sounds like the known issue mentioned in the OP:

    Note however due to a Safari bug WebGPU rendering is glitchy from v26.0-26.3. It should however work correctly from v26.4+.

  • Some recent stats I got from webGPU: ~5% of devices appear to be failing with "Error creating WebGPU renderer" (something along those lines). I'm not sure if this is a breaking error or if Construct falls back to WebGL if it happens. Data is from a couple thousand random players.

  • Construct should fall back to creating a WebGL renderer if there is an error creating a WebGPU renderer.

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