[Boris Ulzibat]

A test scene i made to chack the workflow using Cinema 4D+M~W.
It contains both preset and custom materials (metal, glass, glossy and rough plastic, parquette) HDRI and emitter object.
After couple tests of trial and error i got that the workflow is not that bad
Need to figure out two things more:
1) how to rotate HDRI from within Cinema? (both sky and texture rotation give no result) *my thought is to create a sphere and assign emitter mat to it with HDRI as a texture*
2) how to enable Multylight feature? *tried [-ml -d] and [-d -ml] arguments - no effect*

[noseman]

Dear Boris, since you are new to Cinemaxwell please have in mind that MANY features that SHOULD work in the cinemaxwell plugin are non operational. The official statement of Nextlimit until cinemaxwell gets an update (it is the same as last year) is to use Studio.
Your choices are:

a. use cinemaxwell plugin as is and don't expect too much
b. use studio
c. stop using M~R and wait for the new cinemaxwell release.
Rumor has it that they are finally making an effort to make a decent plugin and we will have it soon (soon = from 1 week to 2 years)

I hope things will change. You are welcome to hope with us.

[Eric Lagman]

1) how to rotate HDRI from within Cinema? (both sky and texture rotation give no result) *my thought is to create a sphere and assign emitter mat to it with HDRI as a texture*

Not sure how to do this either. I tried mapping an mxi onto a sphere, but rendertime will go up quite a bit. This treats it like an interior rendering which the archviz people are having so much trouble getting to clear up. For some reason when you use the mxi as sky it does not affect the rendertime like this. It actually seems to go quicker than using just emitters for lighting. Your test looks good by the way.

[Boris Ulzibat]

Dear Boris, since you are new to Cinemaxwell please have in mind that MANY features that SHOULD work in the cinemaxwell plugin are non operational. The official statement of Nextlimit until cinemaxwell gets an update (it is the same as last year) is to use Studio.
Your choices are:

a. use cinemaxwell plugin as is and don't expect too much
b. use studio
c. stop using M~R and wait for the new cinemaxwell release.
Rumor has it that they are finally making an effort to make a decent plugin and we will have it soon (soon = from 1 week to 2 years)

I hope things will change. You are welcome to hope with us.

I'was waiting for a decent plugin too (and still do), because until now, i thought things are REALLY bad:)
I know, many features are missing BUT i use a Mac, and thus i have a choice - Maya with no plugin at all or Cinema 4D with this plugin.
Working with Maya was like meking an object, then trying to scele it in studio to appropriate scale, then compose all of the objects and material/render them.
The Studio works really slow with a lot of objects, and maya's triangulation is far from ideal... so understand me - the workflow with Cinemaxwell is THE workflow

[Boris Ulzibat]

1) how to rotate HDRI from within Cinema? (both sky and texture rotation give no result) *my thought is to create a sphere and assign emitter mat to it with HDRI as a texture*

Not sure how to do this either. I tried mapping an mxi onto a sphere, but rendertime will go up quite a bit. This treats it like an interior rendering which the archviz people are having so much trouble getting to clear up. For some reason when you use the mxi as sky it does not affect the rendertime like this. It actually seems to go quicker than using just emitters for lighting. Your test looks good by the way.

It's sad... ok, we've always got the Studio, anyway
BTW Thanks

[beppeg]

The command line in the c4d plugin don't work
The workaround for -ml is to start the render and, in the mxcl, after voxelization, hit the stop bottom, go to the render setting and check ml and then hit the play bottom
Now you can play with multi-lights

[noseman]

Since I'm on a mac too, I have decided NOT to use M~R until it becomes a real product.
Thank goodness, instead of losing time trying to get M~R to work, I invested this time to learn more about Advanced render.
It has already paid off.

[Boris Ulzibat]

The command line in the c4d plugin don't work
The workaround for -ml is to start the render and, in the mxcl, after voxelization, hit the stop bottom, go to the render setting and check ml and then hit the play bottom
Now you can play with multi-lights

Thanks, i figured this way too!

*Chanting: "need to be patient... need tobe patient..."*

[mashium123]

Hi there.

Hm. Well, here the -ml thing in c4d plug works just fine.
No need to work around for me.

This is what i put in the command line in plug:

-d -ml



Mesut.

[macray]

No problem here as well. Don't know why this shouldn't work. Tried it several times and it does what it's supposed to do.

on WindowsXP

[zoppo]

Hm. Well, here the -ml thing in c4d plug works just fine.

same here.

For some reason when you use the mxi as sky it does not affect the rendertime like this. It actually seems to go quicker ...

can't confirm this. if you try hdri and -ml you can see that the hdri lighting seems to produce more noise than the other emitters.


and about rotating the hdri: does someone know how to do this proper from studio? i can rotate it and see it in the work space but in the render it changes ...

[sunmade]

crashes when I use -ml option in plug in command line...

have to use the workaround as well.

[zoppo]

-ml uses very much memory so you have to be carefull with the output size. maybe you don't have enough memory for both running c4d and -ml rendering?

[sunmade]

possibly a RAM isue.

I have 4,5 GB RAM

not sure about the scene size nor poly count.

[Boris Ulzibat]

possibly a RAM isue.

I have 4,5 GB RAM

not sure about the scene size nor poly count.

I have 3 gb Ram, MXCL crashes when rendering with -ml option in resolutions above 800*600.