Maxwell Render | Official public forum

Just found out that v 1.0 can handle different .mxm's assigned to different faces of the boolean objects, just like cinema does!
You can even have an emitter "cut" from the, say, metal object!!!
Test renders to go!

PS. Let's to take a break from future plugin updates discussions
The pictures:
The ball with text booleaned from it.

The material (tag) setup of the ball.
(ball has standard plastic, text - emitter.

The resulting image with ml animation.


The only thing neccessary to do, is to check if "create single object" is highlighted. If it is - turn it off.

Could you post a screenshot+render to prove it, please? I cannot really believe - and didn't try it with the new version.

if you talk about assigning mxm on differents polygon selections in studio, thats not what C4d users are waiting, we are waiting the ability to assign any tag ( mxm, metal whatsoever) from within our app

if thats within the app, then send some screenshot please...

macray wrote:Could you post a screenshot+render to prove it, please? I cannot really believe - and didn't try it with the new version.

Will provide proof soon!

thomas lacroix wrote:if you talk about assigning mxm on differents polygon selections in studio, thats not what C4d users are waiting, we are waiting the ability to assign any tag ( mxm, metal whatsoever) from within our app

if thats within the app, then send some screenshot please...

It' within tha app. It is not a polygon selection assigning, but it/s interesting

ok, at first sight i thoutgh you were talking about poly selection, sure, the booleean works, except for ligth ( unless you edit the boolean and invert normals) for the polyselection, i usually split my selection to get another object so that it can be ready to render with maxwell, but its quite a painfull workflow ( mostly if the client want some modification, it happens every time...)

thomas lacroix wrote:ok, at first sight i thoutgh you were talking about poly selection, sure, the booleean works, except for ligth ( unless you edit the boolean and invert normals) for the polyselection, i usually split my selection to get another object so that it can be ready to render with maxwell, but its quite a painfull workflow ( mostly if the client want some modification, it happens every time...)

Yep. I was talking about booleans.

Hey guys... don't get hyped yet.
The only reason this works is because C4D creates two seperate objects when you use booleans without "create single object".

So there's nothing special about assigning two materials to two separate objects

Multiple materials on the SAME object is what you really want.

If you want another tip then, do the following.
a. Make a poly object
b. select the desired polys
c. "function - split"
d. delete selected polys from original object.

VOILA you have a seperate object with the selected polys.

Assign seperate materials.

Big deal

as quoted in my previous message

OOOps I'm getting long sighted.. I missed that.
Nothing personal thomas

noseman wrote:Hey guys... don't get hyped yet.

I don't!
That post was just to make a break from release dates discussions!

That post was just to make a break from release dates discussions

Oh really?
Where is my cinema plugin update?

noseman wrote:

That post was just to make a break from release dates discussions

Oh really?
Where is my cinema plugin update?

Hmmm... Psst, don't tell anyone, this thread is conspired one to talk about plugin updates! The posts above are written so that noone cen guess what we are doing here!

Where is our plugin update BTW

That's right, now that we've disguised the thread topic... Where are the plugin updates... namely a competent netrender and c4d compatible compositing tags?

Screw the speed, I just want functionality!

greg3000 wrote:That's right, now that we've disguised the thread topic... Where are the plugin updates... namely a competent netrender and c4d compatible compositing tags?

Screw the speed, I just want functionality!

Functionality = Speed!!!