Ashley's Forum Posts

  • After a wait, it will continue running actions and remaining sub-events. So in the second case you set the variable to 1, then immediately compare it to 1.

    In the first case you set the variable to 1 after a wait, then the next tick the variable resets, and it compares it to 1.

  • It's hard to read the text in that image because there's something strange about the quality, but the code appears to reference a plugin named StraniAnelli_HTMLElement.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Oh, let's not do this again. Those platforms had far worse problems of their own (game-ending memory leaks, whole categories of plugins that didn't work, etc. etc.)

    GPU driver bugs are pretty much random, and the fact some different technology works around one specific problem, does not work around the fact that GPU driver bugs can easily ruin your day whatever you're doing. It's an industry-wide problem.

  • It doesn't look like Construct's code where the problem is happening. I would guess you have a broken third-party addon. You will need to contact the addon developer about it.

  • Ashley question out of curiosity - are there cases where driver bugs affect cordova app performance but not chrome performance?

    Yep.

    Also the Chrome browser and the WebView (used in Cordova apps) have different GPU driver blacklists, which means you can get fast GPU acceleration in the Chrome browser but slow software rendering in the APK. It's also really hard to identify because chrome://gpu in the browser will tell you everything's OK, but when you run in an APK everything's slower. So it's entirely possible a GPU driver bug affecting only the WebView is either causing poor performance only in the APK, or has caused Google to blacklist the GPU driver only in the APK. That would explain what's being observed here (but this is currently a theory, there isn't proof yet).

    The vast majority of devices should not be affected by issues like this. It's just an unlucky few. And GPU driver issues affect pretty much all gaming technology, and frequently in worse ways (e.g. blank screen or startup crashes for native apps - at least web tech can get the game to run)

  • My best guess from the (not much) information available here is the device has a buggy GPU driver that kills performance. It's pretty rare these days but is usually the main reason you end up with poor performance in strange circumstances. If you test a variety of other devices, I would guess the other devices would all be just fine, and only your specific device has an issue.

    If you only have one device to test on, and it's got some kind of problem, it's easy to imagine that all devices have the problem, or that it's Construct's fault, or HTML5 sucks, etc. This is why it's important to test on a few devices, to make sure you're not misled by specific-device issues. Android in particular is a bit of a minefield with lots of quirky different devices around. And if I'm right about the GPU driver issue, ironically that is to do with the native technology on the device provided by one of the manufacturers - and nothing to do with your game, Construct, or HTML5.

  • r215 just came out and changes how this works, so try that.

  • It should be working in the C3 runtime as well. The C2 runtime has very little usage and is being retired soon, so the vast majority of everyone using IAP is using the C3 runtime, and as far as I know it's working fine for them.

  • Projects should open regardless of which browser, or which version of the browser, is saving or opening the project. The file format has nothing to do with the browser engine and doesn't change at all depending on it. So it should always work. As Kyatric noted we'd need all the information requested in a bug report to be able to help.

  • That looks like a bug in the Chromium 84 browser engine that was since fixed. It should work if you update the browser to the latest version (85+).

  • It should work. Opera also uses the same browser engine as Chrome (Chromium). It's hard to say more without more information though.

  • You do not have permission to view this post

  • I think the iPad 2 has stopped receiving software updates, so its version of Safari is probably out of date.

  • This should be fixed in r215:

    Bug Fixes: 9-patch: could render alpha incorrectly on corners in editor

  • It's not a bug. The engine has to create a texture to render the text to. If you make the text object huge, it exceeds the maximum texture size, so the engine compensates by reducing the quality of the text. Just use a reasonably sized text object and this should never be a problem.