Mobile / cocoonjs optimisation tricks ?

Alatok Softloulou

as much as I love Construct 2, I strongly disagree with Scirra's approach to exporters. The best example is Android: CocoonJS was deprecated and what alternative do we have? Jittering Crosswalk. It's just soo not professional, ehh. And it's always about waiting for better future.

szymek

Hmm.. Ashley says "I truly believe that native exporters would mean we end up doing nothing other than maintaining a bunch of parallel codebases with no time to do anything else" hmm... What about if Scirra hire more people to his team?

If the reason is the lack of funding, it should not be impossible to get it from many different sides.

Alatok

it seems that Unity etc. and all other engines with native exporters are 100% wrong

Ashley says also "Like I said, most projects which run in to trouble are either exceeding hardware limitations, or grossly inefficiently designed." which sounds really funny if you think about strong jittering / micro-stuttering issues. And the latest CAPX by Softloulou is the best example.

szymek

Indeed, sounds really weird...

Anyways, I made my decision. I'll try to make a small prototype with free C2 license like — suggested. And will look at how the C2 develops in the coming months... But at the moment it is not yet ready for commercial game making.

Alatok

That's good idea. In my case I hope for native AdMob from ludei and meantime I will work on some simple app that could run well even on jittering Crosswalk.

Verily Construct 2 teaches us patience

Like you guys said, it seems construct2 is only for prototype usage right now (wich is sad, and even for that it's limited now), we have to wait for some fixes (sadly from Google/chrome side). I knew Construct2 is a HTML based engine and i was fine with it (and actually it's a really strong one) i was reading everything i could find about optimisation, tricks to make the best of it, but right now (with the lastest issues) it's just plain impossible to make something pro with Construct2 (it happens even with the smallest prototypes now).

Like you may know, from browsers usage stats : http://www.w3schools.com/browsers/browsers_stats.asp

Has you can see, Chrome represent 60% of web browser usage ... So what does that mean ? We just have to wait and hope that Chrome fix that soon. Or move to another engine, and that pains me (yes i really enjoyed Construct2) ...

If anyone comes up with a fix for that let us know <img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile">.

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)

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

Softloulou Aphrodite

Gianmichele wrote about auto updating webview in Android 5.0:

Honestly I'm a really scared that an auto updating webview, more than nodewebkit, could break a perfectly working game without any action from the user (or even knowing it really).

Ashley replied:

Google already manage to do this without breaking the entire Internet, so I'm sure apps will be fine too.

***

so everything is fine...

Softloulou Aphrodite

Gianmichele wrote about auto updating webview in Android 5.0:

Honestly I'm a really scared that an auto updating webview, more than nodewebkit, could break a perfectly working game without any action from the user (or even knowing it really).

Ashley replied:

Google already manage to do this without breaking the entire Internet, so I'm sure apps will be fine too.

***

so everything is fine...

not related to webapps/webgames but more to webview-based exporters (exporters which are not something I can really think is great, since they are prône to monopolising and they sometimes just interprets standards the way they want and they break the multiplatform support, as cordova based projects will run on android and iOS only, so you have to export one more time for other platforms, while a web game just runs on all platforms that possess a browser supporting the standards, the only reason to justify their use is either to sell them, or to use lower level interactions with the system).But again, if you choose an exporter suceptible to break when the webview update, you should already know that beforehand.