Hi Ds! Well... I was very nervous about this thread I also thought you are trolling me 21 minutes for 1 very simple scene on a very-very good GPU!
13 sec is ok and it will be less in the near future within several monts so stay tuned. Ask any questions you want, I love C4D and working on this integration with huge enthusiasm!
21 min looks too much anyway also for 1920x1080 at 1 iteration. It should be seconds! Really! I am not joking Can you give me a full scene please for my tests? To I will probably also give you a debug version with some more detailed info.
Yes, whatching videos, serfing web Chrome is ok while doing GPU render. They don't make problems in my practice.
The screenshot looks fine! The speed indicator "SPS" (samples per second) is ok.
You just need to reduce the amount of Render Max Iterations. It computes 32x64=2048 samples per pixel while it's ready at 1 iter (64 samples per pixel). You don't need default 32 iterations: see CentiLeo Render settings.
Can you please show the screenshot of the first scene (not a sphere) as an example of reasonable scene with 1 iteration?
Wow, this looks very wrong. Please, help me to investigate wha'ts going not the right way.
I would like to see the screenshots from IPR like here
At the botoom of IPR there is a bar "GPU Indicators". It's enabled with mouse right click and selecting "Show GPU info" in menu. To understand what's every number meaning see here
How many textures are there in the scene? And what's the interface of GPU connection to Motheboard? PCI-Express direct connection or through the riser? I don't think the out-of-core textures should behave like this. There were so many tests with far bigger scenes on smaller harware with great performance.
Another potential reason: what drivers have you installed? Latest ones? How many other GPU programs are working at the same time? Any Mining, Octane, Redshift for e.g.?
Hi Ds! Welcome here! Ron is right, thanks, you should update to Cinema R23.110 or higher build version. It done using Cinema GUI automatically and for free. This update will also reduce the bugs of Cinema itself!
This is mentioned on the in a section titled "If CentiLeo doesn't show after installation".
CentiLeo Chat:
Non Rendering Displacement, Displacement mapping not rendering in C4d Picture Viewer on all objects
Hi Ron! It looks like a bug, please can you send me an example scene to ?
One of displacement limitations is that when it's applied to particles such as XParticles it doesn't displace, right now the objects scattered by Cinema\s Cloner are treated same as particles so no displacement too.
Thanks for recommendations! Your friend may freely ask any questions here on FB group
Btw, CentiLeo can work on old hardware, but actually I would note there are .
They are not very hard, but e.g. 2GB GPUs are still circulating and I know CentiLeo may work on them, however there are more risks for instability. Also on smaller GPUs performance is clamped not only by GPU compute power but also a little bit by complex CentiLeo architecture that was primarilly designed for slightly larger resources to deliver very good things at larger scale. Also Nvidia and Microsoft push application developers to go for more advanced features, GPUs, etc and sometimes this forces us to think less about older hardware
Btw, while you have R23 and there are nodes there! If you select CentiLeo node space then using uvwTransform node has bigger functionality than Texture tag and it recreates the functionality of native Cinema texture tag's scale/tile/offset/repeats params but it's more powerfull because it can be done per node or used as main projection method for all material textures.
uvwTransform can do the same things as native Texture tag for the same projection if you select defaul texture tag projection in uvwTransform.
On top of that there is easy possibility to use it as mask for node Material mixing. There you can use simple material mix (2 materials) or layered 10 material mixer and combine them as much as you want. To make a mask for these material blends from uvwTransform (with limited repeats) you may apply uvwTransform to just the whole white bitmap or bitmap with some own mask to get complex mask shape.
Hi Ron! Thanks for tests and your opinion!
Using selections for decals is another way that I have just forgot to mention. Yes, it has a problem that it repeats mapped materials everywhere. In the past I made a feature where it was possible to stop repetitions but have removed this for some reason. Actually, I need to analyze things again Since Cinema R20 a lot more mappings inside material are allowed, not just a mapping enabled in texture tag for the whole material. So basically we can map the most of the textures of material using texture tag default projection and some textures (3D noise or scratches or whatever) can be mapped with different mappings using uvwProjection/uvwTransform. Basically, I also need to learn the best user practices of decal/label placement and probably make some boxes that can be shifted across the surfaces.
Why do you left the images noisy with few iterations?
CentiLeo Chat:
Animation Test, An animation an old scene with new renderer
Hi Ron! Thanks for the very good test! I think the wheel shrinks during the motion because of the lack of motion blur keys. Just go to CentiLeo Render settings -> Camera Tab and there you will see motion blur transformation steps. By default it's 2. Just set it to a higher number, say 10-20. The maximum is 32. I hope this should help.
Hi Ron! Very cool images! Small fixes can be done, but they are already in a good shape.
Cinema R21 has Intel Denoiser, CentiLeo uses it from R21 and this small remaining noise can be killed completely.
Btw emissive lights of CentiLeo are very fast. However right now for Cloner and X-Particles objects they are not improtance sampled (and can be slow) - will fix this later.
Quote
Ron Walker wrote:
What I would like to know is how to use the various addition shaders Centileo offers as there are no explanations I can find on the site.
I tried to make them intuitive, but still has to write Manual pages about the shaders. And I would also recommend to use node-based materials that is enabled for R21-R23, they are visually more intuitive with inter-node connections.
Quote
Ron Walker wrote:
Also is there any kind of Volumetric Environment/Atmosphere available?
Not available at the moment. To be done in the future.
Best regards,
Kirill
CentiLeo Chat:
Sunbeam Tiger, Quick render using an old model with new renderer
Hi Ron! Very nice renders! Btw, it will be fast even if the car headlights are made not from bitmaps but from real glass, bulbs, etc (with a lot of refractive geometry). CentiLeo is fast for such materials.
As for decals
They are possible to do, but the problem is that things are not visual.
Look at the screen and the scene file
There decal is done using the layer shader where the base layer is metal and on top of that there is a bitmap with centileo logo (1) and there is a white bitmap mask (2). Both (1) and (2) are connected to uvwTransform node. This node has "scale" parameter which makes mapped textures smaller for smaller scale. And there is "decal" flag that stops mapping for out of [0..1] range of UVs. This example operates in mesh explicit UV channel the one we create in UVW tag. That's why there are few decals because the UV space 0..1 regions appear several times. But we can also map in XYZ local space to object where material was assigned. To do this a uvwProjection node should be connected to uvwTransform and therein a "XYZ" mode should be choosen. Then with IPR help you can find good offsets to place decal on a surface. Bad that the real decal box is not visible. Will work on this part in the future and will learn other workflow experiences.
Ron Walker wrote:
Finally could you direct me to some tutorials for Shadow Mapping and an up to date manual for the cinema version. This to me seems to be the one thing missing - tutorials.
Hi Ron!
(hdrs are from )
This sample shaderball has:
1) shadow matte material example, where the light sources (hdr light and 1 rectangle light) have shadow catcher weights in their centileo light tags. These shadow catcher weights determine the amount of shadow this light casts on the shadow matte material pn the ground plane.
2) Additionally the other hdr (a hdr for camera) has only one non-zero channel and it's for camera. When this hdr with non-zero channels appears first in the cinema object tree then it's non-zero channels override other hdrs below this hdr in the object tree. In this case a non-zero camera channel of the top hdr overrides camera channel of hdr below. But the hdr bellow has diffuse, reflection and other channels that are not overrided and they illuminate scene materials but have no effect for camera. Also you may toggle Alpha output or Transparent output channels in AOV tab of render settings to export respective shadow only images.
3) If you have R21-R23 then you can see in this scene a node material setup for metal material with colored flakes. Very simple to do and handy for car renders.
As for Manual/Tutorials. They are started here: They have basic technical info + xparticles setup.
Actually it is a problem there are no docs for mateials / shaders although there are similarities to other renderers. At the moment I must accelerate CentiLeo with RTX and after that I can continue writting manual about materials and make a couple of presentations. More speed is needed because there are problems compared to others in many exterior scenes with not very complex lighting where other engines have RTX. While CentiLeo is currently very good for complex situations like out-of-core geometry, complex GI lighting in interiors or night shots or mesh lights or many lights.
Prices They are to be determined yet. But actually need to reach 0.7 release. The prices will be similar to competitive products of similar features. Probably lower at the beginning when things are too sensitive.
Texture Fade away bug This is a bug. The textures for some untested reason compete for their place in cache and one texture looses just everything. I have already seen this for extremelly low cache sizes in other much larger scene in 3ds Max and planned to fix it in some later future. But your caches are great with 700Mb on GPU and 4000Mb on CPU. It shouldn't act like this. So I will need to fix it in the most close release. Please, can you send me your scene in email or PM. With Cinema 4D quick launches I will be able to fix it faster.
Hi Alex, and welcome here!
Have you checked the flag "Is Normal Map" inside CentiLeo bitmap? This flag is at bottom of Bitmap. There are also other Normal Map flags to swap the channels.
Connect it to Bump slot of CentiLeo material. Btw unlike Cinema you can mix Normal Maps and b/w Bump Maps in arbitrary way because internally they are all converted to b/w bump map for manipulations.
Hi Ron! Thanks for reporting the issue!
A lot of bitmaps and large bitmaps should be supported given some resonable GPU/CPU texture caches. Reasonable is something like 512MB for GPU / 4GB for CPU.
It's a bug, maybe I did it just recently. Please, help me fix it. Can you show the screenshot from IPR GPU Indicators like a panel at the bottom of the IPR? See example:
To open the panel you should right-click in IPR and enable "Toggle GPU Info".
What numbers are there for texture caches? A screen could be ok. And how many bitmaps are there in the scene? What is the resolution of HDR if it's used?
AntonioDi wrote:
А поддержки volume light в этом билде еще нет ?
Hi Anton! Welcome here! No, there are no any volumetrics here. Currently concentrated on particles, attributes and render speed. Will publish TyFlow direct support in few days.
I also thought you are trolling me