Putting the opacity change stuff into a System->OnLoadingFinished makes it work.

Not quite sure why - but it feels like it's picking all the families first before the red ones have been created. Perhaps when you create a sprite it puts it in a list and creates at the end of the frame.

Ashley may be able to shed some light on it.

I don't believe the accelerometer works on cocoon yet. That isn't anything to do with C2 - it's a cocoon JS problem.

If you find it overwhelming (and it can be) then you might want to consider making something more simple before doing an adventure game of that type. eg. a hidden object game would be a step along the way to that without having to deal with all the complexity at once.

I don't know if there's a tutorial. But as with anything else in C2 or any other programing (or indeed in life), it's a matter of breaking the problem down into smaller chunks.

Each of the locations in that game could be represented as a different layout. And each hotspot within the location could be represented as a sprite.

As sprites they can be clicked on and animate and spawn other sprites or text boxes. And from there, you could load up other layouts, ie move to another location.

I think you could get a simple and ugly version of that up and working fairly quickly.

This is great. Nice and fast, feels responsive.

It's nice to be able to make this sort of game which is no longer feasible commercially for consoles - and yet is still loads of fun to play.

Beautiful!

I really like the look of the planes and how they handle.

It's annoying though that it stops you playing when you run out of time. I had taken no hits at all - I think I should have been allowed to play on!

Ah, the post has made a mess of my careful ASCII art. This is what I mean:

<img src="http://www.st-andrews.ac.uk/~jcgl/Scots_Guide/audio/clipping/fig1.gif" border="0" />

Apparently it's called clipping, not clamping.

Since the last time I requested a feature it had already been implemented, I thought I'd go for another.

I find the Sine behaviour really useful (though badly named). What would make it extremely useful is to be able to clamp the values - this would allow much greater control over the curves.

eg. If currently I have a triangle wave with a magnitude of 10 then I would get a wave like this

/\    // \ / \ /

    \/    \/

Now if I was able to clamp the same wave to 5, then I would get a wave like this:

__      __

/ \    /     \__/    \__/

Which would be very useful.

Also on the sine behaviour, it would be great to be able to set the offset in an action.

Awesome, thanks. I obviously missed that!

It would be really useful to preview how layers parallax in editor. Currently it's very trial and error to get something in the right place in a layer that parallaxes.

I'm not quite sure how this would work. But I guess what I'm asking for is that when I place something on a layer relative to other layers in the editor - that's where it will be in game.

On my current project, I have each level in a different layout, and since the start of it I wanted to create a single HUD that would work with each.

First I created the HUD dynamically when I load the level, but this is a pain to create and maintain if the HUD is complex.

Then I created a HUD on the first level and made it global. This works - except if you jump into a different level - if you are testing or if you are continuing a saved game.

And today I found the solution... which basically involves checking to see if the HUD is loaded - and if it isn't switching the layout to the HUD layout and then switching straight back - with the HUD kept because it is global.

I am very happy with this!