Maxwell Render | Official public forum

I have just installed Cinema 4D R11 and the latest Maxwell Plugin (version 2.1.3.0) on a clean installed Mac OS X Snow Leopard. When I open C4D in 64-bit mode and try to load a 4096x4096px texture in a new MX-material then C4D freezes (the color ballon starts spinning). I have restarted the Mac, but it doesn't help. Changing back to 32-bit mode and everything works fine and I can load the textures without a problem..

I had this same issue with the last MX-plugin when running in 64-bit mode, I thought it was one of the fixes in this new release?


// tennet

Is it one particular 4096 x 4096 texture, or any? What is the format?

Hi, this seem to happen with random files. I've tried TIFF with no compression, TIFF LZW and some random JPEG files also. I have tested this both at home running Cinema R11 + Maxwell 2 with the latest plugin and at work using the same setup. Exact same problem. I have to log off or restart the computer after every crash, the Cinema document window is frozen in the background, but other programs can be used during this.

If I just open Cinema, add a new MX material and then try to load/unload different textures in the "Ref 0" slot then it will suddenly freeze. I tried to see if it had to do with files that were loaded over the network, but it also crashes when loading files from the desktop (for example a 3000x3000px JPEG). It is the same files that cause the crashes all the time. Some files can be loaded and some just can't. I've opened them in Photoshop to see if something is different, but they are all normal 8-bit files, no clipping paths or alpha channels included.

Changing back to 32-bit mode and those same textures load perfectly.

// tennet

Could you email me the smallest one (jeremy at nextlimit dot com) so I can open it under a debugger to try to see what the problem is?

Thank you Jeremy! I have sent you an email with a texture for troubleshooting. Hope it helps, let me know if you need any more info.

// tennet

Thanks -- it also hangs here and looks to be either OSX- or Snow Leopard-specific. I'll let you know if I find any good workaround.