0 Favourites

Node-webkit performs poor all of a sudden?

  • Hi, I just updated to the latest Node webkit exporter, and I seem to experience very bad performance compared to my previous exports. Just wondering if anyone has the same problem?

    Thanks

  • HI Tinimations - did you change anything else? e.g. upgrade to a beta version of Construct2

  • I'm hesitant to upgrade my node-webkit since the last one was bad, and apparently this recent one is awful too?

    Keep your old Node-webkit installers, since they're not given on the site. Incase the situation doesn't improve for a few months.

  • hundredfold No I upgraded to the latest stable release that released yesterday.

    alspal Hmm actually I'm not sure that works. When I tried to export with the node webkit I original had (which was also downloaded from scirra btw), I got directed towards the latest version.

    Seems like I'm not the only one experiencing issues?

    Edit: Hmm ok after some tests it doesn't seem to be as severe as I first feared. However I have gotten reports from testers that the version exported roughly 2 weeks ago runs siginificantly better than the one I exported today. I need to make some more tests to determine wether this is caused by some changes I've made to the game, or if it's changes made to construct/node webkit.

  • I don't even have an old node-webkit build (I keep to stable releases, last stable included NW in the build) so now I can't even update to the new stable because it'll break NW ._.

  • sqiddster Do you have the opportunity to install it on a seperate computer or something to test? If you read the edit I just made to my previous post you can see that I still get it to run fine on my own computers. I still haven't been able to find out wether the reported bad performance from testers are caused due to me making changes to the game that makes it incompatible with hardware below a certain spec, or if it's construct/webkit.

  • Well I know that Chrome 38 has some serious Vsync issues, and the new NW is based on Chrome 38 so I don't really want to risk it, unless I hear someone who has seen a definite improvement over previous NW builds.

  • Hmm I see. Alright I did some more intensive tests and it definately runs worse. Still need to figure out if it's my changes or the webkit though... :/

  • sqiddster

    The newest version fixed the screen-tearing, but there's still a little micro-stuttering left when medium-ish size sprites are moving.

  • Does anyone have the last version of the node? Was it ever released in the current form, ie a separate installer called "nodewebkit-for-c2.exe"? I guess I'm stuck on the last stable for now, unless r190 can have the older node installed over it...

  • TiAm

    I heard that either Construct2 or Node-Webkit breaks if you use an older version of Node-Webkit in the latest Construct2, but I can't test it as I have the latest both.

    If a Node-Webkit update rolls out I'll give word if the problem is fixed, as for the problem itself, it's apparently because Chrome v38 which the Node-Webkit is based on has vsync issues and some other problems.

  • TiAm, here's a link to the old node installer but, as said above, you're limited to no newer than r187.... C2 checks version numbers and prompts you to update if you try with the wrong one.

  • Construct 3

    Buy Construct 3

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

    Buy Now Construct 3 users don't see these ads
  • Colludium Nesteris

    I got the old exporter working in r190 without issue. Though...I did do the test on a secondary machine that isn't hooked up to the internet.

    Anyway, I don't know if there might be hidden glitches, but it appears to work fine. I've got a writeup on how to do it that's about 95% done; it'll be up in the general forum in a few minutes.

  • Did a reformating of my computer yesterday and got all drivers up to date, and it's first now I truly understand what you folks mean with v-sync issues. HOLY S***. Even the construct 2 editor is incredibly jaggy.

    Edit: The editor jagging might be solely due to the GPU driver. People are reporting V-sync issues here as well, even outside of games.

  • Tinimations

    Posted a guide here on how to restore the older, non-jerky node-webkit to r190 stable. It came out a little wordy...but basically, just replace the new node files with the ones from r184.

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