[mashium123]

Hi.

I don't get, what my fault could be. When I hit the render button in plug (the new one) mxcl starts and the render starts. When I stop the render and close mxcl, both programmes (mxcl AND cinema) crash.
They don't freeze or s.thing, they close, as if I had shut them down.

This is not something scene dependent. Happens in every small to large projectfile. Hmm...

Could someone help me please?

BTW: I use Cinema 8.5XL, if this does mater....

P.S.: I'm able to open the produced mxs-file in studio and render it. But nothing happens there, when render is being stopped and mxcl being closed. None of active programs shut down, everything works fine.
So this problem is only concerned to the c4d-plug.


Thanks in advance.
Mesut.

[glypticmax]

Hi Mesut,
Do you have Task Manager running?
If not, look at it when you stop a render.
I had some problems, until I waited for everything to calm down (CPU useage dropping) before closing Cinema or mxcl.
Its been a while since I've had problems.
I'm using Cinema 9.52 XL.

Good luck,
glypticmax

[mashium123]

Hi glypticmax,

thanks for trying to help.

I tried and looked at task-manager. And it does not looks unusual, what happens there.
After render-button in c4d-plug is being hit, mxcl.exe and cmd.exe additionally appear and mxcl starts taking its place in the memory and cpu-usage, the render begins and continues in a normal way. After pressing the stop button in mxcl the memory usage remains about the same and the cpu usage falls down on a normal "calm"-status.

So nothing unusual here.

With closing the mxcl (either by using 'Exit' in the menu or by the 'x'-sign) the same problem appears -> Cinema4D also shuts down.

It's *quite* annoying to start all over again and again and again... just to get one test-render after an other.

Maybe someone has got another idea?

Thank you.
Mesut.

[mashium123]

Hallo everyone.

Just wanted to tell, that a de-install followed by re-install of the maxwell package fixed my problem.
Well, I can not really tell why the problem appeared and what finally the solution was.

But the brute-force method of reinstalling the maxwell package did it for me.

Thanks. Mesut.

[mashium123]

Ehmmm....sorry to continue my monologue. But my problem still remains.

The reinstall procedure mentioned above did it... but obviously only for a first run. (You may recognize that I was not able to run 3d too often in the past days or so...) After that the same problem appeared again.

I reinstall again, and the same problem appears again. But it's kind of weird. I am not able to reproduce the problem in a regularly manner.
Everytime I try to change just one action after another to find the problem, no crash happens. But when I leave the test-row and change the complete situation the double crash (mxcl and cinema) appears again.
But not always!
Mostly (is this an english word at all?) the problem appears, sometimes it does not. Sounds weird. Well, welcome then.
Still everything is totally independent from scenes. A simple cube render leads to same as "complex" scenes.
May the plug be buggy, is it my cinema (normally c4d works 100%), is it mxcl? Or am I the bug in the end?
Hmpf.

Mesut.

[lllab]

here the same happens,
after closing mxcl cinema crashes most of the time...

anyone else?

cheers
stefan

[noseman]

C4D crashes on quit whenever I have the Cinemaxwell plugin in the plugins folder.

[glypticmax]

I had a variety of problems with C4D, Cinemaxwell, Studio, MXCL running at the same time, so I just got in the habit of closing C4D/Cinemaxwell before I booted Studio to work on my renders.
My little 2 gigs of RAM get eaten up pretty quickly with -ml or high res renders and closing Cinema gave Maxwell more RAM to chew on.
I have definately had more problems with the V1.1 plug than the previous incarnation.