Motion 4 and Ridiculous Crashes

Question

I've been using Motion 4 for a few months now, and while I've experienced periods of repeated crashes -- which I've come to expect with Motion-- I'm seeing something new today:
I open a simple Motion project. I simply select a layer. Motion crashes. I trash the 'motion.plist' preference file. Reopen the project. Motion crashes as soon as I do ANYTHING. My computer is definitely fast enough (specs below) to run Motion, especially a project with only three layers. I've recently reinstalled the entire operating system and all of Final Cut Studio, did all the updates, and everything else works great. Just Motion doesn't seem to work AT ALL.
Any advice? I'm attempting to follow along with some online tutorials, all of which are great, none of which seem to mention Motion 4's crash epidemic.
Thanks so much.

Answer 1

Yeah, Motion does that. But it shouldn't and it is often an easy fix if we can debug it with you.
In your case, the crash logs are essential. There will be a statement that indicates which thread crashed and there will be some uselessly cryptic code in there. You can find your logs in Terminal, or some other obscure utility app. Open a couple of them and see if there is anything common and post that description. You can also copy the phrase and googleit, amazing things come from independent research.
Rebuilding your system suggests all kinds of user issues that may or may not be causes or associated but scorched earth rebuilds are rarely necessary. Probably just your card's software needs to be ref lashed.
Bogiesan