I can't figure out why, it seams that in same event C2 can't apply action to all instaces via pick all. But here is second soulution for your problem, this time with checking for collision http://db.tt/YhpwdOYM

edit: maybe Ashley can answer your question

try this

use overlaping at offset and it will work. I have set it to X:4 and X:-4 so that it works at high speed, but you can set it to2 or 1...

capx

glad to be of help

yes you can drag one event under antoher and slightly move it to the right so it becomes sub-event of that above it...don't move contitions in events move entire event - couple of pixels on left edge of event that you wont to move

if you wanna to count instances of "one sprite object" then it's possible, but if you wanna to count all sprite objects/not instances an their instances then it cant be done in one shoot. Family count dont work in CC. I sugest method in my first post if family count don't work in C2, or you get number of each sprite instance and add that to instance count of all other sprite objects

I don't have C2 licence so I can't tell you that it's posible to put your sprites in family and then set Text to "Family.Number.of.Object" like in CC - in CC that option you can call but it's not working like meany things in CC.

If that's not possible in C2 you can set text to 'objectcount'(from system) (all object that ara on layout and exclude those that are not sprite and counts as those that are on layot even if not visible. Some of these are:

text, particle, tilebackground,canvas, array, ok button, dictionary, fuction...

find out the rest that you use in your project and for total number of object substracte each of them

'objectcount'- number of object that are on layout (visible or not)and not sprites = number of sprites

that's all I can think of

try this

Thanks R0J0hound for pointing out difference.

But difference beatween what is overlaping at offset in CC and C2 is exactly that what leads to some problems in case you would like to make built-in platform behavior work "perfect" with smal sprites: to prevent sinking, penetrating sprites in obstacles for 1-3px.

Why is that so:

As I understand it, collision happens when sprite is on obstacle and it functions like triger. On the other hand 'overlaping at offset' in C2 funcions exactly the same as collision(=overlaping 1px), but not as triger, more like while: 'overlaping at offset 1' is basically equal to while it's coliding - if sprite rectancle is the same size of the collsion box.

If solution to this is that you make collision rectangle smaller one px from sprite size, and then if sprite with platform behavior due to not working accuratly with small sprites sinks in ground, and you then set its position so that is visibly on obstacele (set SpriteY to Obstacle.Y-obstacle.Height/2-sprite.Height/2) it is not colliding whit it so you can't jump.

If you make it collide so it can jump you can't use overlapinng left or right(overlaping at offset 1,0 or -1,0) becouse it is overlaping like colliding, standing on the line of obstacle...

Yet again I think that what counts for overlaping in CC is better, because in C2 it's overlaping at offset of 1 is basicly same as collision detection.

Thanks for your help, but I made this example in order to understand

overlaping at offset. I moved some sprites one pixel to show that it works only if sprite is not on obstacle but moved one pixel from it. In Construct Classic this works as I think it should, but in C2 something is wrong. I know that you can make it work but that is not the point, because: "For example, testing for an overlap at an offset of (100, 0) will temporarily move the object to the right 100 pixels, test for the overlap, then move it back again." (Manual)

I would like to know how overlaping at offset works.

Thanks again.

I have following situation:

<img src="http://dl.dropbox.com/u/37009800/Construct%202/Need%20Help/overoff.png" border="0">

Sprite on right side shouldn't overlap left or right because he's not inside obstacele, he's on it. Am I doing something wrong here?

capx

It's not pixel rounding issue, it's the way C2 platform behavior works. Many people have noticed this before.

Read this, this, and this.

Your only solution is custom platform engine with loops, becouse C2 is against the old school <img src="smileys/smiley2.gif" border="0" align="middle">, but thats not so hard to pulloff and most of all with custom platform engine you can have variable jumps <img src="smileys/smiley36.gif" border="0" align="middle">

in this you never hit ceiling (pixel rounding On)

Thanks man, I see it all much clearer now.