Guide: Fix Jank in r190+ Node-Webkit Export

  • Chrome is the dominant browsers, for Win 7/8, so its the goto browser for testing for most of us.

    True indeed, but given the size of Google and the resources at its disposal you can't help but ask why this ongoing issue has not been solved already, options:

      Can't fix it Don't care - the fix can wait till google is ready HTML5 is not ready for serious workloads - like games

    This isn't a C2 problem but... it is a C2 problem in the end, because we rely on these end tools to export.

    Not a C2 problem, but a C2 flaw, because it is 100% reliant on third parties who simply aren't concerned enough to give priority to the bugs they introduce.

    HTML5 is designed for the web, fine, we get that, but this situation is critical because the web (Chrome & Firefox being the bulk) currently is broken for HTML5 games.

    Sadly this problem is inherent to the web. Browser wars, inconsistencies, and unfixed bugs, have always been the way of the web. It is not likely to ever improve....

    So atm, here's the export options:....

    The way I see it, the only export option right now is Win8. All the other options are broken.

    szymek

    There's nothing unsolvable here, we should see improve through 2015 and beyond

    Now that does sound familiar....

    Saddest part:

    Construct 2 is easily the best 2D game dev tool around (imo) - excellent work flow, frequent updates, prompt bug fixes, new features continually added.

    But it constantly gets broken for the most part - if you want the world to play your game - by third party dependencies!!!

    This kind of thing is always going to be an issue, has been in the past, is right now, and will again be in the future.

    The only option we have, each time the other party creates a bug, is to wait for the other party to fix the problem...

    Of course in the meantime you cop the 'what a crappy game' from the would-be player\customer - well that is good for business...

  • "Can't fix it

    Don't care - the fix can wait till google is ready

    HTML5 is not ready for serious workloads - like games"

    We all know that 2 is the anwser, they broke it so they can fix it, and html5 before that went really great for gaming, however that is getting ridiculous at this point, it is not like they think of chrome as a simple browser, how could that kind of things go into the stable channel, the nice part is that there does not seems to be a way for us to fix it (so nobody will simply workaround that).

    I know the situation will get better, and as a non-wrapper and non-profit user it really does not matter for me what happens to node-webkit or crosswalk, but that makes me wonder about who is really trying to do what, like it is not the first time the chromium takes décisions that bothers everyone (the XP and Vista dropped support, sure XP is not backed up by microsoft anymore, but Vista I am not sure.), however the fact is: if firefox got broken, or even opera, the situation would not be as bad, that is plain stupid, we should not have to rely on how one browser is performing, how did that happen?

  • Question - I'm using C2 64bit version for windows 8. Would I experience any problems by instead running C2 32bit in order to use NW 10.5? Thanks.

  • PSI

    You shouldn't. Just smoother gameplay.

  • TiAm - thank you.

  • PSI

    Actually, just to clarify, you aren't talking about the actual C2 IDE are you? Doesn't matter whether you use the 64 or 32 bit version of C2; all that matters is the version of the node-webkit exporter.

  • OK, got it. Thanks.

  • BTW - thanks for this guide - works great!

  • New build!

    Node Webkit v0.11.5 (based on Chromium 38)

    https://www.scirra.com/node-webkit

  • New build!

    Node Webkit v0.11.5 (based on Chromium 38)

    https://www.scirra.com/node-webkit

    Any better? I'm thinking we won't see a significant improvement til chromium 39-40...but I'd love to be surprised. <img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile">

  • Thanks for this guide, was a great help, seems like this improve performances (running on 32bits and not 64bits). I will try it on a bigger project to see if it helps. I have a really noob question though. Is it possible to export for the web with a different exporter (using base construct2 web exporter) ? (Since the jerkiness happens on chrome browser with the web exporter).Thanks

  • > New build!

    >

    > Node Webkit v0.11.5 (based on Chromium 38)

    >

    > https://www.scirra.com/node-webkit

    >

    Any better? I'm thinking we won't see a significant improvement til chromium 39-40...but I'd love to be surprised. <img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile">

    I was running 11.5 It's better than previous, but I have way better performance from 10.5 after following this guide. This Node issue / C2 export issue is beyond annoying. It's getting to a point where I am seriously considering switching from C2 to something that exports to desktop properly. Nothing like working on your game and then out of no where.. janky stuttering. Try and fix, and realize that Node is the root cause. Pretty dampening to the workflow, motivation, and optimization efforts. <img src="{SMILIES_PATH}/icon_neutral.gif" alt=":|" title="Neutral">

  • >

    > > New build!

    > >

    > > Node Webkit v0.11.5 (based on Chromium 38)

    > >

    > > https://www.scirra.com/node-webkit

    > >

    >

    > Any better? I'm thinking we won't see a significant improvement til chromium 39-40...but I'd love to be surprised. <img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile">

    >

    I was running 11.5 It's better than previous, but I have way better performance from 10.5 after following this guide. This Node issue / C2 export issue is beyond annoying. It's getting to a point where I am seriously considering switching from C2 to something that exports to desktop properly. Nothing like working on your game and then out of no where.. janky stuttering. Try and fix, and realize that Node is the root cause. Pretty dampening to the workflow, motivation, and optimization efforts. <img src="{SMILIES_PATH}/icon_neutral.gif" alt=":|" title="Neutral">

    I was feeling the same Facecjf. It's sad, and i don't think Construct2 can do anything about it (and we are not talking about any kind of bad optimisation, since it's the same with super basic tests).

    I'm annoyed too but my project was still in the prototype phase and not too advanced so ...

    But for those how had games running smoothly before, it must be a real down.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • I was feeling the same Facecjf. It's sad, and i don't think Construct2 can do anything about it (and we are not talking about any kind of bad optimisation, since it's the same with super basic tests).

    I'm annoyed too but my project was still in the prototype phase and not too advanced so ...

    But for those how had games running smoothly before, it must be a real down.

    It is and it isn't. It's the nature of constructs reliance on 3rd party wrappers. I've found that what doesn't work now... will work in about 4 months.

    Don't get me wrong, C2 is amazing for 2D game development, with great update cycles, stability, and features. I just wish desktop publishing was better and not reliant on Node.

  • For information purposes:

    I tested previews and exports with the following versions of C2 and NW.

    (r190, r192, and r193) + NW 11.5 = still stuttering.

    I reverted back to NW 10.5 (Win 32bit) and it's smooth again.

    Hardware Specs:

    xeon 3.5ghz

    32 gb ram

    solid states

    nvidia gtx650 ti

    These are just my findings, though I am curious of others results as well

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