I don't know if this is a glitch in my MMF2 program, or if it is supposed to happen. But when I make any kind of object a global object, it does NOT appear in any of the other frames I make. I thought if an object is global, it is supposed to appear in all frames. Even when I set an object global object first, and create a new frame afterwords, the global object still will not appear on the next frame. What is going on?
That's the way it is, and it's a shame. To make use of your global object, you'd have to copy/paste it (or drag'n drop it) in every single frame where you need it.
I had some weird problems when copy/pasting global objects (sometimes they stopped being global despite being marked as such etc) - that's when I thought "there's probably a reason why there are detailed instructions in helpfile for transferring global objects from frame to frame instead of just copy pasting them", as I also used to do the whole time - it's just a very natural thing to do.
Basically you have to open the frame where you want the global object to appear in the frame editor, open the source frame in the list (I forgot what's the name of the window, it's the one that contains frames as expandable folders etc) and drag it FROM THERE into your frame. Read the help if you don't understand my instructions.
Really? Well, thanks for saving me from re-installing the software.
Seriously, I remember back during their first generation products (TGF, CNC, MMFE). When you set an object as a global object, they would appear on every frame. You didn't have to copy the objects over.
Now, they have it set so they do NOT appear on every frame? Why did they do that? Wasn't that the point of setting the objects as global objects, so you WON'T have to copy the object over to the next frame, and all their alterable values are saved?
The alterable values (and animation frames and everything else) of an object are still saved between frames if an object is global.
Well I don't know if it's a glitch or what, but when I restart the frame of the global objects origin, I think all the alterable values of that global object are still reset. The only time it doesn't appear to reset is if the current value of the global object is carried over to the next frame.
They definitely should carry their values and everything else over as DavidN said.
As a side note, there are ways of breaking it (although looking back I think what caused it to break in that particular case is checking / unchecking the "global" option combined with copy pasting, not just copypasting), it'll probably be fixed in one of the next builds.
Posting Permissions
Reply With Quote