[jvanmetre]

Using MW 1.6.1 with Leopard (most recent release)...when I go to launch a render from Studio, wheel spins a minute or two and then it quits. Activity Monitor in Leopard states that Studio (is not responding) and I don't even see an instance of MXCL coming up in the monitor which I'd expect if it were launching.

Render preview in Studio works... wondering if it's a ram issue-- not enough?

I've got a QC 2.8, 2 gig ram.

Suggestions much appreciated.

jvm

[flower]

Hi jvm,

I get the same thing. Studio writes the myproject_tmp.mxz file but mxcl doesn't kick into action. What I do is go to the Finder, highlight the _tmp.mxs file and use the keys apple+O and that gets mxcl going. Bit of a pain, but I'm not too bothered by it. If I am doing tests, the _tmp.mxs file stays highlighted (as long as you haven't navigated elsewhere in the meantime)so clicking on Finder then apple+O is all you have to do.

But, I suppose would be better if it just worked the way its supposed to.

New '08 Mac 2.8 Octo, 2Gb Ram.

[jvanmetre]

flower-

Thanks for the reply...was in a bit of a panic as I've swithched completely to 1.6.1 on both windows and mac...model in rhino on pc, export as pack and go to mac and usually have required tweaking in Studio on the mac before rendering...figured it out just to open mxcl on the mac and bypass studio. A bit nerve racking though as I've had to change my ways of working with a deadline in front. I've actually streamlined workflow as a result!

jvm

[nachob]

We have just detected that if the path to mxcl contains a spacebar " " it can fail to launch from some applications. We are solving it for the next version but it can happen in the actual version.

nachob