Octane 2026.3 for Cinema4D - v1.9.1

[ChrisHekman]

This was an oversight. I'll see if we can fix this.

Aah, perfect, thank you! : )

One more thing I noticed when rendering an existing scene from 1.9.0 in 1.9.1: Some node heavy materials change their look a bit. I think it might be connected to usage of the Gradient Node and you do list this node under the "improved color conversion" section. Could this be possible, even for just a grayscale gradient? I will try to make some tests with a simpler material.

Yes. For 2026 color conversion for these nodes was basically always wrong unless using legacy srgb or the value was exactly 1 or 0.
However we did add scene conversion that should keep scenes the same

Could you send me a scene with some of those materials (before they were converted to 1.9.1)

[Tim0042]

One more thing I noticed when rendering an existing scene from 1.9.0 in 1.9.1: Some node heavy materials change their look a bit. I think it might be connected to usage of the Gradient Node and you do list this node under the "improved color conversion" section. Could this be possible, even for just a grayscale gradient? I will try to make some tests with a simpler material.

Brought the material into a basic scene and simplified it a little bit. Purple submaterial has a noise node going into a gradient going into the bump, blue submat has a fresnel masked via a noise, also filtered through a gradient.

The same scene in 1.9.1 seems to result in a brighter fresnel and a clipped or otherwise adjusted bump noise. Still not sure if it does have something to do with the gradient, but I attached the c4d. =/

//EDIT: Ah, just saw your response after I was done typing - yep, I hope this helps and thanks for looking into it! : )

//EDIT: Updated the image, as I forgot to re-apply ACES in the LV for the new plugin version, so now the comparison is clearer - sorry!

[ChrisHekman]

One more thing I noticed when rendering an existing scene from 1.9.0 in 1.9.1: Some node heavy materials change their look a bit. I think it might be connected to usage of the Gradient Node and you do list this node under the "improved color conversion" section. Could this be possible, even for just a grayscale gradient? I will try to make some tests with a simpler material.

Brought the material into a basic scene and simplified it a little bit. Purple submaterial has a noise node going into a gradient going into the bump, blue submat has a fresnel masked via a noise, also filtered through a gradient.

The same scene in 1.9.1 seems to result in a brighter fresnel and a clipped or otherwise adjusted bump noise. Still not sure if it does have something to do with the gradient, but I attached the c4d. =/

//EDIT: Ah, just saw your response after I was done typing - yep, I hope this helps and thanks for looking into it! : )

Gradient Test Material Look Change fix.png

//EDIT: Updated the image, as I forgot to re-apply ACES in the LV for the new plugin version, so now the comparison is clearer - sorry!

Thanks for the report. Apparently the gradient node was not being version converted to the new version of the plugin resulting in different values.
I added a fix. It will be part of the upcomming hotfix. I suspect tomorrow.

[ChrisHekman]

I tried a new standard interface but cinema4d crash on kernel change, always. Now i'm back on v1.9.0

We tried but QA and I cannot reproduce this crash. Could you provide more information on your settings, scene, c4d version and steps to reproduce the crash?

[Edovech87]

I've the last versione of cinema4d. When I open it, i select octane renderer (no save section with 1.9.1) and nothing else. Then I select path tracing and there's the crash. Very simple

[DinoMuhic]

I've the last versione of cinema4d. When I open it, i select octane renderer (no save section with 1.9.1) and nothing else. Then I select path tracing and there's the crash. Very simple

Can you please try with a default C4D Layout or re-instaling the plugin?

You say "no save section with 1.9.1" what do you mean with that? There is a save section in the Render Settings when you choose OctaneRender

[Edovech87]

I made a video to show you what's wrong with this version. As you can see, the save section is no longer available and free vram seems a little less than before with a default empty scene

[DinoMuhic]

I made a video to show you what's wrong with this version. As you can see, the save section is no longer available and free vram seems a little less than before with a default empty scene

We have a 1.9.3 out already viewtopic.php?t=85668&sid=04a1b01bfe5b237c3c9847b7261d52d0

Please redo any c4d layouts you may have using octane

Also any VRAM related things are usually related to the core engine and not the plugin

[Edovech87]

I see and now it works. The free vram is about 1 GB less the 1.9.0. I'll post in the right section. Sorry. I know it's about the octane core.