Does anyone have this? I would like to learn how the rain was done.

Thanks.

So, how do I do these 2 actions?

Thanks.

Does setting the display angle to something else other than the default (0 degrees?) do anything? I've tried using it and I don't see any effect at all. Is it supposed to rotate the screen?

Thanks.

Is there any way in Construct to loop through all private variables of a particular sprite?

Must I name these private variables in a special way? What actions do I use?

Thanks.

So Deactivating makes the sprite ignore actions related to the 8-direction behaviour?

For example, I have a container with 2 sprites. Each sprite belongs to a different layer on the layout.

If I place (using the GUI, not with events) 1 of the sprites on the layout, is the other sprite supposed to be created automatically? If yes, which layer will it be on?

Is it a bad idea to have containers with objects which are on different layers?

From what I've seen, 1 sprite may be "dragged" into the other sprite's layer. The behaviour seems quite erratic (isn't fixed or well-defined). Is there a smart way to go about doing this? I want to make sure that the objects are always fixed on their own layers (where they are supposed to be), but yet I want the container to be maintained.

What are the differences between the following actions:

Set Activated

Set Ignoring Input

for the 8-direction movement behaviour? They seem to do exactly the same thing to me.

Thanks.

Are all .fx files applicable for both Effects and Transitions?

Is there a tutorial or some documentation where I can learn about .fx files?

Thanks.

What are .fx files? How do you create them and import them into Construct?

Has anyone made more types of layout transitions that I can download as add-ons to Construct?

I'm looking for more transitions other than the 6 main types provided with Construct.

Specifically, I'm looking for a "glass shattering/breaking" layout transition. Does such a thing exist?

Thanks.

Do these 2 actions exist? If not, is it possible to implement them in a non-hardcoded way?

Note that I'm referring to "Control", not "Key".

Thanks.

How do subanimations work exactly? The way I'm thinking about them now, I find it strange that you still need at least 1 animation/angle for the "main category" (not allowed to remove).

For example, I want to have an animation called Walking, and 4 sub-animations called Up, Down, Left, Right. Walking is completely described by these 4 sub animations, so I shouldn't have any animation in the main category Walking, but I'm forced to have one.

Also, the events/actions don't care whether an animation is a sub-animation or not, you just need to specify the animation name. So what exactly is the point of sub-animations, and when should I use them?

Thanks.