Physics collisions affecting all instances

Link to .capx file (required!):

accounts.google.com/v3/signin/identifier

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.

youtube.com/watch

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)

This is just a picking issue in events 9,10,11,12 of the 'byte all' event sheet. 'System: Compare two values' doesn't do any picking so what you're saying is: if the x/y velocity of the first Little is >800/<-800 then set the x/y velocity of all Littles to 800/-800.

You should use the physics 'compare velocity' condition instead of 'compare two values'.

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

construct.net/en

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?

Picking in Construct2 is "Picking instances of an object type according to some conditions".

And system conditions like "compare two values" does no picking (it doesn't select specific instances, just apply the action to all the instances of the object type).

If you want to learn more about picking, check the how do I FAQ section "Picking/selecting instance(s)".

Anyway, not a C2 bug but a user mistake, moving this topic to closed bugs.