MMF2's Collision is obviously BROKEN

with active-on-active collision

FILE TO SHOWCASE

long story short collision is screwed

how has this not been fixed yet

Lots of bugs original to MMF2's release have not been fixed yet.

Don't hold your breath.

I think its more of the way MMF works and its object selection routines.

To work around this issue you could use a turn on a flag of the object when it collides with the other object and only move the instances of the object where the flag is on. Let me know if you need the example file.

but I am sure how to work around the issue wasn't the point of the thread but thought I would just mention that.

Quote:

---

MMF2's Collision is obviously BROKEN

---

It's not at all an issue with the collisions, it's just the way the object selection works. Francois will probably explain why.

Personally, I dont call that a collision because it does not use the collide function AND as far as MMF2 cares, if one object is overlapping, they all stop. Try giving obejcts values and stuff...
Im no expert.

Replace the condition with "negated (object is overlapping backdrop)" and add a backdrop with obstacle selected.

negation is confusing because it seems to be too aggressive with its selection sometimes

basically it's acting like "if ANY object is not overlapping then move all of them" instead of "if THIS instance is not overlapping then move it"

the non-negated event behaves as the latter case which is more intuitive, so i don't know

I really hope for that to be fixed in MMF3 - I often had problems with that.

http://www.mediafire.com/download.php?jjuy52onxhm

Hopefully that will help...?

//edit//

Using your event with an obstacle backdrop in place of "active 2" does work. I assume that MMF2 prioritizes the behavior of an active object over the non-behavior of a backdrop... but I digress.

Quote:

---

Originally Posted by Pkeod

Replace the condition with "negated (object is overlapping backdrop)" and add a backdrop with obstacle selected.

---

that's why I posted "with active-on-active collision".

I know there are plenty of work-arounds but should there really be a need for that for something this basic?

This issue is a real pain and I don't see why it can't be solved