Game Performance on Android sucks

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

come on ashley :D

you know it, a lot of a lot of people are reporting performance issue.

how ludei did fix this with his simple canvas+ plugin? it's a vey small plugin size and it fix the performance lag.

Is the plugin available for Construct3? I think I missed it

Thanks

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

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.

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

Send a message at supportsdn@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 supportjva@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?

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

Send a message at supportbsv@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 supportrlq@construct.net with your debug apk.

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

Debug your APK

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.

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

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

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

Are you sure that Godot sucks ball on Android? Because I have rarely heard anyone about poor 2d performance in Godot (infact many strongly suggest Godot for 2d games)

But it is not a no-code game engine either

And did you tested the apk in other mobiles? If no then please do it. In my case game never works on Samsung galaxy S5. And it was having everything. And including Panasonic eleuga A2 through which I am posting this post (in both mobiles game was running smoothly on chrome but apk simply pissed off)

Your argument that "if that big game works on my mobile then my construct game must also work on my mobile" is invalid. There is huge difference between native and wrap

And regarding distribution of apk file for testing,the only issue which I see is that someone may copy the mechanism and launch his/her game before you. But otherwise there are no such issues. It is almost impossible to reverse engineer the source code from apk file. Assets can still be stolen even after you launch the game on store and mechanism can(and will be if your game succeds on store) be copied and used by any other developer

Again repeating, please test the apk on other mobile also

Best of luck

Hi again

I tested your game and results were perfect.

Huawei Honor 7x smoothly running

Xiaomi mi 8a smoothly running

Finally There is issue with your mobile.

I was following your bug from day 1 and openly speaking I was very worried about your issue ( I can understand your frustration ). Hence at this mid night I spend 2 hours studying chrome bug report and testing your game on various other mobiles

Do a casual experiment. Go to "game show section" in construct 3 forum (here) and test any of the game uploaded to play store. I strongly guess that those games will not even work either

And relax. You can launch your game on play store without any worries

Now the theme of the question changes:-

How many players (mobile) are there in the market which does not work for webview? This is really a scary situation Ashley