indy2005's Forum Posts

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

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Neither makes any difference...has to be the apk

  • > The cost of ads is 20-30 FPS? I only trigger an ad on game over?

    It shouldn't be. But this is standard troubleshooting procedure. Right now you know there is difference in performance between the apk and chrome. One difference between them is admob. So if you disable the admob events, you will know IF that is causing the performance difference.

    First I will disable the events, then I will try with the plug-in completely removed from the project if there is no difference.

  • You could try disabling anything related to admob and see if that changes the apk performance. Would at least narrow down the problem, or rule out admob as the cause.

    The cost of ads is 20-30 FPS? I only trigger an ad on game over?

  • AdMob plug-in for interstitial and reward ads

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

    60-61 FPS on chrome on this device. Issue is purely with APK. And my buggy gpu manages to play any other Play Store 2D game without any issues.

  • Possibly some issue with the compiling to Android then.

    What export method did you use ?

    Debug APK. 40 FPS on APK Vs 60 FPS on chrome on the mobile device.

  • The fact it runs fine on chrome on the device - leads me to believe it’s the apk...or the wrapper

  • Now this is interesting. Run the game from the editor in chrome...60 FPS on the phone. The debug APK on the same phone sucks balls. Loading up the editor on mobile and running it, gives me what I would expect for such a simple game.

  • I guess I am somewhat nervous of posting my entire capx publicly. It’s the first game I ever got close to completing for publishing.

  • I am not making Doom 5. It’s a spinning target sprite with some ballon sprites pinned to it.

  • I guess the answer is to create in GMS2...it's a 2 layout app with no scrolling.80 objects. If I have to optimise the crap out of that in Construct, I owe it to myself to try another engine for comparison.

  • Any use? My concern is...if my phone was so crap...why can I play Dead Cells but not my game!!