Printable View
http://www.mediafire.com/?kt20yhtn48pn6m1
Hello! I have gotten myself into a huge problem with what I thought should be a very easy problem.
I have created a specific movement for an enemy where the enemy will change direction when it gets near the edge of a platform. It works fine when there is only one enemy but when I add one more enemy the older one stops detecting the edges. What can I do, it seems like such an easy problem but yet it doesn't work? :(
I'm pretty sure it is because of MMF2's object selection. I don't even have to look at the example to tell you that. There are multiple ways you can solve the issue, with the easiest (and fastest, frames per second-wise) being to use the ForEach object. If you don't have the full version of MMF2, however, you can't use any objects that don't come with it. However, there is still a way to do it, though it is a little complicated. If you don't have any experience using FastLoops, though, then you will need to learn how they work first. There is a tutorial on them here, if you don't already know how to use them.
I do not want to rely on ForEach or any other extensions, I just want to keep it as simple as possible for personal reasons. I do have experience with fastloops but I had wished I wouldn't need to use fastloops for this.Quote:
Originally Posted by happygreenfrog
Well, MMF2's object selection is terrible, so there isn't any other way to my knowledge. Fastloops are slower (and potentially less reliable) than ForEach loops. The ForEach object works with most runtimes, so there aren't really any problems with using it. If the personal reasons make using it impossible, then you will have to settle for the Fastloops, and live with the worse framerate that it will give you.
I fixed the file you gave me using Fastloops, BTW. I probably could have lowered it to use one Fastloop, but I didn't. It should work okay, though. Enjoy!
Thank you very much! Works perfect! :)Quote:
Originally Posted by happygreenfrog
just curious, how would the foreach version of this look like?
Why are you wondering? Do you not know how the ForEach object works? Or are you new to using it? If it is just that you are new to using it, then I can make you a simple example. If it isn't, then I will get to work on it.
I'm just new in using it and would be nice to see what mistakes i'm making ;)
Well, then, could you tell me what you are trying to do, then? Or make a simple example of what you are trying to do? Or is it that you are trying to convert the example I just shared to use the ForEach object?
yes, i just have tried to convert it, the best thing to learn is look at some good example ;)
i've tried it and in my version they always got the same flag (on/off) for every object...
For instance:
+ ObjectA Angle > 180
-> Change Animation Sequence to YEY!
...
+ Allways
-> Start ForEach loop < loop name > for ObjectA
+ On loop < loop name >
+ ObjectA Angle > 180
-> Change Animation Sequence to YEY!
...
As you see its quite easy to include any Event intoo a ForEach loop, which handles each instance correctly regardless of what method youre using.
You shoud definitlively trust and depend on the ForEach extencion whenever you need to, it is supported by most if not all of the exporters and works wonders patching up MMF2s broken Object Selection.
The Advanced Direction Object, Layer Object and Window Controll Object are also very good and widely supported friends.
yes, i understand these basics. maybe i'm doing something wrong in this example. i start like this:
new obj created: spread value 1 to id
always start foreachloop
then:
on foreachloop
+id obj = loopinteration
+obj = overlapping detector left
+obj = overlapping detector right
+X detector right is overlapping a backdrop
+detector left is overlapping a backdrop
--> set flag on
The ForEach object comes with an example or two. Have you looked at them yet?
You dont need to mess around with SpreadValues or IDs when using the ForEach Object, thats kinda the point of the ForEach Object, it does this automatically for you.Quote:
Originally Posted by StingRay
Im not sure what youre trying to do here ^ but if there is only 1 Left Detector and 1 Right Detector:
+ 'Detector Right' is overlapping a backdrop
+ 'Detector Left' is overlapping a backdrop
-> Start ForEach loop "loopA" for object Active
+ On ForEach loop "loopA"
+ Active is overlapping 'Detector Right'
+ Active is overlapping 'Detector Left'
-> Active set Flag0 ON
Behaviors don't handle object selection any better than the rest of MMF2, to my knowledge. They basically do the exact same thing as just pasting those events to the bottom of the event editor, if I remember correctly, though they are also a little buggy. So ForEach loops are the way to go for good object selection.
I've used MMF for years and have never heard of the ForEach object until right now. I've always used Fastloops (?)Quote:
Originally Posted by happygreenfrog
ForEach is essential, and should NOT be considered an Optional Extencion or Special Feature.
It does what fastLoops do FASTER and with FAR LESS WORK.
It COMPLETLY PATCHES UP the most essential problem/ design flaw/ bug ( call it what you will ) with MMF2 ( being correct INSTANCE SELECTION ).
Youll have to be very convincing to make me believe that the FastLoop workaround was INTENDED for MMF2.
FasLoops are realy great! They can infact do EXACTLY what the ForEach does, only FastLoops require more work AND it works SLOWER.
But thats not all, FastLooping through Objects require you to RESERVE 1 of the 32 AlterableValueas as an ID_ value!
GooooooOOOO, FASTLOOPS!!!
( ... )
Are there any Exporter which DONT support the ForEach Object?
Not very many. According to ExtensionView, it is supported by:Quote:
Originally Posted by King_Cool
Windows
Java
Flash
Anaconda
Not to mention the fact that the information in ExtensionView for the ForEach object is outdated, because I know for a fact that it is supported by the Android runtime.
It sounds awesome and much less work for us, however my current project has literally hundreds of events and up to 20 fastloops that go through a triple-dimensional array each time the player moves the character around a space. It would be such a huge pain in the ass to go back and change everything over now, but for any next projects I will absolutely have to look more into this.Quote:
Originally Posted by King_Cool
So how does ForEach really work? Is it kind of like the old For.. Next loops?
My main thing / problem / whathaveyou is getting the event sequence order right. Spread Value 0 in alt Z -> Always loop (Blah) for # of object times -> If loopindex (Blah) = Val alt Z then <do stuff>.
I had been very used to using object-oriented programming with VB6 in the past and with it you could have object arrays which made using loops and picking the correct instance of an object LOADS easier than the fastloops method so any way I can use MMF2 with more ease is better with me, Russ.
No iOS support? :O
It popps up under the available Objects for MMF2 iOS builds, when changing the build type to iOS...
Is that missleading information?
I was almost positive ForEach was common amongst the different Exporters, gues i was wrong...
Im sure i heard plans about ForEach support for XNA, here on the forum.
ForEach should be top priority among all Exporters in my oppinion.
I think it is compatible with iOS. ExtensionView is outdated. It doesn't mention anything about Android, either. I don't have the iOS runtime, though, so I didn't want to say it was compatible when it wasn't. However, since it shows up when changing the build type to iOS, I think it is compatible.Quote:
Originally Posted by King_Cool
FAST LOOP METHODQuote:
Originally Posted by Del_Duio
You have multiple Instances of a Bullet Object, and want to handle them seperatly withouth MMF2 confusing them.
PREPERATION
- Allocate an ID_ for Bullet using an Alterable Value
- Spread Value 0 through Bullets ID_
MAIN EVENT
+ Allways
-> Start FastLoop "a" 'number of Bullets' times
+ On FastLoop "a"
+ Compair FastLoop "a" itteration index to Bullets ID_ value
-> DESIRED ACTION
There is nothing realy wrong with this method, its only that ForEach does this better and faster.
...
FOR EACH LOOP METHOD
You have multiple Instances of a Bullet Object, and want to handle them seperatly withouth MMF2 confusing them.
PREPERATION
None
MAIN EVENT
+ Condition
-> Start ForEach loop "a" for Bullet
+ On ForEach loop "a" for Bullet
-> DESIRED ACTION
...
You see how the two methods compair?
ForEach object Itteration loops require no preperation or use of Alterable Values, you dont need to specify how many time the loop should trigger, you just ( 1 ) start the loop for the Object and ( 2 ) create desired action in the 'On loop' Event.
When compairing the two methods, ForEach turn out faster, someone did a test but i cannot remember who.
Im quite sure you can run regulars loops through the ForEach also ( meaning loops which are not specific to an object ).
Wow you're right that is much easier all around. Thanks for going through the trouble of typing this all out for me, I'll put it to good use King_Cool!Quote:
Originally Posted by King_Cool
It is also worth mentioning that:
Some Conditions are Red.
Events that start with a 'Red Condition', do internal loops through all Instances of the Object automatically ( Instance selection is correct for such Events ).
...
Example:
'RainDrop collides with Backdrop' is a 'Red Condition'.
This means if 3 RainDrops collide with the Backdrop, the Event will trigger 3 times ( once for each RainDrop )
...
Think about it like this:
Events that start with a 'Red Condition', automatically does a FastLoop/ ForEachLoop thought the Object Instances in the Condition.
Hi there this helped me a lot but I wanted to know how to add a delay from when the edge is met followed by turning around and moving to the next edge like the enemies often do in Sonic The Hedgehog.Quote:
Originally Posted by happygreenfrog
Actually don't worry I managed to do it using 2 additional flags which seems lazy but it works!
Flag1 disables movement while the delay is on countdown.
Flag 5 (in my case otherwise flag2) also diables movement but turns off once the delay is over
Simply ?Attachment 25936
Thanks for your response. I have never used foreach statements before, I will give it a tinker. Looks dead simple in comparison to what I had. Mucho Gracias ;D
Just to confirm, I replaced the fastloop formula for the foreach one and kept the sensors, it worked a charm. Thanks for your help
Here's Patrice's example, with delay and no need for detectors.
Attachment 25937
The example works but not in the level i am using it in. The dino just turns left then right on the spot continuously.Quote:
Originally Posted by aenever
The level does use a lot of fastloops for a static engine if that is relevant to mention.
The level does not seem to like checking if a coordinate is an obstacle.
The level is 10700x2400 in size.
The level can handle the dino with sensors as the dino has 6 of them, 2 for wall collisions, 2 for floor collisions and 2 for edge which may seem excessive but it works without fail.
I see, well explained, makes sense for larger games. Best of luck at least your on the right track now :)