Some of you may know of this bug while working on MMF or TGF. Myself I always have a problem with this issue and need to keep finding workarounds for it. Here's how it goes:
Group.4 overlaps with Group.0
Group.0 is facing direction 24 [down]
Group.4 Internal Flag #5 = OFF
{
Make Group.4 invisible
}
This is rougly how my problem looks like. Group.4 are objects walking around the level, while Group.0 is the ground object. You don't really need to know this but the flag 5 is for knowing if the object currently has it's gravity reversed or not. Anyway, when this event occurs, ALL the group.4 objects get invisible. How do I make it so that only the object colliding with Group.0 gets invisible? Seriously I hate this problem and I would earn so much time if I found a way to smack this problem in the wall and move on with my project!
I think he was asking for an answer, not for someone to brag that it works for them, so they can't help. That would be no different then asking for help, and everyone in the room yells out that they can't help you. It's rude unless they ask you personally.
Omg, and your post wasnt pointless then? Attacking someone else instead of helping him, yay thats what he wanted.
I just wanted to point out that in my version of TGF it works perfectly fine, so it could be something with his version. Please dont make me more annoyed than i already are at you. -_-
Lol please not this forum too, I get enough of that on my own.
But anyway, did you try with several group.0 and group.4 objects? Strangely I solved the issue by adding another "Group.0 is overlapping Group.4" at the bottom, and re-ordering the conditions abit. That's a good tip btw, re-order them if it doesn't work!
Now I just need to get hold of a decent platformer engine.. anyone who can help out?
I spoke my mind out agenized his post, far be it from me to get disrespect for doing so. I don't care, but that’s not going to stop me from doing it. If you wanted to point out that it must be a problem in his version, then say so. Don't brag about how you don't have the problem, because in personal experience. That is the most annoying thing anyone can do to me when I ask a question. That's all I was saying, sorry if I came off a little strong, but seriously. Think about it.
PS: And before you take someone else’s side for making a counter post just as pointless as the one I made to point out their pointless post… take into consideration why I made my post. Peblo.
Sorry Brandon I think you're the one who's not really helping out here..
Does anyone know where I can get a shooter-sprite? That can point a gun in any direction? See I just made a really good engine with monsters, now I just have to create the shooting dude.. And I need a platform engine and sprites.
Well personally, if I wasn't helping, then I can automatically assume that SkyDragon was no help either.
As far as shooter sprites, you could try making a post under: Solitaire Club; I'd be more specific about what you want though. Just asking for a shooter sprite, might not get you to much. Also, give them a way to contact you other then just the post. Once you start talking on MSN or AIM, the chances of getting the sprites raise a good 90%, trust me.
The Solitaire Club isn't active because there are to many posts that aren't specific. People still read posts, they just won’t reply to them if they are shit posts. Or they will reply, but they won’t take you seriously.
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
Brandon i love you!
But you know, the best ways to avoid this is: