Yep. All my layouts have their own event sheet and then just include the events sheets that use common events.

requestAnimationFrame must be a C2 event? I just copied the error thrown in the cocoon console.

The only plugins I use are "Function", and "Date" - so I doubt it is something in one of them.

I think the touch stuff just stopped working because of the error thrown, probably crashed the function or layout.

Here is the error on CocoonJS when using spritefont:

JSUtilities Exception: TypeError: Result of expression 'a.canvas' [undefined] is not an object. Cause: Tag: requestAnimationFrame Function: function() {a.hd();}

I found that if I have it on a layout, it breaks the touch events too. I don't know if that helps? :)

Have you tried emailing Ludei? They are fantastic with email support.

It doesn't seem to work on my cocoonJS :/

I tested on iOS and Android. Awesome plugin though!

Hey all

I have been working on my optimisations today and implemented a lot of the methods mentioned.

One thing I tried and now just found to be very BAD was over using tiled backgrounds. I thought that I could use a nice small tile and grow it over a large area. Big mistake! It killed the performance. I think I am getting a good idea of how html5 handles images and memory.

Thanks for all the helpful feedback guys. I re-use a lot of assets with scale and rotation, but there are some things that I can't seem to really reduce.

I'll chat to the designer and see if she has some ideas.

Just a side note. My window size is 960x720, but the layout is the big one.

Thanks Ash :)

Thanks guys.

Ok, so what ever is drawn on the screen is what is in memory. If I have an image that is larger than the screen resolution the entire image is put into memory even though only a portion of it is drawn. Is this correct?

Hi Ash

Does Contruct always load all assets in the game on the initial game load?

I got this feedback from Ludei and wanted to check from your side about this. Is there a setting I don't know about?

* Try to load the resources once you need them (when loading a level for example) instead of loading all of them at the beginning. Unload them once you do not need them anymore (once the level is done).

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

Thanks for the feedback Ash, if I cut a 2048 x 2048 image into 16 of 512 x 512 slices, would it then be better?

Is there another way to create a large type of layout? Or would it be best to try and flatten whatever I can into single images instead of layering?