Maxwell Render | Official public forum

I installed the update for Maxwell render2.5.1 -C4D 12 today. Also the plugin.
If I choose "new maxwell material" and try to open it within C4D to add a mxm-file, the whole programm crashes.

Waht's wrong there?

Can you tell me more about your setup? Operating system & version, exact Cinema 4D version, 32- or 64-bit, etc?

MacOSX 10.5.8, 32bit, C4D 12.0

I discovered further that maxwell works fine if I open an old maxwellscene. Even if I open one of the old maxwellmaterials in this scene and choose a new mxmfile from themxed browser and drag it to the icon of the old mxm, C4D builds a new maxwell-material like the chosen one from the mxed browser. But as far as I click on the unspecified maxwell-texture-icon, C4D crashes .

Thanks, I can confirm this when running Cinema in 32-bit mode. Could you try running Cinema in 64-bit mode and let me know if it still crashes then?

Sorry - that's not possible.
I run the software on a MacbookPro which doesn't allow 64bit mode.

I see; in that case there's no easy answer I can give you at the moment -- the crash appears to happen inside the render engine. So I'll let you know here if/when I diagnose it or find a workaround.

Thanks for your efforts!

At last it's possible to work with the upgraded version as described above:

Open an old naxwellfile, delete the geometry but not the textures.
Create newtextures by choosing it with the mexd browser and drag it to the opened icon of an old maxwelltexture.
C4D creates a new maxwell texture.
Don't touch the unspecified maxwelltexture if there is anyone in your material manager.

Hope we are going to get an "upgrade" of the 32 bit-upgrade soon...

That is not going to be a real solution; any rendering with Fire in the plugin, whether material preview or otherwise, is crashing in 32-bit Cinema here. I would recommend rolling back to the previous version; it should work fine, except that it will not be able to read MXM files written with Maxwell 2.5.1.

You're right. Didn't check that untill now.
Are the updates not tested before releasing them?

It has been tested internally, and has also been made available as pre-release to customers here on the forum, since January. Apparently not many people use Cinema in 32-bit mode on OSX.

I have posted links to a 2.5.1.5 release preview (see here) which addresses this issue, so please give it a try.