Hi and welcome here! Can you always reproduce this bug? What are your PC specs? What objects are there in the scene? Can you share a scene for tests with me? Either PM or to info@centileo.com

Hi there, this kind of artefact is well known as "shadow terminator". You can see it because there are very few polygons on the sphere. You can remove it with one of the 2 ways:
1) Increase the number of sphere polygons.
2) Increase the the "light shift" value in CentiLeo Material. This parameter is placed either in the Bump or Diffuse block of parameters.

Quote
Nobody wrote: Found out the material is ONLY editable in Node Space when creating it from C4D's top bar menu, not from the Material Manager window under Create Material > Extensions > Centileo. Node editor potentially crashes C4D when not in Node window setup

Node material is not created with "Create Material > Extensions > Centileo", you should use one of the ways described in my previous message

Quote
Nobody wrote: Hi. When i create a Centileo Material (mind you render settings are set to Centileo), it won't let me open it in the nodespace at all. Only materials that are in your example scene will open in it. Also yes there is "Nodes" in the upper right tab of C4D but then what?

Hi!
1) At first select CentiLeo node space or select CentiLeo in render settings
2) Create New Node Material using Ctrl+Alt+N or menu in material editor
3) Or Create New Node Material using top level C4D menu -> CentiLeo -> Material

Hello Any and welcome here! I hope to release the new version approximatelly in a month. There will be a lot of bugfixes, bloom, LUTs and AOV masks.
Please use at least auto-translated English input here

Normally it should render fast, but still some small tricky bugs may have some influence. I hope to fix it asap.

Hi Diego and welcome here! May I have a look into the scene? The settings could be different

Thanks for sharing! Btw you may add subtle color variation to the grass for more realism using Random + Gradient Ramp nodes

Thank you, I am ok, that was a small issue

Hi there! I still haven't looked because I was busy with the other bugfixes and currently I am in the hospital for a short time. I will get back to the issue next week

Hi rush.a and welcome to CentiLeo! Thanks for good words! I think the reason of difference is that in case of CentiLeo there is only Emission property, while in case of Octane there is Emission + Diffuse mix. Probably Octane Emission is implemented with some slight amount of diffuse property. Please try to combine Emission with Diffuse material using MixMaterial and see what happens.

Best regards,
Kirill

Thanks for sending me a scene. I will look there trying to fix the issue and get back to you.

Can you please share this scene with me? E.g. you can send a link to info@centileo.com As for scene I mean a setup with textures that always crashes and doing 7 minute first pixel loads.
Fortunatelly I have 1070GTX to test with. This GPU isn't small, it has very nice amount of memory and in our design CentiLeo shouldn't crash because of low VRAM. But we could get some logical programming bug that's doing a problem.

Thanks for wishes, Raphael!

Sure finding good or bad things from your detailed point of view would be very helpful. In the near future I plan to implement more features to make the engine more user friendly and will slightly postpone some hard-core render optimizations that I love very much . The approximate basic plan of work is here https://centileo.com/docs/index.php?COURSE_ID=3&LESSON_ID=40 Also need to make critical bugfixes, but there are not so much of them. My goal is to not overload the engine settings with a lot of purely technical parameters and rules that are very hard to explain to beginners. Ideally the parameters should be creative and respond for graphics look, but sometimes there is still an inevitable need to make some toggle "Importance Sampling" on/off and encourage a user for experiments.

The forum may accept drag&drop images right into the "Reply form" when you drag and move the images on top of it. Up to 10Mb or so per image. Once the images are loaded you may select a place in your message by mouse left button click and later click on one of uploaded image to place it to the selected point, e.g. within a table cell.
However we will probably need to upgrade the website engine because this one is quite old already.

Best regards,
Kirill

Hi DM50, the log is from Max, not from CentiLeo. Let me know about the scene parameters? It can be just a stupid proramming bug or in the other potential case this can be CPU RAM or Disc space overflow. For example, how much RAM / Disc space do you have? What's a GPU?

How many bitmap textures? Bitmap textures produce the texture caches and it can be possible they can occupy the disc.
7 minutes seems to be too high for the first pixel. It can be either thousands of texture files with cache generation or it can be some kind of 4 billion unique polygons with a GPU such as RTX 3080.
Please, tell me more about the structure of you scene, I am interested in the bug investigation.

CentiLeo 0.66: Interior
3ds Max plugin, 1200x1600, one RTX 3080, 2048 samples (32 iterations x64), 2:40min. Converted from Corona.

CentiLeo 0.65: Interior
Here is the interior render: 32M triangles, 15GB textures, the lighting from outside of room, 2 x RTX3080 10GB VRAM.
Rendering Performance: 2560x1440 image, 32 render iterations (2048 samples), the Motobike render kernel: 24M samples/second, 5:20min for the first image and 5:50 for the second, and then it’s denoised to kill the small residual noise. The Bulldozer kernel renders 32 iterations in 8 min, the noise is lower, but under denoiser it’s killed same way.

Hello Saihan and welcome to CentiLeo forum!
Thanks for sharing your nice picture with us! I am fan of Lego too, and now will go and play with my sons with their Lego 51515 Robot Inventor

I may recommend you to see the manual for Cinema 4D that describes our functionality. It's in English but there are the screenshots. And I will also publish the shaderball scene for c4d with some examples.

https://centileo.com/docs/index.php?COURSE_ID=3&CHAPTER_ID=069

Kirill

Hi Raphael! First of all thanks for bug report! Potentially fixing it can be useful even for using CentiLeo without combining with any other GPU engines.
The issue is with GPU initialization at the stage when we get the list of all available GPUs. I have some ideas about this and hope the experiments will help.

It would be certainly interesting to see results of your experiments with CentiLeo and get the feedback about the current amount of issues. There are some known issues such as dockable IPR window, a lovely feature of C4D. But there could be some other issues that need extra attention.

Don't know what to do with a forum message cutoff, maybe that was some rare accident that we can't reproduce with the tests.

Hello and welcome to our forum! Yes there will be a plugin for Blender, we like it very much. But it hard to say when we can do this