Hi Joao, and welcome here! Video bitmap is not yet supported, but will be fixed in the near future

Thanks for reminder about Laubwerk Plants! I will look at this after the next upcoming release

Hi LU! I will add volumetrics not to the next release, but during some commercial release

Thanks for suggestions!
However, Cinema 4D has some standard layouts. I can't remove the top line with "Menu". I can remove menu itself, but the top line will be there. Also I can't move it to the right. It's only possible to move the icons to the right of menu and this will look strange. Also it's possible to replace the icons with text and move them to the top line and it looks not cool.
In the future more other items will be added to the top line similar to Octane live viewer but with our options.

Please, can you post a screenshot of your interface how IPR menu icons correspond to the rest layout?
The icon size is adaptive and I have made them the same as in the Cinema itself and tested on various monitors.
As for Menu moving it's not possible, it's a default panel and I will add more options to this panel for materials and other items adding. I can move the icons to this top panel, probably loosing the icons and making them as text.

Hi LU! We have own node materials & shaders in CentiLeo, it has a lot of settings and similar functionality. And there will be a converter to CentiLeo materials

As far as I know you use the old Iray from years ago. But it was redirected to the Omniverse product of Nvidia and as an offline quality engine co-exists with real-time path tracers there.

Many aspects of realism come from tone mapping. It can't be underestimated. For example if in CentiLeo you add Aces tonemapping, then LUT and then some bit of Bloom and some contrast tuning and you get very big difference.

Hi, this is usually about post render settings of contrast, LUT, tonemapping and things like that. The RAW image output is practically the same if we talk about the same material models, however they may differ a little bit too sometimes.
Sometimes the softness shadows of the HDR Image may differ because different renderers may use differerent internal thresholds to get HDR lighting. Here the gamma and multiplier settings may change the look.

Is Iray itself still alive? It was transformed into Omniverse in Nvidia.

Thanks for report and a scene, I will look there asap

The last Forester update is September 2023 https://www.3dquakers.com/#section-news
But it's probably update for the new Cinema.
As for Chaos Scatter we should access their SDK and contact Chaos, and see whether they have intention to share.

However, we also plan to have some own similar Scatter in the future, and some other procedural objects and libraries.

Thank you for wishes! Happy holidays to you too!

Btw the issue in the topic start was fixed. But the one with .EXR reader in 2023/2024 Cinema is not because it's Maxon bug I will probably use a different library for texture reading or consult with them

Hi! I have postponed the material converter during 0.68 due to some complex things. But I will add a material converter for several engines at 0.70 release

Hi and very big thanks for report and a scene file! Is you HDRI texture a HDR or EXR file? Cinema 2023 or 2024?
I have found Cinema 23 and 24 crashes itself when we add a bitmap with EXR. It's not the case with older Cinema. And it's a bug in Cinema code as I currently figured out. But will also look into your scene, thanks for this!

Thank you for bugrep, I have fixed this already and the bugfix will be released together with the upcomng release, still need to wait some time

Hi Junky! And welcome here! Thanks for bugrep! I have fixed this bug already just few days ago. And I will upload the update once I finish preparing 0.68 release with new features. It's expected within 2 weeks.

Quote
junky-junky wrote: Then I close the IPR window and open it again and this strange pattern covers image. After closing the window, Cinema crashes.

That's the key. The issue is with Nvidia OptiX denoiser that we use. There was no any problem before driver update (I used some 1 year old driver). But the issue appeared with fresh drivers. On the software side it was possible to fix the issue and it no longer appears on the future CentiLeo.

For now you may even turn Denoiser value to zero and the glitch will dissappear.
In my case it was enough to restart Cinema to get back for correct behavior. And also don't open-close the Interactive Preview window, just keep it always opened.

I will upload the fix together with other new features very soon.

Best regards,
Kirill

I see, you wanted to distinguish the individual elements of the Voronoi Fracture. At the moment the Random node assigns just random numbers per object or per mesh element (disconnected from other mesh elements), these random numbers don't follow any rules, but are separately generated randoms. Only the attribute nodes like MoGraph Node or Vertex Map/Color nodes can help here

They will be available since 0.69. It's quite soon, however I also want to compress the texture caches for this.
0.68 with native hair and splines is approaching btw

Hi Walter, what if you map the Noise Node with Voronoi settings to the Alpha channel of Material?

Then I need a scene with ForestPack to try to investigate your error. A lot of things were fixed, but probably something was missing.
info@centileo.com my email or PM here