Hello, if you didn't know about it, my first guess is Delta time :

https://www.scirra.com/tutorials/67/del ... dependence

Does that help ?

Here's some game play footage of my game Robot 505. Still very much a work in progress.

http://youtu.be/jA2Ohjk1afo

That's looking real good ! Solid art style, and we can already feel the power of that robot :p

Hello, i may be wrong, but i think i have seen somewhere a post about optimisation, and image size dont really matter (it's only affecting the download size, not slowing the engine or so.), if thats true, then it wont matter since you want to pack different size of the same image in your game it's going to be the same. (Lets wait for more responses here ). I would say if you really want to optimize you should make a different app, with lower size images (and not an universal app) .

Hello Evasleipa, yeah its a known problem. It's not a problem with Construct2. It's a HTML5 general issue right now, depending of Chrome and Node Webkit (from what ive seen). We are all waiting for some fix about it. (I have the exact same problem like many others)

Here is a Capx i have done for you to test.

By pressing " i " you can switch the visibility of the two buttons (it's the same logic if you ask if it's a sprite visibility or Layout / layer). The red button is clickable even when hidden (that's not what we want) but the blue one is only clickable when visible. And this, because i said : If button blue isn't visible then deactivate the group (where all the actions for the blue button are), this way you can easily make many actions, for various buttons inside a single group and deactivate the whole thing by only doing one check (the visibility).

That's the right way to go. It may seem strange that buttons are clickable when the layer is invisible, but that's normal (invisible doesn't mean inexistant).

You need to tell the engine you don't want it clickable when hidden.

For that you can make a group and then a main event inside looking : Is my menu layout visible or not ? Then all the actions / events.

Softloulou as far as I understood it, if you plain to make an html5+js browser game (your last post makes me think that), even without C2 this chromium issue will be on your way (unless you rely on somekind of plugin to make your game work, but that is another constraint for the end user, and even then other issues will be presents I would think)

Yes Aphrodite, i was targeting smartphones and browsers for this project (a fast passed scrolling game like "jetpack joyride"https://play.google.com/store/apps/details?id=com.halfbrick.jetpackjoyride). This jittering issue with Chrome/Node Webkit is a real pain. For now i will just continue my prototype and see how it goes the day i export it (i will leave the browser / desktop aspect aside (i will test the game with firefox ^^), and see what i can do for mobiles).

>

> > 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.

What i would like in C2 :

-> Timeline

-> Animation / tween system (for simple animation purpose like moving menus / cutscenes, should work with the timeline too)

-> Vector sprites / animations (Like Flash, same should work with the Timeline)

-> Advanced particle system (with animated sprites included for example)

-> A function library ? (for used / created functions so we can find use / copy past them faster ? Duno that's some crazy idea but i guess this can be used)

-> Find a secure export way, so games wont break (jagginess) with some Node / Chrome updates (but well, it seems impossible to do)

-> Advanced implemented painter.

-> Possibility to choose exporter version ? Like multiple Node Webkit versions ? (to help counter the Bad Node Webkit updates for example)

Thats some ideas. Keep up the good work.

Like many said :

-> Timeline

-> Animation system

-> Advanced particle system

-> Vectors sprites / animations (kind of like Flash / illustrator)

A way to ignore Node Webkit (Jittering problems killing games)

But most of all, keep C2 a priority for now please

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

Thanks for the responses guys, i will do some tries with node 10.5 (and then on my main project). I let you know what happens. (Hope Chrome fix that soon)