indy2005's Forum Posts

  • > Ribis would you mind testing his APK on your Samsung Galaxy Note 10? That has a Mali G-series GPU too...

    I just tested it. CPU usage between 17/24.

    The game runs at 60fps, however every time you start a new game there is a significant drop for like a second.

    There is a while loop at the start to randomise positions until there is no overlap. But the curtains shouldn’t open until that has completed, and that group is the deactivated. Maybe the curtains are opening before that while loop has completed with placement of targets?

  • Thanks for testing 👍🏻. I will do. If you have an issue with WebView on your mobile - I guess no Cordova game will work

  • Google have confirmed my GPU has all necessary extensions enabled and is not block listed...

  • Ashley told me to raise an issue with Chrome team about poor APK performance, when performance on Chrome was OK. Interestingly Chrome team directed me to this discussion posted by the Construct team themselves. This reads to a nivice like me, that there are many people reporting my same issue, and that an engine whic delivers via WebView could be problematic for a considerable number of users, as the disabling of certain instructions on certain GPUs on WebView, is for security reasons and is disables WebGL. That would explain my game running like a dog with 2 legs, but the Google team have stayed my GPU instruction set is fine and not blocked...

    bugs.chromium.org/p/chromium/issues/detail

  • I think the only way to make progress on this (or any other similar device-specific issues where Chrome is different to an APK) is:

    1. Make the most minimal project you can that demonstrates a performance difference between Chrome and APK, with on-screen performance measurements
    2. Export both to the web and as an APK
    3. File an issue with Google at crbug.com and include:
      • Report "Performance difference between Chrome and Android WebView on <device>" (refer to the APK as the "Android WebView", since that's what Google call it)
      • Links to both the web version and APK
      • Steps to reproduce in both cases and observed measurements
      • Details about the specific device model (in this case Doogee N20)

    I'm only speculating about what the problems may be (it's just experience has shown GPU drivers are usually the culprit in this type of thing). If you can get Google to look in to it, they should have the development tools and engineers to work out what the problem really is, and hopefully solve it.

    Hi Ashley,

    I raised it with Chrome team. Interestingly they directed me to a similar issue which was raised by the Construct developers, which implies that WebView is causing an issue for a lot of people.

    This is the issue raised by Construct team.

    bugs.chromium.org/p/chromium/issues/detail

  • I think the only way to make progress on this (or any other similar device-specific issues where Chrome is different to an APK) is:

    1. Make the most minimal project you can that demonstrates a performance difference between Chrome and APK, with on-screen performance measurements
    2. Export both to the web and as an APK
    3. File an issue with Google at crbug.com and include:
      • Report "Performance difference between Chrome and Android WebView on <device>" (refer to the APK as the "Android WebView", since that's what Google call it)
      • Links to both the web version and APK
      • Steps to reproduce in both cases and observed measurements
      • Details about the specific device model (in this case Doogee N20)

    I'm only speculating about what the problems may be (it's just experience has shown GPU drivers are usually the culprit in this type of thing). If you can get Google to look in to it, they should have the development tools and engineers to work out what the problem really is, and hopefully solve it.

    There is a huge difference in the Animation Frame Fired utilisation on the APK.

    APK

    Chrome

  • > I could send my APK to a trustworthy individual to run on a mid to low end device??

    Send a message at supportrbj@construct.net with your debug apk.

    > Is there any way to display information like chrome://gpu on an exported apk?

    Debug your APK

  • > I could send my APK to a trustworthy individual to run on a mid to low end device??

    Send a message at supportije@construct.net with your debug apk.

    > Is there any way to display information like chrome://gpu on an exported apk?

    Debug your APK

  • > I could send my APK to a trustworthy individual to run on a mid to low end device??

    Send a message at supportmzs@construct.net with your debug apk.

    > Is there any way to display information like chrome://gpu on an exported apk?

    Debug your APK

    Would you want the capx too?

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Try disabling workers in settings

    I've had an issue of game not running on a Samsung Galaxy with workers enabled, ran fine with workers disabled

    Bought me about 4 FPS, thanks. Despite it saying 45 FPS, it is just janky. Specifically noticeable in the rotation of the main central sprite via a rotation behaviour.

  • Process of elimination.

    Might want to consider who your target audience is, unless it's just you.

    I bought a mid end phone to check performance on lower end devices, expecting a single viewport application with 300 events and 80 sprites to be a good first game to launch. I don't have a better phone to test it on, so at the moment i have no way of knowing if it will be crap for everyone.

  • Apparently the idea of testing other phones has gone out the window.

    I will just dust off my other 40 android phones

  • Not really buying the whole my GPU is blacklisted, based on how I see my other games playing - including Dead Cells on this phone.

  • Question...if my GPU is api blacklisted, why are all my Google Play games running silky smooth? Surely if I was being forced into software rendering, every game would run like crap...

  • Apparently Godot sucks balls on Android, and just seen the price of the mobile exporters for GMS2. May have a play with Unity. If my driver is blacklisted on APK I will see the same problems....if not..........