No, it is not, and it is apparent why - if you make some units and wait for them to file to the end, then make one, and before it gets to the end make another, they will both keep moving until neither is overlapping. This is because MMF2 does not properly deal with object selection with negated events.
Back to the main issue
...
Im just thinking here
An overlapp condition performs Instance Selection right?
But maybe the issue here is that the Selection only works within the Actions of the Event, not the Conditions?
...
So when
'If ObjectA is overlapping ObjectB'
an instance selection is performed ( Only Objects wich meets the criteria are selected )
But in the same event when
'If ObjectA AlterableValue_ is different than ObjectB AlterableValue_'
MMF2 treats it like
'If ObjectA( Object ) AlterableValue_ is different than ObjectB( Object ) AlterableValue_'
Object selection work on conditions that you retrieve from the object you want to be selected. As you go down the condition list the object selection will either stay the same or get narrower. If you use compare two general values, you are not changing the object selection, because this condition comes from the Special Object and not either of the objects you would want to select. Objects cannot be selected from expressions, and can only be selected from actions through the Create Object action.
What did you mean by this? Why does it not deal properly with negated events?Quote:
Originally Posted by LB
I don't know why, I didn't write MMF2 or see its source code ;p
Basically, if you have a condition (Negate) Object A is overlapping Object B, you would expect it to select all object A and all Object B that are not overlapping the other. Unfortunately, if any Object A are overlapping any Object B, then the event just gets completely skipped because there are at least some objects overlapping.
This is more a design flaw of MMF2 than anything else and I doubt it would be easy to fix.
is there some extension or something i could at least use for doing collisions instead of using mmf2's overlapping?
No, and if there were it would cause lag. Collisions in MM2 aren't sleeping beauty perfect, but they are fast and work well enough to get the gold. With extensions there would have to be several unnecessary steps of exchanging information and it would have to be done for all objects, which is much slower.
EDIT: I believe that Looki's Surface Object handles its own collisions, but that's impractical for this scenario and you would still have the same negated event problems. This is less related to the collision system and more related to the event system and object selection.
i am using foreach now and my only problem now is that if two objects are overlapping where it doesn't apply and another object begins to trigger the event, it won't apply unless they are overlapping the last created object and then it applies it to every single object on screen.
Yes, because, as I told you, it won't work.
so what on earth am i supposed to do?