Ali, I can't believe that it coinsides everywhere just every highglight here and there is the same, every shadow detail is the same.
How you did it? It's amazing! Thank you very much!

I guess it was not easy to convert Vrays' glossyness to our roughness. We never talked to Vray about what formulas they use for glossyness, we never tried to reproduce their exact look.

More experiments with SSS on the face of the man

Attach "shadow catcher" shader to the diffuse color of centileo material. May attach not to diffuse color but to some reflection color

Hi Ali! It looks very well I think. I mean the rendered image. Will take it for tomorrow's workshop

I think that compared to Vray we have colder post-production tone. And it seems there can be some play with reflection weight of the wood that is close to the camera.
But in general if it is a result of automatic conversion with just very slight tuning it's very cool!

As for animation we have made a bug in one of the recent developments... Need to fix it ASAP.

Ok, will add it. Right now it is in cntlColorCorrect node

Quote
Rodrigo Bitencourt Rodrigues wrote: Feedback: Centileo Camera on the menu: When you click it should create the camera assuming the position and rotation based on the editors camera, just like the c4d camera button works. question: Centileo is ready for animation?

Right, should have done it this way. Will fix.

As for animation - yes, why not. It should work. I have tested now and after 4-th frame it shows Cinema 4D message unable to write file. Need to look what is going on. Myabe haven't activated something in just C4D maybe some bug.

Quote
Aimar NL_21 wrote: more and more reset with lost version ( cntlc4d 0.453 ) . again, I'm not sure what is wrong .

Please, can you describe that problem that you have? IPR is reseted (restarted) rarely when you click something? I will try to fix it by next version.

Quote
Alex Comtur wrote: As will be realized caustic, though reflection?

Hi Alex and welcome to our forum! Yes, it is in our plans (but not very soon).

Have you used some slight bump maps to emphasize the details of the textures? I like the last image a lot, thank you Ali!

Thanks Daniel! As soon as you are subscribed to this topic just see the demo of 0.45 http://centileo.com/forum/forum23/96-centileo-045-features-demo
Same is available in version for Cinema. And join our Facebook group https://www.facebook.com/groups/centileo/ - it has nice notification capabilities.

I have seen your amazing works! They are so cool. I am just not skilled enough for your level. It will be very cool if you share your experience, guide us a little bit and share your thoughts on current CentiLeo status. And just demand from us as much as you want

And some still image. I tried to make SSS skin for this scanned man.

Hello everyone,

We made some small demo about what happened for 0.45 version. It's available for Cinema 4D and 3ds Max.
Quick note: my artistic taste maybe not nice but the goal was to demonstrate the features Kirill is a pro-gram-mer!


Copy-paste video description from Youtube page:

This is the demo of CentiLeo Renderer new features 0.45 alpha update (features available for 3ds Max and Cinema 4D plugin both with interactive IPR). It supports fast rendering with many light sources and real-time adjustment of AOVs that are summed into the Beauty image. Inside "Blend Beauty pass" you can manipulate reflections, diffuse transmission, environment.
Inside "Blend Light pass" you an manipulate the light sources united into the groups called "passes". Each light pass is assigned in the special property of the light source.
Btw, take a look at how many creative look controls we have for the light source.
Also you may notice that the scene size is 8 GB (3GB geometry and 5GB textures) and it works very quickly on the single GTX 970 computing 15 AOVs in parallel (their resoltion doesn't matter, images are stored on CPU RAM during computation).

Kirill

Super! Thank you!

Quote
Rodrigo Bitencourt Rodrigues wrote: Feedback: I think the ipr size should be the same as the final output with a percentage control. You can have 1920x1280 at the final render and preview it at 100% or 30% (640x426) of the size at ipr the ipr size on centileo render tab is not handy.

Rodrigo, it can be fair. However we currently have built an autonomus IPR mode where it is possible to avoid production render in Picture Viewer at least when animation is not yet there. There is a special Save button in IPR window and everything can be exported.

Ideally this IPR tab settings should go to IPR window UI but we currently have some problems writting interfaces in wxWidgets because we need custom controls and custom styles. It just simply needs more reading of their API, digging and etc.

There should be options to lock the aspect ratio with main resoltion. There will be also the mode to fit render resolution to the IPR window size.

I am interested whether you still have bugs/crashes when manipulating material layers? After 0.453 some complains from other people have changed to positive.

Anton Bessonov doesn't need special representation, he is really great 3D artist with the highest demands.
His page https://www.behance.net/Bessonovart

Here are a couple of his WIP tests on detailed car model.
The first one was done in one of the earliest CentiLeo. The last picture was done with 0.452 for Max (1 minute for 2000x2000) on one GTX Titan straight out of the raw render.
So, he tried to make carpaint (see second picture) with some image of normal map flakes. I think we should make some procedural flakes shader for such tasks

Wow! Very nice except of the window HDR What is the resolution of textures?

Hi Ali, thanks for your tests! Posting a video with express test too:

If you make this trick https://www.youtube.com/watch?v=WQ3vNXF5vg4 but in CentiLeo for Cinema then our renderer may perform 2x faster.

For example GTX970 works well when it is inited with GPU (geo+tex) cache less than 2GB. Then restart IPR closing and openning the IPR window again. And then while IPR is running you can up you caches more than 2GB: go to Hardware Settings, up the caches like you want and click "Apply". And it will have both good speed and larger caches which may be better for large scenes.

Sometimes GUI lags are possible when you render on the GPU which is also attached to your display. This happens because one GPU is shared among OS programs, Cinema viewport and CentiLeo.

But this trick may help eliminate these lags and run smooth even if you have one only GPU.

This thing has relation to CentiLeo's out-of-core feature and NVIDIA CUDA drivers which also compete for memory.
When we will work on multi-GPU feature we are going to make this process automatic so that you will have no headache with such tricks irrelevant to creativity. This is our aim!

PS: One more recommendation is to render on one or more GPUs that are not attached to display. And leave "display" GPU to the OS and viewport, it can be just some basic small GPU.

Change Log: cntlc4d 0.453 alpha (2016 Dec 1)

[C4D plugin] Fixed non-working camera tag.
[C4D plugin] Fixed a couple of negligible bugs.
[C4D plugin] Reduced the frequency of IPR scene/camera update detector.
[C4D plugin] At the moment the camera doesn’t update during motion, only after mouse button is up. After testing will return back the updater during motion
[C4D plugin] Added a setting “IPR refresh time[ms]” in RenderSettings->IPR menu which is 100ms by default and it controls how often CentiLeo checks for updates of the scene.

Download here: http://centileo.com/forum/messages/forum18/message357/91-download-link-centileo-for-cinema-4d-v0452-...

It seems that problem is with us. Need to detect it. Does it crash Cinema? Does it overload the CPU? Can you please from the start switch off "update scene" which auto-updates it and see what happens?