[michaelmarcondes]

Ok.. here is the thing, I set all the scene and all.. well I hit write mxs or render... it crashes in a heart beat .
I am on win32 c4d10.1

[Carl007]

Well, I know just what you mean...
I try to turn of everything but the camera, some emitter and perhaps the floor or backdrop and then I write a MXS file, ok no crash, then I try to render the scene, ok no crash, then I add more and more objects and repeat the process with writing MXS and rendering. About now one would have pinpointed the problem... Don´t forget to save after every change to the scene.

Another hack is to create a new c4d document and copy the contents oft the "bad" doc to the new one, except the "maxwell render settings object".

I try to have all the textures in the same folder as the c4d doc.
I try to keep every bitmap as a RGB .tga file or hdri
Beware of too long path names.

I really hope this alpha/beta behavior will cease to exist.

[michaelmarcondes]

thanks... what I did try now was to take out the sky element from the scene.. I mean. . the c4d sky
now it is writing the mxs . . but it is taking forever and I dont know if it is working or not!

[Tyrone Marshall]

Hello Michael,

I understand the problems you are currently experiencing.

Be sure to check this thread there are a few issues at the moment with the plug-in you are using that will cause these problems.

ref: http://www.maxwellrender.com/forum/view ... hp?t=22962

The issues are known.

[michaelmarcondes]

ok thanks Tyrone . . .I will check it out

[Tyrone Marshall]

ok thanks Tyrone . . .I will check it out

One more item Michael,

Can you post a link to this scene that crashes. I want to test it.

[michaelmarcondes]

k.. that no texture applied error we know..ok.. but how can I make it work?
Any custom mxm I add it gives me this error!

[godzilla32]

Hi guys any news here? I'm having major problems rendering and writing MXS files. My model is very simple, it is a hedge that I'm doing some tests with for a new project that I'm about to start. The error message that I get is,
Application error caused by plugin "maxwell.dylib"!

Any ideas what hte problem might be?

Cheers.
Ben

[Boris Ulzibat]

Hi guys any news here? I'm having major problems rendering and writing MXS files. My model is very simple, it is a hedge that I'm doing some tests with for a new project that I'm about to start. The error message that I get is,
Application error caused by plugin "maxwell.dylib"!

Any ideas what hte problem might be?

Cheers.
Ben

Check if there are multy materials applied to different poly groups of your object.

[zoppo]

Check if there are multy materials applied to different poly groups of your object.

yes - that's a killer. and an annoying one!

it's no fun to do your poly selection in studio

[michaelmarcondes]

Yes Ben.
custom mxm is not working well in the new plug... it will be fixed soon.. for now use the standard ones and move to studio to give them your final touch.

[AndreD]

..same here..
just tested to render about 10 1.1 scenes..
Not a single one that doas´nt crash cinema

[godzilla32]

Hi guys any news here? I'm having major problems rendering and writing MXS files. My model is very simple, it is a hedge that I'm doing some tests with for a new project that I'm about to start. The error message that I get is,
Application error caused by plugin "maxwell.dylib"!

Any ideas what hte problem might be?

Cheers.
Ben

Check if there are multy materials applied to different poly groups of your object.

That was it!
Thank you.
Cheers.
Ben

[shen.de]

hi guys anything new here?!

after some projects I've found some time today to install 1.5(with new c4d-plugin)...
I've read the problems people had...

on my test I experienced:

- sometimes plugin doesn't find mxm-materials altough the path is right

- a normal studio setup with a chair took about 10mins to reach SL7 ... same scene reached SL11 with 1.1

- when I apply a cinema material(texture) with a maxwell plastic material(then cinema-material into texture-tag) c4d shuts down with bugreport

these are the first-10-mins-issues

[leoA4D]

I have a C4D scene containing Area lights with Objects dropped into the Details tab>Object field causing a violent crash. I confirmed it by removing the lights and objects and pasted them into a fresh MWR and gave it a with test – crashed in a heartbeat – and without test – as a clean area light, no crash.

L.

MacBook Pro, 2.16GHz, 2GB, Mac OS 10.4.9
Cinema 4D v.9.6UB, M~R v1.5.0.2