MMF2 Build #249 - Final version

Global objects do not stay global in editor, there is a few things like changing a name of the variable when multiple selected that makes unglobal in editor and sometimes they just became unglobal for some reason, it's pretty frustrating when working in editor with multiple frames, it's not easy replacing all the objects, or changing all the values in each frame.

That would be a wonder if it would be fixed.

Could you describe very precisely the steps to reproduce these problems please? Thanks!

First one that i am sure off is if you select multiple objects that are global and try to change the name of a variable for example, renaming alterable value A into Damage or health. It makes all of them not global anymore in the editor, meaning every future alteration; if i add a new animation or change damage for a weapon from 4 to 5 it will only affect the object in that frame, instead of all instances of that object across frames, like it normally does.

I think adding groups to multiple objects selected at once also does that.

And making an object global that already exists in other frames, but is slightly different, doesn't make them global in editor to begin with.

I think there might be something else aswell but i cant remember what.

I found the "Restrict actions" bug.

http://mfa.aquadasoft.com/view/1286909219-restrict_actions_bug

The event of the "Restrict actions" condition collapses when the timer of the frame more than 10 minutes 55 seconds.

I can confirm the above bug. Build 249, MMF2 Developer.

A first animation sequence of the moving(or shooted) object is can't detect "Has animation is finished?" condition?

Quote:

---

Originally Posted by ASD

A first animation sequence of the moving(or shooted) object is can't detect "Has animation is finished?" condition?

---

If this is the bug I'm thinking of, I think I have reported it like 4 times on various occasions. And sent the example files.

Hey just a simple suggestion for consistency

The data elements viewer should have a tab for Pixel Shaders in HWA. This is important for opening source code and all, so it seems logical. If theres ever time for it

+1

Are there list of known issue of current version?