Vikingvikingviking's Forum Posts

  • parlingu Nice! Good looking and seem to work well. Out of curiosity, did you manage to add any a11y features to your app? If so I'm very interested in hearing more about it.

    Keep up the good work!

  • cesisco do you feel the problem is solved for those devices as of r248?

  • These were the devices I collected, but the Jank is much better after beta r248

    Samsung Galaxy A20e (OS 10) Mali-G71

    Samsung Galaxy S9 SM-G9600 (OS 10)

    Redmi 5 (OS 8.1.0) Adreno (TM) 506

    Alcatel A3XL (OS 7.0) Mali-T720

    cesisco do you have videos showing the level of jank for those devices?

    If I can get the example projects used I can test them on iPhone and we can compare the platforms.

  • Does anyone know the state of the list of devices that we tried to compile?

    It could be good to send it to the chromium devs even though it may only contain one device 😅

    I hope the issue will be solved. It's a bit problematic to release on android as long as the jankiness exists.

    Let me know if I can help, even though I don't have any android devices.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I tested the same S8 Galaxy with the R249 and still stutters the same, big jumps and stutters. It didn't make any difference in my case but it's nice to see that it's been at least testing new things to fix the issue with Android.

    Yeah, it's still very noticeable here. Would be nice if we still gathered examples with jankiness and contacted chromium team.

    Sorry, I didn't have much time for doing the test but I think we should just keep using that simple test that it been shared on the thread so we follow all one demo and it clearly shows the stutters plus has no events, I think it's perfect as its the simplest you can get to show the issue, but it looks for some the issue has been fixed already so not sure what to think any more.

    This is a good plan, keep it simple and the same. Makes it easier for everyone involved.

    Good work!

  • They only have easy access to Pixel devices(where this problem is not present), so it would be better to give them a substantial list of devices so there's a higher chance of this being tested.

    And I thing, it would be important to know if this is a problem on high-end/new Android devices apart from those Pixel devices

    I totally agree. I interpreted your earlier post as you were on your way to shut down the thread. I just thought better to send what we got so far.

  • If I can't get more devices, I'll assume that this problem is not relevant and it's only affecting a few devices, so continuing this thread is meaningless.

    We could always send the findings collected so far, who knows it could lead to a solution on those devices

  • I test with an iPhone7 and I can say my game which shows janking as an Android APK runs very smoothly on my iPhone7.

    Happy to hear that

  • Cascade Games

    For me, my iOS device is running construct games fine. I don’t notice any difference between chrome and the Cordova app.

    I'm using iPhone 11. It would be more interesting if anyone has an iPhone 6 or 7 that could be used for testing.

  • I'm sorry I'm not able to help out more.

    — wrote about a similar problem: construct.net/en/forum/construct-3/how-do-i-8/generate-apk-construct-apk-160655

    Together we can maybe escalate this more efficiently to the chromium devs.

  • Yeah, I can imagine, I don't have an android device but I feel this issue is a big problem. It could be that it is a chromium problem and not a Construct problem.

    If you go to the bug tracker you can that it seems like more people have the same experience, it is good to add a comment or start the issue because that might help with getting the problem solved quicker.

    Here is the bug tracker link: bugs.chromium.org/p/chromium/issues/detail

    If you feel like it, it would be good to tag this post with #android, #webview, #apk

  • Hello, good work you guys have put in.

    The projects that been tested do they all run fine on pixel devices?

    Also if it lagged on all the device except pixel it still a problem.

    I think the list of tested devices and OS versions should be compiled into a list and posted on the issue. This sounds like a significant issue as the mobile market is an important one. I don't own a android devices myself, but it would be nice to get the problem fixed.

    Could be helpful for the chromium devs to know so they have an easier time finding the issue if it is on their side.

    How are you guys generating the apk-files?

    I don't remember the workflow, if it is possible, try export a Cordova project and do the android wrapping manually.

  • Hello,

    I don’t have an answer but I gathered some info down below that’s about a current problem, would be interesting to here if you are experiencing the same issue.

    If I understand correctly, the problematic app-file is made with construct 3?

    Also, I interpret the text as there are more problems than just size.

    If you read this post: construct.net/en/forum/construct-3/general-discussion-7/chrome-mobile-vs-apk-160701

    Do you have similar performance problems?

    If so here is a the issue in the chromium bug tracker: bugs.chromium.org/p/chromium/issues/detail

  • One way would be to check the player and enemy's Y-position on collision.

    If the player's y-position is less than the enemy's y-position then it should that the player jumped on the enemy. Probably it needs some tweaks to work in some cases but it's a start.

    Check out the demo project "Kiwi Story", it has the functionality you're looking for.

    In Kiwi Story, Open the event sheet "eEnemies" and look at event 55 and event sheet "ePlayer" and event 35.

  • Don't force yourself to do it if you don't like it.

    If you like it, maybe another approach can help to motivate. Prototype more on paper. Plan more, split up features in smaller tasks. Join a game jam.