Ninjadoodle's Forum Posts

  • Ashley Sorry, just in case you missed my previous question, I just wanted to ask about the slow / stuttery Cordova exports again ...

    So, from what I understand there is nothing that can be done to improve this unless Google fixes the bug/issue?

    Thank you!

  • Ashley Same issue in both ... web app works perfectly smooth, and the debug apk is very stuttery.

  • Ashley Thank you for the reply. I've tried both r136 stable and the new r139. I've had a look, and my phone does indeed use this 'Mali-G51 MP4' GPU.

    It's a shame this, as my game runs perfectly fine on an old iPhone 5s, and yet on a new Android it looks like it's struggling. I'm kind of hesitant releasing an app on Android because of this.

    So, from what I understand there is nothing that can be done to improve this unless Google fixes the bug/issue?

  • Ashley My device is HUAWEI Nova 3i with Android 8.1, but I've also tried on Galaxy s7. Both of these phone run the Web version perfectly smooth, but as soon as the game is Cordova wrapped, there is noticeable stutter / slowdown.

    On iOS this doesn't seem to be an issue, and the game run smoothly all around - right now there is the freezing issue though.

    It's frustrating as the game looks so good as a Web app, yet as Cordova it looks horrible. I'm not really sure how to bug report this... Should I provide a small project that you guys can build for android and test?

  • Hi guys

    Just wondering if anyone might have some ideas here. I've tried wrapping a few of my games using Cordova, and while testing the debug versions I notice they are quite jerky / stuttery. The Web versions on the Sam phone work perfectly smooth.

    I wod like to get to the bottom of this, but dont know where to start.

    Thanks in advance :)

  • I've just tried 'use worker' with r139, and it still seems to be broken.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • — - Ok cool :) At least we know what it is, and no problem!

  • — - Ok, so I'm on Android v8.1 and everything seems to work fine on Chrome.

    Are you using any external plugins?

  • — Im gonna try to export Tower Raid using r139 and see if it works on Chrome :)

    I'll let you know soon!

  • — - Things seem to be ok for me as far as web exports go (r136 stable).

    Which version are you using?

  • Hi Guys - Thanks for the feedback :)

    — - I'm using r136 stable, and no outside plugins, only official C3 stuff. What are you having trouble with?

    AllanR - Lol, I'm never gonna get the sfx thing right! I know exactly what it is, I just keep forgetting to do it! I'll fix this ASAP :)

    The death counter is a cool idea, I might put this in when I update the game. 'Deaths', should have a score table of it's own hahaha.

  • Hi guys :)

    #7daygame number 7 is here, and this one is haaard lol. Should have called it 'Tower of Death', instead of 'Tower Raid'!

    WEEK 7 GAME - TOWER RAID

    PLAY GAME - ninjadoodle.com/games/towerraid

    YOUTUBE - youtu.be/CcI_6FjYjqY

    Have fun and post your best runs :)

  • Hi guys :)

    The latest prototype is here! In this episode, we learn how to make a jumping frog, using a combination of frame by frame animation, and tweens.

    WEEK 7 PROTOTYPE - FERGUS FROG

    YouTube: https://youtu.be/vKJ7fE2cN0k

    Example: https://ninjadoodle.com/prototypes/fergusfrog

    Project: https://ninjadoodle.com/prototypes/fergusfrog.c3p

  • Hmmm ok, its seems that if I load it from (https) ...

    ninjadoodle.com/games/test3

    it works just fine

    but this ...

    ninjadoodle.com/games/test3

    will make it hang at 99% (connection not secure).

    Is this is normal behaviour?

  • Hi guys

    When I reload my game in the browser it hands at 99%.

    ninjadoodle.com/games/test3

    The game loads perfectly fine on the first load.

    Also, the console doesn't show any errors, just a warning ...

    ***

    main.js:1 The AudioContext was not allowed to start. It must be resumed (or created) after a user gesture on the page. goo.gl/7K7WLu

    g_aGe main.js:1

    c3runtime.js:2 [WebGL] Shader program '<fill>' compilation log: WARNING: Output of vertex shader 'vTex' not read by fragment shader

    c3runtime.js:2 Made with Construct 3, the game and app creator :: construct.net

    c3runtime.js:2 [C3 runtime] Hosted in DOM, rendering with WebGL 2 [AMD Radeon Pro 580 OpenGL Engine]

    ***

    Any ideas would be awesome :)

    Thank you!