#339199
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 .
#339204
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...
#339206
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.
render engines and Maxwell

well I don't think AI will remain like it is now. […]

Help with swimming pool water

Hi Andreas " I would say the above "fake[…]