I **hate** that qualifier bug. It made me scrap some of my finest physics engines. It's even more annoying as it's a MMF bug. Happens on some comps, not on others, despite the coder. If you find a way around it, email me a copy of the source .
Disclaimer: Any sarcasm in my posts will not be mentioned as that would ruin the purpose. It is assumed that the reader is intelligent enough to tell the difference between what is sarcasm and what is not.
Yep it sure is annoying But you know, the best ways to avoid this is:
1. Re-ordering the conditions, try to think of in what order you would want things to be done. Re-ordering Actions might work aswell.
2. Make more conditions defining that it's only supposed to be 1 object that reacts. For example if you have a group colliding with another group, maybe you should include it so that:
If Group.0 overlaps with Group.1
If Group.1 overlaps with Group.0
This works sometimes, depending if you have alot of conditions in the event. Then you should put this second overlapping condition in the end of the list of conditions, or simply something else. Experiment!
3. If everything else fails, you will have to make more things that defines only 1 object. For example giving all objects who are overlapping ground value 1 to Alterable Value A, and those who aren't gets 0.
I bet people know more about this than me, but still, I have afew years experience.
Advertisement
Post Reply
.
But you know, the best ways to avoid this is: