Guys,
Take a look at this, everything goes right until you have hit an obstacle. Hows that possible? It somehow effects all the other object too during the loop.
Printable View
Guys,
Take a look at this, everything goes right until you have hit an obstacle. Hows that possible? It somehow effects all the other object too during the loop.
After a fast loop / fast function is executed, MMF2 forgets the object selection (filter). This means that you need a duplicate "Object ID == Loop Step( "Fast Loop object", 5)" condition at the end of events 21,23,25 and 27. This will remind MMF2 that the actions should only affect that one instance of the object.
Sidenote #1: This is a similar quirk to that of spread values and loops, where MMF2 puts it on a "to do" list and then forgets about it.
Sidenote #2: It would be smoother to set the position of the Active System Box Object in the always event, and I see no reason why you don't only spread values when people join/leave. I guess this is only for testing so it ain't as efficient as possible.
Wauw! thanks man! :D !!! It worked! About sidenote2, yes that is right. Just for testing purpose that was.
Ok, next problem... when having more objects i can only move object[0] with the right speed, and all other objects go crazy when moving. Why is that?
(click on an object to control it)
Also i may add that when reaching about 100 objects the tester slows down to 20fps... thats a problem.