[doc]

hi,

i have the new maxwell plugin installed. when closing cinema i`m getting an error message every time. if the plugin is removed everything works fine.

any idea what could cause this??

thanks for help.
marcus

[liquidlight]

Same here with C4D 9.6, OS X.

[chromecity]

Same here with C4D 9.6 WinXP Pro SP2.

[firebird]

same here! funny thing, I only get this message after closing maxwell client, means I close C4D, and when I stop rendering and close the MX viewer, then I get this error message, although I have closed C4D half an hour ago!!!!

so what programm is responsible for this error message, C4D or Maxwell???

[jurX]

....no problems here!

[spekoun]

Same here... When you start render via Cinemaxwell and let it render and during this rendering you close C4D, then C4D will not close. It looks like it is closed, but start manager and you will see. App is closd bu process still runs and still reserves memory... Process is closed with error message when MXCL is closed...

[goncalo]

yes me too

[firebird]

Same here... When you start render via Cinemaxwell and let it render and during this rendering you close C4D, then C4D will not close. It looks like it is closed, but start manager and you will see. App is closd bu process still runs and still reserves memory... Process is closed with error message when MXCL is closed...

so the solution is to save only the mxs file, close C4D and then doubleklick the mxs file to render! not the best ways, is it???

[dyarza]

I have the same problem. C4D 9.6 on Win XP. Althought it does not seem to affect anything, it is just anoying.

D

[spekoun]

Same here... When you start render via Cinemaxwell and let it render and during this rendering you close C4D, then C4D will not close. It looks like it is closed, but start manager and you will see. App is closd bu process still runs and still reserves memory... Process is closed with error message when MXCL is closed...

so the solution is to save only the mxs file, close C4D and then doubleklick the mxs file to render! not the best ways, is it???

Or I sometimes close C4D via Task Manager... Not very correct solution, but it works too..

But this is a bug which i can live with. I sufffer with Cinemaxwell workflow much more... I know i repeat it in every post, but i cannot help myself

P.S.: to firebird: I am planning to buy Conroe very soon too. Can you share some experiences and speed tests, when you get your one???

[lllab]

mine crashes two when closing cinema...

[chromecity]

Just to clarify, compared to the people who are mentioning closing the client, the .MXS files, and so forth...

What I'm experiencing happens as easily as:

1.) Open Cinema 4D.
2.) Don't do anything except close C4D.
3.) Unhandled Win32 Exception.

Definitely attributed to the Maxwell plugin since it does not occur if you move the Maxwell plugin out of the C4D "plugins" folder.

[seco7]

Same problem here, C4D 9.6 on XP.

[stu.dio]

Same problem here in Mac OS X 10.4.7 dual G5
But one the mac it says "The application CINEMA 4D PPC quit unexpectedly." with the options to close, report or reopen.
??

It doesn't effect any work but becomes annoying if you shut down and leave only to find the next day your machine is still on with this message burning a hole in your screen.

[firebird]

P.S.: to firebird: I am planning to buy Conroe very soon too. Can you share some experiences and speed tests, when you get your one???

yeah definetly, I was assembling the whole stuff yesterdays, just to notice that my main power supply is out of date and doesn´t match with my mother board, so that´s another 100 bucks to spend! uahhhhh!