No, me neither. Is that using an extension, and if so, which one?
What did you do to "remove them" - just use the normal "repeat while key is down" condition instead?
Originally Posted by Sketchy Incidentally, I tried putting the event in a group, and disabling it (like in Pixelthief's method for making fastloops more efficient) - didn't help at all. MMF2 was obviously still evaluating all the conditions, even in the disabled group.
This is odd. Lazy evaluation is one thing, but this is entirely inexplicable- theres should be no reason an event is making an effect while it is closed- the game is never evaluating it. I'm going to do some testing with large collision objects and see what happens
Yes, it's very strange.
I tried making a test app to see if I could reproduce the results, but it all seems to work normally - except in my game.
I can send you my game file if you're really interested - maybe I've just missed something simple (it happens ). I have another bug you might be able to help me with too, while you're at it (duplicates not doing what I want them to again)
Hmm.. that's really odd. I'd guess that it constantly checks for collisions if you have any conditions doing collision detection, regardless of whether or not you're using collision detection.
You might want to mention this on the Clickteam boards, they could figure out the problem and patch it.
When I uncheck that box, I get things registering collisions many pixels outside their boundaries.
Might be because there's empty transparent space around the sprite? It's why I love that crop button.
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.
Advertisement
Post Reply
Edited by alastair john jack
). I have another bug you might be able to help me with too, while you're at it 
(duplicates not doing what I want them to again)
