Quote
ssjenforcer wrote: I would upload it but it is a 50 Mb scene file. It is a simple grass textured plane, two figure objects fr om C4D, a platonic in the air, and an X-Wing, all on a tracked camera shot.

Yes, please do it. I need the project .c4d file to figure out the problem.
If I do a scene by myself I will do everything right and will not get any problems. The file you sent me is a .fbx spacecraft model. I have imported it and it renders very fast. But I need to see the problems that arise in you scene. 50Mb is not a problem, you can use a google drive for example and send me a link.

Thank you for files sent, I see them and will check soon!
Btw, in previous message I have shown 6.48 iterations performed in 2:22 min. And now I see 16.14 iterations in 49 sec. Strange! But I will look inside

No, in this case distance property inside Sun tag doesn't do anything. It moves the object near-far but the overal implementation is that it's infinitelly far. Maybe native Cinema renderer interprets it somehow like spot or area light source. Maybe in Cinema the Sun tag distance doesn't have effect for Infinite light sources at all, I haven't tested really.

The Sun Light object in CentiLeo menu is based on Cinema native Infinite light source + CentiLeo light tag. It has no position, it considers it's infinitelly long away from the scene. It only illuminates from a certain angle which is controlled by object coords.
If you want to change the shadow softness casted by object when illuminated by this light then just change the "Lighting angle" in CentiLeo light tag. Make it 1-30 degrees or anything.
If the light intensity become dim or very bright then change it either as Overall Multiplier in CentiLeo light tag or either as Intensity in General settings of this light object.

Operating on rendering animation frames is done in Cinema render settings (button Edit Render Settings), menu item "Output". In this section you will be able to select Fame Range to render.
Saving each frame automatically to file is controlled in Cinema render settings, menu item "Save". These are basics of Cinema 4D.

What's your scene? What is this green field? A texture? A forest? Surely it looks strange slow. Please can you send me this scene file for tests? I am curious what's whong there.

Sure I will do this, there are Chinese files actually. Btw, it's possible to do even now for any use. He can just explore the res directory inside CentiLeo plugin, find *.str files - they describe all GUI words that we use for this or that module.
Also it's possible to translate Cinema/CentiLeo node space GUI for node materials/shaders. To do this one may open Resource Editor (type this in search string in top right corner of Cinema GUI). In this resource editor a user may find the CentiLeo nodespace database and go through all the materials and shaders to translate what is "Bitmap", what is "Ramp" and etc. There are not many, and things are quite easy.

Kaki, thank you very much! I hope we will be able to make translation to Chinese at some point in the future. Of course it includes not only renderer interface translation, but also a future documentation. Also here on this forum it's better to use English language (even translated by computer) to better search the information.
多谢

DGFD, what Cinema version? What console? CentiLeo also has some debug console - is it what you open?

You can increase the multipliers larger than 1. Just type the value or use top-bottom arrows. 0-1 range is only for the left-right slider just to make the fixed range.
One guess is that you probably played with exposure too much or maybe with the scene scale. I just wanted to check this all by myself

Well, we tried to make our shader nodes similar to C4D shader nodes at some extent. There will be also other improvements there.
And for sure there will be a nice documentation with a lot of examples on shader nodes.

ssjenforcer, how things are going? Still no message on our email

Does your light has CentiLeo light tag? There there is a Multiplier and there are Multipliers of intensity for Camera, Diffuse, Reflection and other layera. Increase them and increas the overall Multiplier.
Also please send me an isolated scene example that reproduces the problem either attaching here or to info@centileo.com. I will look there. Really all these multipliers work out of the box, maybe you hit some problem probably with scene scale or scene exposure or something like this.

hao qiqi0, very nice, thanks for sharing! Did you use procedural Flakes node combined with Ramp node for colorizing the individual flakes?
Btw, the Flakes node also has greyscale output and it can be used for reflection roughness variation in case it's needed.

hao qiqi0, maybe let's talk English?

No, the caustics are not very easy to implement. But they are important. We plan to integrate them after commercial release. It may take months since now.

Normal maps are needed for fake bump effect. If you need this then in a Bitmap node please check "Is normal map" flag.

Show examples of your pictures where you think displacement is not so correct.

Sure there will be a manual with nice examples and a material converter, this is a must have. We tried to make CentiLeo very easy to use, we will add a lot more features to cover everything. The remaining part of development is not so large.

Probably not a bug. CentiLeo uses Focus Distance value from C4D native Camera object. This value can be changed by C4D native tools, animated and targeted if I am not mistaken.
On top of that this Focus Distance can be changed inside CentiLeo IPR window with [AF] button (auto-focus). But this [AF] change will not make the focus distance to follow some object in focus. To do this, Cinema tools can be used, Cinema's autofocus with picker button.

Hi Hao and welcome here! Caustics are not yet supported. They will be integrated in a longer term future as an additional render layer without any settings, but with a separate checkbox to add caustics per light source.