Cocoonjs V C2 HTML5 Export

After exporting the same project using-

1, HTML5 website (standard C2 export)

2,Cocoonjs (experimental)

I get the following FPS when i run the exported games in BROWSER window-

<img src="https://dl.dropbox.com/u/22173473/CocoonFPS.png" border="0" />

My question is..Why is the C2 HTML5 export lagging behind so much?

<img src="smileys/smiley5.gif" border="0" align="middle" />

Are you using Android?

I guess HTML5 export doesn't come hardware accelerattion on mobile devices.

No Android...Both examples running in Browser window.

you used emulator or something like that??how did you opened cocoonjs on browser?

anyway,i think the game will work 60fps on chrome...

also as we know cocoonjs is the best way to do games we will see the future of it soon ^^

How did you export CocoonJS? it doesn't come HTML file, i tought it's required to use CocoonJS Launcher and is for mobiles.

I ran them both on Opera emulator, Why is C2 HTML5 export 23 FPS slower, when its the same js file?

(It might run faster on a better system)

Well, Opera emulator is a mobile.

I tought you exported CocoonJS on desktop version.

Well, most browsers on mobiles aren't powerful enough because they use weak hardwares and no special API support on hardware acceleration, there special frameworks like appMobi, CocoonJS, etc. are solutions to allow special API and convert into native apps.

Well, Opera emulator is a mobile.

I tought you exported CocoonJS on desktop version.

Well, most browsers on mobiles aren't powerful enough because they use weak hardwares and no special API support on hardware acceleration, there special frameworks like appMobi, CocoonJS, etc. are solutions to allow special API and convert into native apps.

Yeh, I understand what your saying, but the opera is running on my desktop?

I just added an html file to get it running, the only thing stopping it running in browser is the event listener(i think)

I run the Cocoon export and it clocks 52 fps...close it..then run the C2 export(same constructjs file) and it clocks 29 fps.

hmm i don't know this way of running but try it in chrome and see if there is a different or no

Opera doesn't support WebGL/hardware acceleration so it's going to be slower. Well Opera 12 was released yesterday which has experimenatal hardware acceleration but you have to manually enable it.

http://my.opera.com/desktopteam/blog/2012/04/20/update-on-hardware-acceleration-in-opera-12

Opera doesn't support WebGL/hardware acceleration so it's going to be slower. Well Opera 12 was released yesterday which has experimenatal hardware acceleration but you have to manually enable it.

http://my.opera.com/desktopteam/blog/2012/04/20/update-on-hardware-acceleration-in-opera-12

---------------------------------------------------

"ECMAScript 5.1 for those who are too damn groovy for JavaScript.

Orientation Support

For Android only, support for camera use in the browser using the same, newer, getUserMedia syntax as Opera desktop Labs.

CSS3 radial gradients and the fabled -o-double-rainbow.

CORS (cross-origin resource sharing).

For Android only, hardware-accelerated WebGL for all things 3D and web. With WebGL on mobile,

it?ll be even easier to make games cross platform and distribute."

<img src="https://dl.dropbox.com/u/22173473/opera%20pics.png" border="0">

Oh I missed that you ran them both in the emulator. It's probably got to do with the mobile optimisation that's done on export.

scirra.com/construct2/releases/r92

"Performance improvement for some mobile browsers after exporting. It may be worth re-testing your games on mobile if you have already since the framerate may now be measurably higher in places, depending on the system. Note the optimisation is only applied on export - if you use Preview-on-LAN feature it won't be any faster. "

chrisbrobs - Opera is currently not at all hardware accelerated by default (so it doesn't use your graphics card to draw). This makes it so much slower that even on desktop the framerates can be lower than mobile. Also you should never take real performance measurements in an emulator - emulators can significantly reduce performance and give unrealistic results. You should only check on real browsers and devices when measuring performance.

Try Google Chrome - bet you get a solid 60 fps on desktop then.

CocoonJS always uses hardware acceleration. That's what makes it so fast!