Fastloop logical problem

[Tiles]

From time to time i am even after years in heavy trouble to understand how MMF works. This is one of these cases

MMF Build 249. A simple thing. I have 10 brickmaker actives, and 9 brick actives. Now i want to check for the brickmaker active that is not overlapping a brick active. And create the missing brick at this place.

So first i spread value in the brickmaker actives. Then i enter the condition Alt Val A of brickmaker equal loop index, plus the condition brickmaker active is not overlapping brick active. This should isolate the one brickmaker that is not overlapping a brick. And as the action create Object at this brickmaker object ...

Doesn`t work. My missing active will not be created. The gap simply doesn`t get filled.

It works when none of the brickmakers overlaps a brick though. But that`s why i run the fastloop, to separate the one brickmaker.

Where am i wrong? Why does this not work as i expect? Could somebody be so kind and enlighten me?

[SEELE]

I can tell you right now its because of a negated event... downloading..

[SEELE]

Fixed; the problem was a negated event...

I used a flag to emulate the negated event, should work perfectly now.

[Tiles]

Thanks a bunch

This is interesting. Does this mean that MMF is in trouble with negated events in a fastloop? Curious

[SEELE]

I suppose i better explain.

Assume that there is a list of objects at the start of a condition which are to be affected by the action under that condition.

when you use 'is overlapping' in a condition then all objects which aren't overlapping will be removed from the list, this is how MMF selects the appropriate instance of an object.

The other condition is ' Alterable Value A( "brickmaker" ) = LoopIndex("makebricks") ' which remove all instances of the brick creator except one, each one only once.

These to condition in conjunction means in plain English:

check each brick maker, and if that brick maker is overlapping... do something.

However when you negate an event all that chances; because for a negated event to return positive, it must have returned COMPLETELY! negative if it were not negated, in this case the only COMPLETELY! negative would be if not a single brick maker were overlapping.

It may sound abstract, but once you get your head around it it's quite simple...

Hope that helps.

[Tiles]

Hm, that could explain why this little bejeweled engine here is so wonky with falling blocks. Also negated events involved. Something to get mad at ...

Beware, ways not finished. Better said, i abandon here. I cannot get it stable