About the jerkiness on the movement...

Discussion and feedback on Construct 2

Post » Wed Nov 19, 2014 12:08 pm

Going backwards isn't in general a solution. I need to know more details about this again. I know it's like this thread all over again but it's simply essential to know things like: is it the same as what happens in Chrome? (That's the difference between filing a bug with Google or with the node-webkit devs) - does it happen with all games? - does it happen on all hardware? - etc etc...
Scirra Founder
B
395
S
232
G
88
Posts: 24,371
Reputation: 193,772

Post » Wed Nov 19, 2014 12:11 pm

@80bit

i have the steam version too, sadly, i updated and my most updated version of my game is saved on r188

dont update, but if ashley updates to stable, you are done for too. but for now, stay in the last stable.
B
23
S
6
G
3
Posts: 316
Reputation: 3,461

Post » Wed Nov 19, 2014 12:37 pm

@Ashley

well i tried it on chrome and nw, and in both happens the fps stays in 60 but i looks jerky.
i tried firefox, but firefox does not give me 60 fps, so i cant test it there, becuase it runs horrible.
phenom x4 965t black edition
8gb of ram
radeon hd 6950 xfx 2gb

i dont know whats causing it, but the previous version of NW was running fine for me.
B
23
S
6
G
3
Posts: 316
Reputation: 3,461

Post » Wed Nov 19, 2014 2:05 pm

If Chrome is the same then node-webkit is working properly and it's a Chrome issue... I would guess it's the same as this: https://code.google.com/p/chromium/issues/detail?id=422000

They already patched it and I saw it working great in Canary, but then they reverted the patch for some reason, but hopefully it means a fix is on the way.

AFAIK it's limited to Windows - does the jank still happen on Mac or Linux?
Scirra Founder
B
395
S
232
G
88
Posts: 24,371
Reputation: 193,772

Post » Wed Nov 19, 2014 2:25 pm

Ashley wrote:but hopefully it means a fix is on the way.


YES PLEASE, YES PLEASE, YESSS PLEEEEEEESSSSSSSSS :shock:
B
65
S
22
G
4
Posts: 358
Reputation: 6,555

Post » Wed Nov 19, 2014 7:21 pm

@Ashley

thanks the heavens :D, and yes, thats exactly the symptoms that i expirience, the exact same thing.
im so relief to read this n.n so it was pretty much the Vsync

will be waiting for the fix, thanks a lot :)

i tested it on windows 8
B
23
S
6
G
3
Posts: 316
Reputation: 3,461

Post » Thu Nov 20, 2014 4:10 am

I have try the new node-webkit v0.11.1 , still not fix the problem
B
37
S
11
G
1
Posts: 80
Reputation: 3,325

Post » Thu Nov 20, 2014 4:35 pm

winsonzhong wrote:I have try the new node-webkit v0.11.1 , still not fix the problem


Apparently it's a Chrome issue, not directly caused by node-webkit
B
65
S
22
G
4
Posts: 358
Reputation: 6,555

Post » Thu Nov 20, 2014 5:16 pm

Chrome 39 seems a lot better here. Check you're up to date in 'About Google Chrome' and then try again - are games working better?

If node-webkit can update to at least v39, that could fix it there too.
Scirra Founder
B
395
S
232
G
88
Posts: 24,371
Reputation: 193,772

Post » Thu Nov 20, 2014 7:26 pm

@Ashley

tried it on chrome v39 and it seems a little better, but is still there, almost full force, but i dont know since i dont use chrome, so im not used to the chrome performance, i will need to see on NW
B
23
S
6
G
3
Posts: 316
Reputation: 3,461

PreviousNext

Return to Construct 2 General

Who is online

Users browsing this forum: No registered users and 33 guests