indy2005's Recent Forum Activity

  • You do not have permission to view this post

  • Were off...lol. If nothing else, I will learn a few things.

    godotengine.org/qa/82562/attempting-to-prevent-overlap

  • But it’s every device on the webview blacklist, which mine Google has confirmed is not.

  • Thanks...is that a permanent no?

  • Is there a way to creat an "Instant App" for Google Play via Construct 3 at all, even if it invoves opening the APK in Android Studio?

  • I guess you make your choice, great engine, rapid development but likely alienating users due to WebView...or go native. I will likely publish this via Construct based on feedback so far....but I do want to go through the experience of creating the same game in Godot. I like the scene model Godot uses...just a blow to finally build your first APK on your first project and find out you are unlucky. I would pay twice the monthly fee for Construct if it gave a native export option. In a way I am glad I didn't test on APK until the end, as I may have never finished it.

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

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • 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

indy2005's avatar

indy2005

Member since 3 May, 2015

Twitter
indy2005 has 1 followers

Trophy Case

  • 9-Year Club
  • x2
    Great Comment One of your comments gets 3 upvotes
  • Email Verified

Progress

11/44
How to earn trophies