[Tyrone Marshall]

Example of Maxwell 1.1 Custom mxm that causes Cinema to crash when attempting to render or write an mxm file.

The more I see the the faults with the new plugin the more the problem looks like it's going to take longer than a few days to resolve.

I hope in fixing new Custom mxm materials that using the old 1.1 custom mxm's don't get even more damaged.

Thanks Becco for this one, I believe this one is also tied to a similar scene where you can have an object with multiple cinema 4d materials/polygon selections and no maxwell render tags involved.

There is not much we can in the interim but allow the plugin developers the time to work through the issues. This is not directed to you, but bad comments and a urge to get a fast turn around will not be the best way to get a good working product. Let's be patient and await more news. Next Limit is aware of the issues with the plug-in and they are aware of the feelings expressed in the forum.

[Becco_UK]

I'm all for waiting because the option is clear - use Maxwell with Cinema and put up with a very bad job or change to another software package/render engine.

I wrote here about 18 months ago of Next Limits' history regarding RealFlow Cinema plugins and how this might impact on the Maxwell/Cinema plugin- turned out to be more or less correct.

Personally I'm sticking with Maxwell for a while longer because it can still produce the best quality3D images around.

Lets get a quality Cinema plugin for it soon!