I have been working on a game and found that it was randomly crashing on iOS with cocoonJS. After a bit of work and emailed to an from Ludei they told me what the problem was. My game was using all the memory.

My sprites were way too big. We have a lot of detail done on large backgrounds so the tiled background option wasn't really feasible. Also, when I started working on the game, directCanvas from appMobi was just launched and that didn't support tiled background at all. Which in turn caused me to use sprites for everything.

At one stage I tried to cut up some of the larger images to see if it would improve performance, but it didn't. Little did I know that it actually had.

So now I am at a situation where I am going to chop up my images and manually tile them. But I have some questions that hopefully someone with some more technical knowledge can tell me.

Does tiled background perform the same as a sprite if there is only one "tile"? Or is it stll faster?

Is there a plugin to easily tile images?

How small should should my tiles be? 256 x 256, 512 x 512, or could I get away with bigger? My background is approx 3072 x 1024.

I don't mean to be lazy and not search the forum - I have actually done some searching and reading, but I was hoping to get feedback from people who have come to the same situation.

Thanks

I haven't looked at your project.

But check the collision polygon on the elements. It's in the image editor for your sprites, under the "origin" button on the left.

Are you previewing in your browser? Maybe the cache needs to be cleared.

Otherwise check your "go to layout" events.

I'm using about 7, but I think I will increase it.

Using WebStorage

The WebStorage object uses a very simple storage model: values are stored under named keys, similar to how the Dictionary object works. For example, the value 100 could be stored for the key score with the action Set local value "score" to 100. Similarly the value John can be stored for the key name. Then the expression WebStorage.LocalValue("score") returns "100" (as a string) and WebStorage.LocalValue("name") returns "John", and these values persist between sessions. (If session storage was used instead, the values would only last as long as the browser session.)

Note WebStorage only stores strings. If you set a key to a number like 100, when you retrieve it back it will be a string. To convert it back, use the system expression int, e.g. int(WebStorage.LocalValue("score")).

scirra.com/manual/120/webstorage/page-1

Thanks guys. I must be blind.

231 events and counting.

Hey

Out of interest I want to know my total number of events, variables, and layouts. Is there an easy way to view this?

For what platform. Browsers usually prevent you from reading and writing to the file system.

You could use a variable to decide if the counter must decrease. And then set this variable on collision, but a apply a wait before the countdown applies.

Eg. ball hits yellow, set variable - wait 0.1 second, then decrease the timer.

I don't know if I explained very well?

+1. Will you post a reply if you found a result?

I added the local storage object and tested it out with cocoonJS. Works perfectly.

I'm a firm believer of paying for something that is worth the money.

Construct 2 is definitely worth the money, and if you have surpassed the free edition benefits, and you still need more, you should make a plan to pay for the game.

Scirra needs to make money somehow.