Activity › Forums › Apple Motion › What to do to make Motion 3 work properly????
-
What to do to make Motion 3 work properly????
James Godwin replied 18 years, 5 months ago 6 Members · 14 Replies
-
Jeremy Garchow
November 22, 2007 at 6:31 pmI had the orange overlay screen too. Real strange.
It has to be some sort of graphics card issue I’d imagine.
I need to update my system as see if it gets fixed. What versions of everything are you on, James?
-
James Godwin
November 26, 2007 at 3:15 pmFinal Cut Studio 2
Motion 3.0.1OS X 10.4.10
Radeon X1900 graphics
I found that I can only export up to four frames at a time without getting the orange boxes, and after 3 exports I get them anyway so i save, quit, reopen and re-export and it works. now, i do have a lot of layers, all in 3d space, but nothing this system shouldn’t be able to handle…
James Godwin
Post Production Guy
-
Matt Doe
November 26, 2007 at 3:23 pmI have been having problems with Motion 3 for quite some time. I run a quad 3.0, 6 gigs ram, x1900 system and for the past few months motion has been crashing.
Mainly it would crash if I tried to move around in 3D space with a big sweeping move, or anytime I would switch from perspective view into active camera view, it would crash. Having saved after every change I finally got the project done I was working on.
I thought all would be saved by the new update to Motion, which supposedly brings it up to date with leopard, correct?? (which I am running). I updated all my software and the OS, now Motion will not even open. I click it in the dock and right off the bat I get the “This Program Unexpectedly quit” and yet all other FCP studio programs open up no problem.
I guess an reinstall and re-update of Motion is in order? Any other advice would be greatly appreciated.
Thanks
-MATT
-
James Godwin
November 27, 2007 at 6:20 pmSo, i found a workaround that may be better for others.
The project that I am doing requires that we update certain text in parts roughly once a month. In preparation for this I took each layer in the timeline and rendered them out in their own QuickTime movie along with the camera movements and this seemed to work much better.
Since Motion only has the one layer of elements and the camera moving it rendered everything quicker, except one of the layers that has a blur on it, which is where it crashes every time it hits a certain part of the export. But, at least it crashes faster and more predictably with this method.
James Godwin
Post Production Guy
Reply to this Discussion! Login or Sign Up