Set the collision polygon manually for one frame and then use the "apply to whole animation". It should keep the shame shape.

Welcome to the html5 gaming experience...

Somebody , I understand. Thank you very much for your answer and for your contribution so far!

About new ideas, how about an animated turbulent noise effect? With Height/Width scale parameters (in order to stretch the effect vertically/horizontally) and perhaps options for selecting the colors? This effect could very well be an input for other stacked effects, like Glass, Lens and Water Background. Finally, It will be awesome if one of the colors is transparent! That way we could create misty and cloudy effects!

! This is amazing Somebody ! The drop shadow effect was a request for so long now and you nailed it a day after Helena mentioned it! And it works on the Text Object too!!! :O

May I ask if it's possible to see the shadow on the layout? Because it's only visible at run-time.

And another thing, is it possible to have an invert Y option, you know, in order to cast shadows on the floor bellow the feet of a character like he/she is being lit from behind..?

Anyway, thank you so much for your effort, you are really spoiling me!

There are some very well paced videos on Scirra's Youtube channel. There is

that tackle the basics of a wave pattern system.

is older but is more in depth and maybe more instructive.

You can use multiple behaviors and build very complex systems but all that need some experimentation. Also try the Circle behavior, perhaps it can help you build even more complex stuff.

Already done that, look on the bottom of the first page!

Gunter , you are right. I had misinterpreted Justin1967's question. I thought that he was asking for the Circle sprite to be visible but not move. Setting the visibility options to invisible is the way to go.

Justin1967 , just use a different (invisible) Sprite for the rotation and keep the one with the Circle as a graphical backdrop. You should align the pivot point of the invisible Sprite with the Circle's center of course.

The simplest way would be not using math at all, instead pin the Blue Sprite on the Circle Sprite and rotate the later...

Here is an example capx.

Somebody , thanks for the link! The things that I should read to educate my self grows exponentially!

Welcome lurker! You are out on the open now!

Somebody , WOW ! Just WOW ! O.o

Thank you so much for sharing!

Ribis

Ashley

I am not saying that Ashley should adopt Somebody 's node based idea. I find it to be a cool feature, after seeing R0J0's example even more, but I understand that not everybody think like this and if Ashley says that this is something that will take several months of work just for this a debatable issue, then I trust his know-how about it.

My point entering this conversation was this feel about stuff that have been mentioned-proposed by forum members and either were shot down or not even had addressed for. I can't be an intelligent arguer about the Timeline feature for example, since I don't know anything about the IDE and how software (C2) is developed. So if Ashley argues about the Timeline being a time consuming feature to implement, I can't say it isn't, I'll just be greatly disappointed, because I believe that it's something that should be a default feature-set within a game creation software. Same goes with all the things I mention in my previous post. Again, I don't know if these are feasible or not, the only thing I can argue about is their usefulness (imo) as workflow tools and game development features.

Also, not having an official todo list is causing an uncertainty about the future of C2 and what can we expect from it. There are many-many things that have been mentioned before and now they lay shattered around the forum, it's too hard to keep track for. The global Boolean is one thing, an other is the ability to choose between the two Shift keys on the keyboard etc... Add all those little things together and we have a huge list of potentially useful features. But now there is the talk about C3 which only implies that C2 has reached its development limit, at least feature-wise, and there are so many things that haven't been addressed or answered yet.

I wish the best for the development of C3 and when the time comes I will support it, I just wish that it will cover the ground on those areas that have been mentioned before. I strongly believe that the todo list should be made into an official forum topic and then a poll can be made in order to evaluate the top features that must be included in the next Construct version. This list should have filtered out things that are not feasible by design however, that way we'll keep the expectations within the realm of reality.

Anyway, sorry for this long post.