Yeah I agree with HolyMonkey, you guys have made a great product that is always under-estimated by people who don't know what they're doing and immediately think it's a waste of time since they think they only have the built-in stuff to use. Then they turn around and play a really good game/application made with your software and they like it until they realize what it was made with which really pisses me off.
Well I discovered it effects ALL my global objects when the problem at hand occurs.
OH CRAP, I just realized I accidentally posted this in the file archive forum.
Whoops. :blush:
No problem, I've moved it.
It's probably to do with the fact i started my game in 244 I think Yves. I'll try a new file soon I guess! Sorry I always sound so harsh :P
I've answered this issue a long while back, I noticed that
To assure that anything you do to an object changes through a global object you should have all objects exist in your first frame.
[ Frame 1 ] Edited a Global Object here
[ Frame 2 ] updated
[ Frame 3 ] updated
[ Frame 4 ] updated
etc etc...
Now there was a problem, for some reason MMF missed a little going backward updated objects - behaviors, going forward from frame # 1 seems to fix this.
[ Frame 6 ] object from frame 6 edited
[ Frame 5 ] not updated
[ Frame 4 ] not updated
[ Frame 3 ] not updated
[ Frame 2 ] not updated
[ Frame 1 ] not updated
That goes for all animation changes etc.
Don't ask me why.
The only problem I ever had with it was that if I already had said object on 2 or more frames then made it global, and there is the slightest difference between the two already over the two frames (something simple like a comment in the wrong place in the Behaviour) they will not "actually" become global, but instead individual because they are already different.
Since, I have always made sure to make an object global before it appears on any other frame. Then there is no problem; you can make all the changes you want.
Oh yes, in this case, if objects are already different when you make one global and answer Yes to the question "Other objects with the same name and type exist in other frames, do you want to make them global too", then the others won't be modified when you edit one of them. MMF2 only updates the ones that are identical.The only problem I ever had with it was that if I already had said object on 2 or more frames then made it global, and there is the slightest difference between the two already over the two frames (something simple like a comment in the wrong place in the Behaviour) they will not "actually" become global, but instead individual because they are already different.
I agree this is confusing. In MMF3 I think we'll definitely change this system and make all the objects global to the application.
And maybe in MMF2 we could add an option in the properties of the application, to force global objects with the same name and type to always be modified even if they are different. I'll add that to the todo list.
OOJ, I can't reproduce the problem you mention. Are you able to reproduce it?
That would be... so awesome.I agree this is confusing. In MMF3 I think we'll definitely change this system and make all the objects global to the application.
And maybe in MMF2 we could add an option in the properties of the application, to force global objects with the same name and type to always be modified even if they are different. I'll add that to the todo list.
Posting Permissions
Reply With Quote