Hi RAin3D_! I have fixed the issue with polygon restriction tag names in Chinese language.
Thanks a lot for reporting this issue and giving the files that really helped!

That's fixed! Sorry for that stupid issue, I haven't tested really well in that area

Actually to change the output range of Bitmap image the Map black/white can be changed. They help to scale or invert the image. This is an example of invert:


You can also change the distribution of the values between black and white colors of the image. For example this can be done using CentiLeo gradient node. Just look that middle grey values in the gradient ramp are changed to prefer darker values for the larger part of the input range.

Quote
ssjenforcer wrote: I have the colour texture and glossyness and reflection which I know where to map in the material, but what about metallic?

CentiLeo has roughness, not glossyness. They are reverse to each other. You either reverse the glossyness texture using output black = 1 and output white = 0 or enable "Use glossyness" flag in material settings.
As for metallic - it's not directly supported right now, it can be used to tune behavior of reflection parameters. I will make a slot and a mode for it. Currently the picture of metallic can be assigned to IOR, but the range of bitmap metallic should be adjusted, because for metals the IOR should be larger than one. E.g. you can experiment with metallic bitmap output black = 1.5 and output white = 4.0.
Reflection1 and Reflection2 are absolutelly the same reflection, but there are 2 of them one on top of another one to get more freedom in hand for various metal implementations.

Thank you!
Are you doing machine learning experiments in a separate application to C4D? Or in C4D itself?
I am quite interested in finding a fix to your reported issue.
Btw, in one of your past topics you talked about supporting matrix color attributes https://centileo.com/forum/messages/forum19/message1207/220-if-i-have-a-spherical-field-with-color-r...
This is supported since some time ago: https://centileo.com/news/145/centileo-for-cinema4d-0610/

Too many polygons is not a problem for CentiLeo ) It can eat any counts. You may see an example of our out-of-core technology https://centileo.com/news/147/centileo-out-of-core/
Btw what's you system CPU RAM size?

A lot of metalls can be nicelly implemented with 2 or even more reflection layers stacked on top of each other. Generally there is a medium glossy reflection 2 and clear mirror layer on top of that.
Reflection 1 can be a specular mirror coating with roughness = 0 and IOR = 1.5 while Reflection 2 may have higher fuzzy roughness = 0.3 with IOR = 2 and it will sit below the first reflection. Then a diffuse layer is placed with some color.

Hi ds, and welcome here! It looks strange. Out-of-memory is likely to be not CentiLeo error, but the one of C4D! Also the general PV render doesn't work when IPR is already running. Close IPR and then launch PV! If that doesn't help please can you send a scene with alembic inclusion to info@centileo.com for my investigations on the problem?

I hope to implement a system where shadow casts can be controlled by user per object or in some mask system. For example it's possible to make a system where object doesn't cast any shadows on all other objects. Probably it's possible to make a system where object doesn't cast a shadow on selected objects, maybe using some kind of layer system to determine the groups of objects receving or not receving the shadow casts. Indeed this feature is very much needed.

Of course! This is very much needed. And not only from Octane

RAin3D_, the free version will be available for more time, no worry

The color was wrong because of a bug with internal gamma usage. This issue and the website SSL certificate are both fixed, no warnings anymore, sorry for this
I will upload a bugfix next day.

RAin3D_, I hope within several months. That would be nice!

Thank you! Of course there is a huge list of improvements that we are going to make. Currently we are doing render speed optimization, hair and spline support. Next we will make material converter from some other renderers, add more post processing options, add more AOVs and masks for render images. We will also make object exclusion system for light sources and render images and so on

Have you seen that Cinema 4D selections work with non-Chinese symbols? This should be fixed in the next release quite soon.

Quote
RAin3D_ wrote: Kirgman, Is there a social software and an official communication place for this renderer?

There is a Facebook group https://www.facebook.com/groups/centileo
And Facebook page where we duplicate the news from the website https://www.facebook.com/centileo
In few steps later will launch the project on other social platfomrs too.

Quote
RAin3D_ wrote: Kirgman , I have sent the email to your account. Can you check and receive it?

Hi RAin3D_, thanks for file! I have already found the problem thanks to you. It was related to Chinese names of selection tags and materials texturetags referencing these selections by Chinese names. I will fix it quite soon, the mistake was small
At the moment you can rename you selections to some name in English characters or numbers to make it working

Thank you, looking forward for files to test the issue

Thank you very much text-tree for kind words! And welcome here!
I understand what you are asking for. Actually currently we have no any material/shaders converter from other renderers to CentiLeo and this creates a problem to get more users. Manual material conversion is a long and boring thing and so material creation from scratch is the way to go.
However, we plan to start developing material converter from C4D and Octane, Redshift, potentially the converter can be open-source.
We will start doing this after 0.66 version will be released. Still 2 versions to wait for

These light types are simply not yet supported. This will be fixed.
Currently only those types are supported: area with rectangle shape, spot, infinite, omni.
The omni has radius parameter in centileo light tag to make a sphere from it.
Infinite light has lighting angle parameter in centileo light tag to change the softness of shadows.

Additionally there are mesh lights in CentiLeo. You can make any geometry object of any complexity and assign CentiLeo Emission material to it. In node space you just connect Emission node to the Output node or you can use a mix combination of Emission and non-emission materials and connected to Output.
There is a cylinder light shape on you picture. Just use CentiLeo mesh light, they are very fast.

Quote
hu wrote: I found a solution, I opened the wrong option

Oh, thanks for finding it by yourself!
Honestly, I have forgotten about this option (send raw AOVs). This option is needed to get rid of any postprocessing from images, save them as HDRs (EXR) and continue processing them in other image processing application.

Hi ssjenforcer, it looks like you are doing smart experiments with shadow catcher!
Actually the cast from soldier shadow catcher plane behind him is a shadow. And it looks like the light source is emitting from the direction close to camera position.
To change this I suggest to add the second Sky object + CentiLeo Environment tag to the scene without HDR image file but just with a white color.
This second Sky object should be placed in the scene next to or as a child to the main Sky object. This second Sky object is placed as the override to Shadow Catcher / Matte of the first Sky object. The override settings are placed in CentiLeo Enviroment tags. The HDR file and direction of the first main Sky object may be not changed and lighting of objects (diffuse / reflection / sss, etc) will not be changed when Shadow Catcher / Matte slot is overrided by the second Sky. This matte ovveride will only affect the shadows casted to shadow catcher plane by the Sky.

Actually CentiLeo is currently constructed so that all scene objects and light sources influence on each other in a physically based way with a few overrides. Making the masks to exclude objects from camera view, making light source include/exclude lists and/or masks is thing that we need and of course it will be implemented into our engine too. Fortunatelly, this is not a very complex feature/