Just a simple question:
Why "X is overlaping Y" is different than "Y is overlaping X".
Just a simple question:
Why "X is overlaping Y" is different than "Y is overlaping X".
I don't think it is. I think it's the same condition. But I have no proof of this, just a general hunch. Anyone else know for sure?
Yes, and no. For your uses, it is the exact same. MMF2 handles it slightly differently for collisions, but that only works when you get into the really complicated fastloop-collision systems where you need to make objects collide before their positions are updated and whatnot. It's rather complicated. I doubt you'll find a difference in them.
If I understand correctly.....
If "Apple" is overlapping "Orange"
Set X position of Apple to 100
This one affects only apples that overlaps an orange
If "Orange" is overlapping "Apple"
Set X position of Apple to 100
This one affects all of the apples when any orange overlaps an apple.
It kinda helps MMF2 select which object to do an action to.
I hope this is not off topic -
I have often wondered about the basic collision difference between
"another (active) object" and
"overlapping another object"
If the object is moving can there more than a pixel or two between collide and overlap?
Collision is a one time event kinda thing while overlapping is continuously happening as long as the event is true.
For example;
If Player collides "Red Active Object"
Then Add 5 to score
In this instance the first time the player collides with the "Red Active Object" 5 points will be added to the score. As long it is on the red active object, the event will not trigger again
If Player is overlapping "Red Active Object"
Then Add 5 to score
In this instance, the initial collision (which i would think be the same pixel as the collision trigger) would add 5 points, and every frame the player is on the "Red Active Object" 5 points will be added to the score
thanks ProdigyX
That makes sense.
love the learning.
As Jacob said, it can have different than expected results during fast loops due to the way the collision mask for objects is (not) updated in the middle of frames/loops, and it also matters which one is listed first in terms of object scoping, for writing the expressions themselves.
Posting Permissions
Reply With Quote