Hi 3Deoskill and welcome here! Please, can you drop a video screencast that shows evidently how it freezes the Cinema 4D? The minimal scene project file may help too. Also it would be interesting to know your PC specs.

Does it freeze forever or stops being frozen after some time?
As for IPR and PV they don't work simultaneously. The PV has more priority, so we pause the IPR, then PV makes it job and after that the IPR launch from scratch reloading the scene.

Threading... CentiLeo and it's plugin is very multi-threaded. But it was bugfixed a lot, and I don't know for myself any significant operational issues. I also have R23 version still available and can launch projects from there.

Quote
Caetano3Dsigner wrote: Yes, the plugin is in the correct folder (the path is ok). But nothing apear in the node editor.

Please check how to install it correctly, I have recorded the steps on the Youtube video, make sure you don't miss something :
https://youtu.be/5CSpHjMrBKI

Also you may try to refresh the cache of nodes and other cached Cinema 4D items. Just remove the preferences folder, see the link below. This cache will be recreated on the next Cinema 4D launch, you will need to re-login with your account password when Cinema 4D will request for.

Quote
Caetano3Dsigner wrote: My Node editor does not show the presets. I click on the + tab and type color or some other preset, but nothing appears. My version is the latest and I use C4D 2023. It only says "No results found". The firewall is ok. Nothing blocked. What happens?

In the node editor menu you have to see the following picture:


Also make sure you have these files in the plugins folder, see the path in address bar.


Shortly the plugin should be correctly unpacked, the WinRAR archivator software is a good option for this.

Hi Giorgio, it's more advanced with bugfixes on the way - 0.698 on Download page. See the direct link https://centileo.com/~downloadC4D069

Quote
Eric Chen wrote: Preview; yours has 2 balls, mine only shows 1 ball

It can be different version of Cinema 4D. The image from your part is 2025, and the one in the Manual is 2023 or 24

Where is the difference? The language?

Hi Eric, but what do you want to do with this preview? What's the question?

Hi Eric and welcome here!
The displacement node is in the list of all nodes under the category Material Generator:


Also don't forget to setup CentiLeo Object Tag with enabled Displacement mapping option for your object:
https://centileo.com/docs/index.php?COURSE_ID=3&LESSON_ID=61&LESSON_PATH=17.61

Hi Giorgio, welcome here and thank you! Sure there are huge plans to make a version for Houdini. This will be the right host app for CentiLeo!

It was very interesting to investigate for the issue in the engine.

And I also hope the old good competition between Juve and Inter will rise again! Competition is always more interesting than one beating another one with a huge advantage.

jiv21, hi! I have fixed the slowdown, now the new version is even slightly faster on your scene.

The issue was in the fact that you configured the stadium scenes with many collections of Mograph multi-instances. In 0.68 they were built as a single union collection. In earlier 0.69 they were built separately because of new shader flexibility. Now the flexibility and performance considerations are combined efficiently.
Thanks to your bugreport the renderer has become even better! Thank you very much!

Btw, this is Juventus stadium. But I want to say Forza Inter! I am fan of Inter for 26 years already.

jiv21, thanks for scene! I see that in this scene the new version is slower than in older version. Already investigating for the reasons! Bug testing is very important!
I guarantee you that scene will not be shared for public.

I have all Cinema versions including those you have mention.
The good email is info@centileo.com I will benchmark it. It's good the difference is 2x in this case

Quote
jiv21 wrote: I usually use normal maps. I do not usually use relief maps and on rare occasions displacement maps. As soon as I have some time available I will send you a scene.

Hi Jiv21, I have tested the scene with heavy use of normal maps and get the adequate slowdown of 5% compared to 0.68 because of more correct precise computation of bump map and normal map. So now we need to explore the scene itself that reports this. There are some extra candidate idea but need to check it using your resource.

Ok, for the moment the first candidate on this problem is normal map which has become more expensive. Will test it once get a resource from you. Thank you for reporting an issue!

jiv21, btw, do you use Bump maps or Normals maps connected to CentiLeo material? And what type exactly?
This can be the reason because I have fixed the issue of using the bump map with gradient node. And this makes the bump map more expensive and also do the same for normal maps whic could be avoided if we split them to different ports.

But anyway working with a scene itself helps better because we may open internal performance counters for every little aspect of the system and compare with the previous version.

Thank you! Btw before I upload the fix with artifact to fix it at the moment: either switch off the bloom or make resolution a multiple of 128.
Your scenes are similar - they are stadiums. Nothing was changed internally with geometry handling. But probably something is wrong on my side with multi-thread waiting that was minimized (that's internal thing not for user thinking).

Currently I have run several 5K-10K renders on 0.68 and 0.69 with one or two RTX3080. And the older 0.68 is not always faster. But thats the render of the car interior and spherical camera. The usual difference is 2%.
Will continue some other benches.

Also what's your render Iteration Size and number of render Iterations?

I have fixed the bug with right side artefact on highres image (over 4096) just 10 minutes ago and now compiling an update with the fix.

As for the speed loss then nothing special was done that could influence the speed. Just more shaders were added that don't influence on performance in my tests.
The issue can be some tricky small thing that was done in some internal configurations that resulted in some issues for your particular scene.
Just anything could make influence.

Can you please collect some minimal scene maybe without your production staff that reproduces the issue? In that case I can investigate and fix very quickly. I can sign the NDA and guarantee no any leaks.

Hi Jiv21! Did you lost performance in 0.69 compared to 0.68? Can you compare them side by side? Have you tested the very-very last version of 0.69 that was updated a week ago?
What kind of scenes did you test? Maybe some very
In my comparisons 0.69 and 0.68 are almost equal, with just small difference.

Quote
zhajiangmian wrote: Great, this renderer is so powerful and has high controllability

Thank you! Working to do a lot more!