Bug occurs, cripples unrelated events: MMF2bug?

[willy]

Take a look at this.

Place squares at mouse with mouse1. Keep placing squares till you see the error, you will need at least over 50 squares on the scene to see this. You will notice that actions suddenly stop working. The triggers won't position themselves correctly to it's ID companion, and even weirder; simple debug commands won't comply. And even weirder still; I made a test to see if completely unrelated events would cripple when the bug occurs, it does.

I've made it easy to debug.
Test if badguy and trigger have the same ID by isolating one badguy:
- Aim at badguys and hold mouse2 (move mouse slowly) to reposition badguys at mouse pos.

Test if triggers will follow their ID companion when moved:
- Aim at badguys and press t to reposition badguys at top of screen

Test if unrelated events are crippled when bug occurs:
- Move blue square with arrows over the red square. The red square should be destroyed, it won't.

Try setting max No. of objects allowed on scene to 20k. You will notice that you are now allowed to place more squares on the scene before the bug occurs. But the total No. of objects allowed is well under 20k

[Algul]

"nice"
after few tries i managed to make triggers follow badguys properly but other issues are above my skillz. It seem that changing overlap to collision fix some problems(couter will always pick right one under mouse and blue/red box will be destroyed), but draging with mouse will not work with too many badguys. => something with collision testing in MMF probably.
This is bad news indeed(at least for me).

[willy]

You managed to get the triggers to stay on the badguys when the bug occurs?

[Algul]

yep
http://rapidshare.com/files/154706641/New_Moment_system2.mfa

after first look i realized that it has something to do with collision. So i get rid of them.

[willy]

thanks man. But the weird bug still occurs. Try throwing in a bunch of these badguys, 200 or so, then try to move the blue square into the red square. It still won't perform the "destroy" action- it is still crippling totally unrelated events.

[Algul]

i dont think its unrelated.
as i said problem is most likely collision detection. If u change "overlap" condition to "collision" condition then it will destroy that red box properly. But i have no idea why these bug occurs.

[willy]

I don't mean to sound like a rectum, but I don't understand why you say it's unrelated.

The thing is, I don't care about the collision between the squares. I placed them in the scene to prove that when my main code went bananas, it affected unrelated events- such as the overlapper event.

Now I am uneasy to continue developing this before I know what is causing it. If it's a bug in MMF2, fine, but maybe someone can elaborate what causes it so I might take some precautions.

[Pixelthief]

It could easily be an error with putting too many objects into the scope of the "Set detector thingy position to enemy position" event. You are placing all your objects position via a single event that does not specify a single index. Perhaps this would work better if you used a fast loop to iterate through each object, find the matching pair of indexes, and position them. IE, #4 from this article:
http://www.create-games.com/article.asp?id=1937

in general its a lot better coding, and makes your other events easier to implement.

[willy]

thanks man, that sounds plausible!

[Algul]

I tried that with fast loops. No change.