Ashley's Forum Posts

  • That message will not appear for any browser released in the past decade or so, so it's pretty much irrelevant now. Besides since C2 is now on track for retirement, only critical issues will be fixed from now on.

  • In practice 90%+ of users won't change the default. You'll either get complaints about latency, or complaints that the audio is glitching, depending on which default you choose. There isn't a good way to get it to work by default right now - I think the best thing to do is to wait and see if Google can fix it first.

  • There is no message, I was just saying it would be good to have the possibility to add a warning message with a link to update if WebView is out of date.

    When the WebView is out of date, it does show a message. It says "Software update needed" with instructions.

    WebView version 71.0.3578.99 should be able to run C3 runtime games just fine.

    So I think we're back to square 1 - I doubt it's solely because of an old WebView version. There must be something else going on.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Check your game isn't using more memory than is available on the device.

  • I'm afraid there's no good way to do this right now. I think some platforms automatically reduce the framerate to 30 FPS in power saving mode, but it's not controllable from the app itself. FWIW there's this Chrome issue proposing to implement support for dropping framerate, but it doesn't look actively worked on.

  • Why are you asking?

  • Driver bugs are random, and each app uses the GPU differently, so it still makes sense if it works in Firefox but not Chrome. You could just use Firefox if it works there.

  • They're internal details. You don't need to worry about it.

  • What are you doing that causes those to be logged so much? It should only happen when doing things like minimizing the browser or switching tab, which I'd have thought are rare actions to take during testing.

  • Well, that basically confirms it's a GPU driver bug. It means it will now be using software rendering and not using the GPU at all. It'll be slower, but at least it will look right.

  • You say the webview is out of date, but then you ask:

    Add a link at the start of the game when it’s not working to redirect to the android update page?

    The message shown when the webview is out of date already does show a link for the user to install the right update. So are you sure you are seeing this message? Are you sure it's to do with the webview version and not something else?

    FYI the update should be there if the device has auto-updated from the Google Play store any time in the past ~3 years. It's hard to imagine why this would not have been the case. If the devices are failing to update due to running out of storage, then there won't be room to bundle a browser engine with it either, so that seems like a non-starter - but it's not clear that's the reason the devices are out of date. If they really are using very old versions of the Android WebView, I'm keen to find out the reasons behind this, and would be grateful if you could shed some light on that.

    We have asked Google to add a minimum required WebView version for Android apps, but so far there doesn't appear to have been any progress on that. More customers asking in that issue might help.

  • A quick Google shows the device was released around 2008, so it's around 12 years old. That's pretty old, and unfortunately probably means no further software updates are available for it. The screenshots look like a graphics driver bug, so it may be that there is no solution other than to switch to a newer device. There is a chance you can get a newer driver directly from Intel that's not available on Windows Update though, so it's worth looking.

  • If I do so, ram usage at the start of the game (in export file) will be about 10 gbs! Out problem mainly is ram usage at the start.

    This is a sign of extremely inefficient game design. See the (old but still relevant) blog post Remember not to waste your memory.

    FWIW Construct 3 does provide more control over memory management. Also the small lag is because it's having to load images for the object on-the-spot. Construct 3 also does that asynchronously (in parallel with the game) which fixes the lag (although instead the object is momentarily invisible while its images load). The new C3 runtime is also much faster.

  • All Android 5+ devices are supported. We are not talking about any dropping of support at all here.

    If your device is 7 years old, I would guess there are only something like 1-2% of devices out there in active use that are that old. So if a 7 year old device doesn't run a game very well, I don't think it's a big problem. The game still runs though so it's supported.