Game stutters a lot when it runs under target frame rate, even at 90FPS!

From the Asset Store
Full game Construct 2 and Construct 3 to post on Google Play

    If you want to experiment with an alternate Android export option, try Trusted Web Activities. That is very much a web export with the proper Chrome browser wrapped up as an app you can publish to Google Play. However it's not clear how ads or IAP would work with that. So it might work well for free apps but monetised apps probably still need to go with Cordova.

    I'm happy to profile and optimise Construct projects if something isn't running well! Sometimes there are easy changes that can be made to the project to improve performance, and sometimes I can optimise Construct. These days even phones several years old can manage 10,000+ sprites on-screen and still get 30 FPS, so most modern devices generally seem to be pretty fast. However I must caution that sometimes there are problems like crappy GPU drivers that ruin performance - a long-standing scourge of the industry affecting all technologies, not just Construct - and it's not always feasible to work around. But usually those are device-specific and not something that causes a performance issue on all devices. Still I'm willing to look in to cases of poor performance if anyone shares them.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

    Interesting, didn't know about Trusted Web Activities. However this is different from the embedding method I described. First because it works only for Google Play but also because as you pointed out it wouldn't work for ads or IAP.

    Ashley, I sent to your ash@ adress a link to download the .apk of some of those games i'm thinking about. So you can check how the embedding works and how they manage to trigger actual Android ads if you're interested. Thanks to this method, those apps are only 15-20 Mb to download. Don't know if it's realistic but maybe it's worth investigating.

    EDIT : To answer that last post about locking the thread, I don't think this thread was about multiple topics with no connection. It was a particular performance issue case that turned into a discussion around the Mobile performance issue as a whole, which seems to be a recurring issue for C3 Mobile devs.

    Oh my this has turned into quite the discussion.

    Ashley Please dont get me wrong, in no way i would say that you constrcut guys are not hard working or optimizing all the time! I am a long term supporter of construct and brought you quite some customers over the years. Anyways, it can be very frustrating, -> webpreview works, firefox has problems with z fighting, on my tablet the fog is not working (lenovo tap 11, pretty common) where one would expect somehwat the same result on all devices) Please understand that this is still for me an hobby i dont earn money with, so it might take me a while to wrap things up, but i will try to bring a detailed report in the next days about the issues. I got another device to test on these days with a slightly weaker processor and as expected the issues are worse on them, but that could actually also be a device issue.

    I dont know yet how to analyze the problems on mobile really, but in what i found so far is that several frames in a row are skipped Therefore it appears extremly janky even at 110 FPS. As soon as i have more details i will file a bug report, but reproducing this on an minimal project, i am not sure if it is possible. But i will try. Other than that is to say that the cpu on all devices is under 50% but that might be bcause of single core usage. Anways, thank you for the repply!

    Unfortunately threads like this become entirely unmanageable as it has combined several entirely different topics: a known issue with worker mode with a workaround, general performance questions, compatibility concerns, Construct Animate, staffing, feature requests, new export options, and piracy. Such threads become too confused to be useful, which is why our Forum & Community guidelines include as a reason to lock threads:

    Chaotic changing of subject or mashing together different concerns, so there is no clear topic of conversation. There should be separate threads for separate topics.

    Therefore I'm closing this thread. I believe the original point of this thread is resolved by the worker mode known issue. However everyone is welcome to start new threads with different topics of conversation.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)