"Events work by filtering specific instances that meet some conditions. The actions then run for those instances only."

scirra.com/manual/75/how-events-work

I see where it says that it doesn't do picking, in the description of compare. I honestly didn't understand what "picking" was supposed to mean. That's pretty vague. That sounds like a slightly off use of proper English. The word "picking" is never used without the object or objects receiving the action. If it ever is, it's in answer to something, and is referencing something that's extremely evident. like:

Mother: "John do you know what ice cream you want?"

John: "I'm picking!"

Never is something just "picking", it's too vague for proper use of the word.

"filtering" like used in the documentation would be better.

Sorry about the lecture, I'm a bit of a hobby linguist lol

[edit]

I see no "compare velocity", is this in another version?

Link to .capx file (required!):

docs.google.com/file/d/0Bwh3wi9gnmg4UC1kZkpoRU9wVW8/edit

Steps to reproduce:

1. Make a physics enabled small object that will bounce.

2. Make multiple instances of said object.

3. Make a player object that spins and has physics too, with player input.

4. Turn off gravity.

5. Crash into smaller instances.

Observed result:

Hitting one instance with player causes all other instances to register the same effect of being hit. e.g. hit 1 and all instances are hit as well. Doesn't happen every time.

A youtube video of result, happens at 30s and 38s. Watch me hit the red square and the green squares also are hit even though they aren't near the player object.

youtu.be/b6I2aWyub_w

Expected result:

That hitting an instance only effect the physics of the instance hit.

Browsers affected:

Chrome: yes

Firefox: yes

Internet Explorer: yes

Operating system & service pack:

Windows 7 Home Premium SP1 (64bit)

Construct 2 version:

Release 132 (64bit)

Sorry for posting again, I decided to take a video of it happening in case it's not happening to others.

You can see it clearly at 30s and 38s. I hit the red square and the physics effect happens to the green squares as well.

I can't post links yet but here's the video.

youtu.be/b6I2aWyub_w

This seems like a bug. Unfortunately it's game breaking for me which is a shame since I've been extremely happy with Construct and was considering buying it.

If anyone can give me any kind of pointer I'll be in your debt. I'm on a dead line and I have no idea how to approach this. Having a bug like this on release is no bueno.

[btw] I'm not going crazy am I? Are other people seeing this?

Okay I was able strip music and less important things to get the filesize down.

mega.co.nz

g1i1ch

I would suggest you upload a .capx file so we can see the code. Its hard to say whats happening otherwise.

Where's the best place to upload it, it's nearly a 20mb file?

I didn't want to report a bug until I was sure I'm doing something wrong. My layout is really simple, this is all of it:

1 arena made from individual bouncy walls.

1 player object, not too big, about 64x64.

3 small square objects, instances, that are just things the player will eat. 20x20

They all have physics. Gravity is turned off. They bounce around the arena and the player object. But I noticed something weird. Sometimes when the player hits one of the little squares it affects all of them.

Like say the player moves into one of the instances, then all the instances react whether they're touching the player or not.

The game will be very physics based so this is pretty bad. Is there something I've set up wrong?