Octane 2026.2 for Cinema4D - v1.8.4

[bepeg4d]

@shine71:

Please write to help at otoy dot com asking for Beppe. thanks.

@desire and stefano-dear:

I've written you a PM

@cjadams:

Sorry, we cannot share any info about Apple Silicon Mac Render-Node.


ciao,
Beppe

[cjadams]

OK, I understand. Is anyone else having really slow laggy IPR on a high spec machine? - this should be working really really well, but it seems to be refreshing like every one second or something like that if I move my space mouse, I move it and then waits and refreshes one second then weights refreshes one second sometimes I get a little black screen for a split second and then it goes back to refreshing.

[Anlv]

Hi,

I updated from version 2025.4_v1.7.2 to this one, but now the rendering is very slow and unusable with old scene.
What is causing this?

I encountered the same problem today, but strangely, I was still using 1.8.4 a few days ago, and the rendering time was normal then (maybe 3-5 minutes, but now it takes about 20 minutes).

I noticed that I didn't change any Cinema 4D settings or install any new plugins, but Windows updated several patches and updated the graphics card driver, so I might need to troubleshoot the issue.

[stefano-dear]

Hi,

I updated from version 2025.4_v1.7.2 to this one, but now the rendering is very slow and unusable with old scene.
What is causing this?

I encountered the same problem today, but strangely, I was still using 1.8.4 a few days ago, and the rendering time was normal then (maybe 3-5 minutes, but now it takes about 20 minutes).

I noticed that I didn't change any Cinema 4D settings or install any new plugins, but Windows updated several patches and updated the graphics card driver, so I might need to troubleshoot the issue.

I don't know if it's the real source of the problems, but I didn't notice that by editing some materials the problem was solved. I didn't understand what and how it caused the rendering to slow down

[cjadams]

update;

I guess what I’ve noticed is that the octane IPR is just fine nice and snappy but the viewport rendering on C4D is messed up it refreshes like one frame for a second or something


- hey, is anybody but me having really slow viewport performance when doing viewport rendering and moving your scene around? I seem to remember that being a lot less laggy before but it’s like refreshing it like one frame per second or something like that and it’s really annoying and I’m also getting a black flicker once in a while. This is on a Verizon nine 9950 X 3D with 128 gigs of DDR five 6000 ram this thing should be fast with an RTX 4090 to boot

[Anlv]

update;

I guess what I’ve noticed is that the octane IPR is just fine nice and snappy but the viewport rendering on C4D is messed up it refreshes like one frame for a second or something


- hey, is anybody but me having really slow viewport performance when doing viewport rendering and moving your scene around? I seem to remember that being a lot less laggy before but it’s like refreshing it like one frame per second or something like that and it’s really annoying and I’m also getting a black flicker once in a while. This is on a Verizon nine 9950 X 3D with 128 gigs of DDR five 6000 ram this thing should be fast with an RTX 4090 to boot

This might be related to the color space conversion of textures when opening old projects; I noticed this very sluggish behavior even when I wasn't rendering, just manipulating multiple textures in the texture manager. Strangely, after restarting C4D multiple times and opening the same project, I found this phenomenon disappeared.

In my workflow, I usually keep render times around 5 minutes; when this sluggishness occurred, my render times shot up to 1 hour and 30 minutes.

[cjadams]

this is a brand new project adding a cube adding a texture having an HDI on a dome light Vietnam and that’s it

Ryzen 9 9950X3D - 128 gig ram - RTX 5090 24g vram
proArt x870-E creator wifi mobo

So i don’t think its the pc

NOTE: The octane window live viewer is fine — but the C4D “Viewport Rendering” set to on option is the one thats slow

[Ashiyawolf]

While this seems to have helped the OP, I don't understand what settings I need. Will there be a guide or post on what best settings to use?
It seems like before ACES 2065-1 was the working space for Octane, but now it's Linear SRGB? I'm just reflecting on what the OTOY Aces guide said for earlier versions.

I assume you are looking at the picture viewer? We are currently working on a solution for that.
In the meantime you can set the view transform to raw. That will show you the results in the selected colorspace in the OctaneRender PV Render Settings.
Ofcourse going to the legacy color space still works aswel.

RawPictureViewer.png

Hi,

No, I'm not talking about the picture viewer, this happen in the viewport rendering.

But now I've noticed that this only happen in the Viewport rendering and not in the octane live viewer.

To recap:
-When C4D is set to ACEScg color space and octane ACES tone mapping is on, the colors in the viewport rendering are wrong or distorted.
-When C4D is set to legacy color space and octane ACES tone mapping is on, the colors in the viewport renderng looks right as seen in the octane live viewer.

Thank you

Yea color management is a bit tricky in C4D. Lets go over the expected behavior from top to bottom with the default OCIO settings in 2026
ColorManagement.png

The Render Space at the top is the internal colorspace that C4D uses to store color information and do its calculations.
In C4D2026 this defaults to ACEScg, and previously in linear sRGB. Octane stores its colors as Linear sRGB and does its calculations using spectral rendering.

The Display Space is the colorspace the render results will be stored in. sRGB by default in C4D 2026. However you also will not see this colorspace by default.

Which leads us to the most important colorspace, the View Transform (Project). This is what the C4D viewport will be displayed in. It defaults to ACES 1.0 SDR-video.
This is what you actualy see in C4D at default.
When set to Raw, you will see the "Render Space", which will be ACEScg. <- This should match Octane LV when set to ACEScg
When set to Un-tone-mapped, you will see the "Display Space", which will be sRGB. <- This should match Octane LV when set to sRGB
When set to ACES 1.0 SDR-video it will be that colorspace. To make Octane LV match you need to load the same OCIO file as C4D and select it in the settings and LV

Now that being said. You will still see differences in colors between Octane and C4D. This is because lighting intensity and material light response will differ between Octane and C4D, and you will need to get them right.