Please, can you share this file with me so I will try to play with settings? Probably we need to crank Softness/Sensitivity/Power to max values and also increase the the Distance Scale a lot. And then we probably have more control using the Gradient.

Thank you Rei and welcome here!

The shadow cast/receive options will be available in commercial release. I still need to do 0.70 before that.

As for matte it's available as "Shadow catcher" toggle in Diffuse rollout of material. You can see the idea how to setup it here
https://centileo.com/docs/index.php?COURSE_ID=3&LESSON_ID=64&LESSON_PATH=17.64
In 3ds Max it's quite the same, but the manual for Max should be created certainly.

As for Visibility options for object I will add this in the upcoming 0.69 release. And also will add RaySwitch material and map

Hi, yet!
The Curvature node depends on ray tracing sampling around the hit point. The parameter Softness has influence on whether you can modify the output of the Curvature using the Color Correction or Gradient. Please see example here
https://centileo.com/docs/index.php?COURSE_ID=3&LESSON_ID=105&LESSON_PATH=17.69.105

Heh, it looks like the preview of material in material browser itself doesn't work. But material from the assets do work when they are assigned to the objects and their previews in object editor also work.
Need to fix that previews to avoid this confusion.

Quote
BruceML wrote: Would be great to see turbulence option in the gradient like default c4d gradient

This is available now:
1) You may connect the Pattern node to the Gradient.InputMap. In the Pattern node you select the Linear U or V pattern.
2) Then you connect the UVWTransform or UVWProjection to the Pattern.InputUVW.
3) And then you may connect Noise (Turbulence) to UVWTransform.Offset.
And there are also many other connectable ports in the UVW nodes that can be applied to the Pattern or something else.

Also pay attention to the horizontal lines on the nodes, they can be used to optimize the representation of the node in the editor. Also it's possible to create own custom nodes using the groups which have input and output ports that you determine with some custom functionality inside.

Just make this small non-default change: https://centileo.com/docs/index.php?COURSE_ID=3&LESSON_ID=57&LESSON_PATH=17.57

This happens because by default we generate the cache .cntx files with bitmaps. And asset bitmaps from library are virtual and have specific address. So we need to redirect our cache files to the known folder to make this working.
This was done to optimize second launches of the project without bitmap read and parsing. Later we will make the options to store this just in RAM (and reload every time) and will compress the caches.

And you may look at the settings description here
https://centileo.com/docs/index.php?COURSE_ID=3&LESSON_ID=105&LESSON_PATH=17.69.105

Quote
BruceML wrote: Is it possible to view textures in viewport when using node material. At the moment they are all default white

The viewport materials are not with textures by default just for Vram and computation optimization purpose.
But you can enable viewport textures with 2 methods:
1) Connect any texture of the node editor to the Output Viewport Color port. And it will work constantly on viewport until you mute it. But this connected node will be for Viewport, not for Interactive preview render.
2) You can switch Solo Mode on any node in node editor (including materials or unconnected nodes) and show the texture both on Viewport and Interactive Preview render.

Quote
BruceML wrote: Okay, will stay in nodes. prefer it. If i need to send an image for reference in future, how do i do it here on the forum. The image button opens a dialog box for "image source", I tried pointing to the image on my drive and did not work.

You just drag & drop the image from computer to the field under this topic Reply form. There is the link Upload files and just drag & drop the image over this area. Here is an example upload

Quote
BruceML wrote: Hi Kirgman Thanks for the welcome. Okay cool. Can you help with colour space issue with normal mayerial and node material. Same project, colour swatches in different colour spaces. You will see the hex is the same #E68B2A

Just don't use old materials. Switch to node materials, they are fully up to date and a way to go. The old materials will be likely removed to avoid confusion. But to make the life as "drag & drop" we will also make the presets for materials to select and tune the most common node materials in an immediate click.

The color space is srgb. The difference you have seen is that Maxon did different solutions before and now for color selection.

Quote
BruceML wrote: Hi, When will we see a dirt node in the node editor? Like in the centileo material

Hi Bruce and welcome! Now this is called Curvature node in the node editor

I have found the internal message from Maxon to developers, so indeed there was an issue with the Nodes for 3rd party plugins on that intermediate builds. That was fixed in 2024.4 or maybe in even in 2024.3.2. That was just month ago

As far as I see 2024.4 doesn't add problems and it works just fine with the plugins compiled for the earliest version of the season 2024.0 as in our case. It also has the new nice particles system.

Hi garrido! Is CentiLeo working? I mean what if you open Interactive preview render, does it launch? If no what's your GPU?

If the problem is only with adding the nodes only please make sure that you have correctly copied CentiLeo plugin to the folder:

Quote
Extract downloaded archive To install CentiLeo for Cinema 2024 you should copy CentiLeo2024 folder from downloaded archive to the plugins folder of Cinema 4D, e.g. to “C:/Program Files/Maxon Cinema 4D 2024/plugins/”

The best working extraction program that preserves the folder structure is WinRAR.

How your plugins/CentiLeo2024 folder looks like?
The nodes are described in plugins/CentiLeo2024/res/nodes/ subfolder, there should be 3 .json files there.
Please, let me know how it goes.

ALSO Your current Cinema build version is not the newest, I heard there was some binary incompatibility introduced by Maxon in 2024.2 or 2024.3. As far as I remember this was fixed in Cinema 2024.4. Also 2024.0 works fine. So please upgrade and test 2024.4 and tell me if that works

Hi Joao, and welcome here! Video bitmap is not yet supported, but will be fixed in the near future

Thanks for reminder about Laubwerk Plants! I will look at this after the next upcoming release

Hi LU! I will add volumetrics not to the next release, but during some commercial release

Thanks for suggestions!
However, Cinema 4D has some standard layouts. I can't remove the top line with "Menu". I can remove menu itself, but the top line will be there. Also I can't move it to the right. It's only possible to move the icons to the right of menu and this will look strange. Also it's possible to replace the icons with text and move them to the top line and it looks not cool.
In the future more other items will be added to the top line similar to Octane live viewer but with our options.

Please, can you post a screenshot of your interface how IPR menu icons correspond to the rest layout?
The icon size is adaptive and I have made them the same as in the Cinema itself and tested on various monitors.
As for Menu moving it's not possible, it's a default panel and I will add more options to this panel for materials and other items adding. I can move the icons to this top panel, probably loosing the icons and making them as text.

Hi LU! We have own node materials & shaders in CentiLeo, it has a lot of settings and similar functionality. And there will be a converter to CentiLeo materials

As far as I know you use the old Iray from years ago. But it was redirected to the Omniverse product of Nvidia and as an offline quality engine co-exists with real-time path tracers there.

Many aspects of realism come from tone mapping. It can't be underestimated. For example if in CentiLeo you add Aces tonemapping, then LUT and then some bit of Bloom and some contrast tuning and you get very big difference.