Thanks for scene! Downloading it now. I will get back once I test it

I want to help to fix the issue. Pls, can you send me a scene to info@centileo.com using some Google Drive or similar fileshare? There can be a stupid bug there

Hi Sang! Welcome here!! Is this the latest CentiLeo version? The latest package doesn't have the documentation you post here in a screenshot.
Also what is you GPU and what are your PC specs?
Can you send me this scene to info@centileo.com for investigation and debugging? It's likely to be a bug there because CentiLeo usually utilizes the GPU for 97-99%

You can use any kind of Cinema 4D object of any complexity and apply emission material to it using any number of textures. There is "Importance sampling" option there and it's better to enable it when the lighting effect is global for the scene, i.e. it illuminates quite a lot. Or disable this option when the illumination is local and not influencing other objects too much.

Yes, it's true finding. Actually this is very easy to do, but I was lazy in this part of work However it's possible to do all these shapes using any shape of regular object and applying an emissive material for it.

Quote
Ashrindy wrote: I have R23.008.

Ha-ha! That's good we found the issue! And thank you for patience
These small numbers of build version are hardly noticeable but can create the issues. Although I am quite surprised you have so low version. In fact R23.110 is one of the early official releases. You probably use some early build from Maxon beta program.

Ok, please, can you post your GPU and PC specs pls? And R23 build version?
After extraction problem is excluded now the reason it doesn't show up can be either wrong plugin folder or R23 build version lower than R23.110

The normal files structure is like here:

Code
pluginfolder/CentiLeoR23/CentiLeoR23.xdl64 pluginfolder/CentiLeoR23/library/centileo.dll pluginfolder/CentiLeoR23/library/centileo_ipr.dll pluginfolder/CentiLeoR23/res/ - a lot of files here

What was your archive extract program?

Ashrindy, pretty strange... Ok, can you screenshot the folder you have copied CentiLeo plugin to?
One thing I have in mind is that it could probably be extracted from the archive in a wrong way and violating the structure of plugin components. Have you used WinRAR to extract the downloaded archive or something else?

Hi Ashrindy, please make sure to follow instructions on https://centileo.com/download/
Especially:

Quote
If CentiLeo doesn't show after installation Update Cinema 4D build accordingly: R25.010+ S24.035+ R23.110+ S22.016+ and R21.115+ builds for latest Cinema versions. Make sure supported GPU drivers are installed: NVIDIA Game Ready Driver 441.87+ or NVIDIA Studio Driver 441.66+ from here

So the drivers should be up-to-date and R23 build version should be at least R23.110 or newer. Do you use Nvidia GPU?

RS references the vertex map tags from the nodes using the name strings. While we use tag ID in the same way as native C4D nodes that are used for Physical/Standard render

Yes, the enabled improtance sampling will certainly increase the render time but in many cases, especially when the light source shape is very complex geometry and it is has global lighting influence on the scene then it would generate much less noise but with more costly render iterations.

Hi thrimanakatha,
Nice cup, thanks for sharing! At first reading just a topic title I was thinking you wanted to report about the fireflies as part of render noise. But that's artistic thing.
Btw, have you done your light sources as mesh lights with emissive material or just with omni lights and spherical shape?
In case of real geometry + emissive material you may test on/off for importance sampling to get better speed. I think in this case it would be faster with importance sampling = off.

You should create and paint a vertex map tag in C4D for your object, then create a vertex map node in node material editor and assign it to any shader property you want.
This was discussed here https://centileo.com/forum/forum19/724-what-is-cid-tag-for-centileo_-it-does-not-seem-to-attach-to-o....

In vertex map node you only determine the tag ID, and then you assign all this material to one or more objects and for each object the speficied vertex map tag will be used if the tag is available.

Redshift uses the names of tags to link them, but CentiLeo and native Cinema 4D nodes use tag id from left to right. Thats all the difference

Vertex map has various usage. E.g. Realflow generates them for deformation motion blur as I described before.
You can also draw a vertex map for your object. And a tag will appear in the list of object tags.
You may draw several vertex maps and they will generate Vertex Map tag 0, Vertex Map tag 1, ... Vertex Map tag N, from left to right in the tag list of the object.

If you want to get vertex map values for your shaders you should just use the vertex map node and connect it to the field you like, for example to determine reflection color properties or material amount in the mix material. In the vertex map node you only choose the vertex map tag ID.

Same story with vertex color tag!

As for mograph tag then it's automatically created for Mograph objects, e.g. for Cloner with multi-instancing, for mograph matrix, etc. You only need to know how to manage the mograph to generate UVW and Color data inside this mograph tag. In CentiLeo this mograph info can be accessed using mograph info node.

I want to fix the issue in the new coming release, this shouldn't work like that. It can be either an internal ray epsilon computation failure. Or it can be related to smooth normals that we have per vertex because when we increase subdivision and smoothness the stupid artifact goes away. Funny thing, but I hope to fix that soon

Quote
ron134 wrote: can you show me some pics for reference i am kinda lost

I hope these few pages may show some idea how shader nodes can be used:
https://centileo.com/news/149/centileo-for-cinema-0614/
https://centileo.com/news/145/centileo-for-cinema4d-0610/
https://centileo.com/news/127/centileo-for-cinema4d-0590/

You can drag&drop your images from windows explorer to node editor and CentiLeo bitmap will be auto-created. By default it uses texture projection determined by TextureTag of the object where material is assigned. However you can change it using uvwProjection node where you can either use a procedural texture mapping coordinates or reference one of UVW Tags that are assigned to your object.

Sure, we need to write a manual for shaders of CentiLeo because there are a lot of nice things that can be done. Also during shader writting I tried to follow the similar practice as native Cinema 4D nodes, so they can be somehow similar.
Do you want me to share a shader ball scene with some materials?

ssjenforcer, thanks for help to new user!

CID is an invisible tag that stores the unique ID of the scene object to leverage it in interactive rendering together with motion blur and optimize some dynamic object changes during edit.
This tag is automatically created for each object if you use CentiLeo. If you uninstall the plugin you will see these tags for all scene objects. And it's also visible in the list of options of tags - but this is a design of Cinema itself, not possible to remove it from that list.

This link shows how to use the vertex color tag: https://centileo.com/news/145/centileo-for-cinema4d-0610/ (see the bottom most picture)
While the vertex map tag can be used in a similar way. It's just a drawing on the surface of the object which stores the values in the vertex map tag. And the shader node for vertex map just gives you access to these values. You can reference up to 10 tags (and more in the new versions) that can be attached per object where tag id = 0 in the node reference the most left vertex map tag and so on.

Sometimes other plugins like Realflow use vertex maps to generate velocity values of deforming object. And these vertex map tags can be used by CentiLeo object tag to use deformation motion blur as described in this short example https://centileo.com/news/150/centileo-for-cinema-0615/