[Hindsight Productions ltd]

Actually trashing the prefs only brought up the template screen, but I did find a fix. Apparently when Tiger has been archive reinstalled after having patched Motion 1.0 up to 1.1- it leaves Motion in an unuseable state. “Software update” sees it as 1.1, and a reinstall of Motion leaves it in this state of broken. Trashing motion and then reinstalling it puts it back to 1.0 and then software update will patch it to 1.1. This fixed my problem.

[Hindsight Productions ltd]

This is the only thread of many I’ve read that may actually fix this. Trying it now.

YES! Thank you thank you!!

Note: the only file I trashed was the app itself.

Eric

[Hindsight Productions ltd]

I feel really stupid for not having tried it earlier, but the fix was simply to move com.apple.motion.plist out my user prefs. I’d been troubleshooting the main system prefs the whole time.

[Hindsight Productions ltd]

Same problem. Reinstalled Tiger due to spotlight issues and this has been the case ever since with motion.

Thread 3 Crashed:
0 com.apple.Foundation 0x9289de80 _NSRaiseError + 264
1 com.apple.Foundation 0x9289dbbc +[NSException raise:format:] + 40
2 com.apple.Foundation 0x92876cec -[NSObject(NSForwardInvocation) forward::] + 176
3 libobjc.A.dylib 0x909b20d0 _objc_msgForward + 176
4 Ozone 0x0145b1c8 OZCacheManager::Instance() + 168
5 Ozone 0x01259aac GLRenderer::render(OZScene*, OZRenderParams&) + 204
6 Ozone 0x01293570 OZRenderUnit::processRenderInstruction(OZRenderInstruction*) + 272
7 Ozone 0x012933d4 OZRenderUnit::execute() + 68
8 Ozone 0x012923b8 OZExecutionUnit::executeLoop() + 264
9 Ozone 0x01291cbc OZExecutionUnit::executeLoopWrapper(void*) + 44
10 com.apple.procore.framework 0x00080444 PCThread::startup(void*) + 36
11 libSystem.B.dylib 0x9002c3d4 _pthread_body + 96